-
Notifications
You must be signed in to change notification settings - Fork 2
/
swagger.yaml
1005 lines (969 loc) · 32.9 KB
/
swagger.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
openapi: 3.0.3
info:
title: Family Car Tracker - OpenAPI 3.0
description: |-
This is a sample family car tracking application allowing us to book car usage times.
Since I'm are using cookie auth on this Family Car project, the Try It Out feature won't work in browsers due to security limitations. Please use Postman to try these requests.
Database is located in AWS DynamoDB, it's named `development-family-car-booking-app`
contact:
email: kushliansky@gmail.com
license:
name: Apache 2.0
url: http://www.apache.org/licenses/LICENSE-2.0.html
version: 1.0.0
servers:
- url: https://qa-car-tracker.ilya.online
paths:
/signup:
post:
summary: Sign up with your credentials.
description: Sign up with your credentials and basic user data.
requestBody:
content:
application/json:
schema:
type: object
properties:
username:
type: string
example: masha@gmail.com
description: Should be the user's email
password:
type: string
example: myPassW0rd
providedCarIds:
type: array
example: ['ho-123456']
default: []
description: By default the user does not provide any cars
availableCarIds:
type: array
example: ['ho-123456']
default: ['ho-123456']
description: By default the user gets assigned the Family Honda car. This is done for simplicity. In a real app, the user needs to provide their own car out of a list or create a car on the fly. This app is for educational purposes, so we are removing this complexity.
firstName:
type: string
example: Maria
description: Your user's name as it will be shown in the application
responses:
'200':
description: Successful signup
content:
application/json:
schema:
type: object
properties:
IdToken:
type: string
example: abc
AccessToken:
type: string
example: abc
RefreshToken:
type: string
example: abc
'400':
description: Bad request. You did not provide the necessary information for a successful signup.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Bad Request'
/token/refresh:
post:
summary: Refresh access and id token by presenting a secure refresh token
parameters:
- in: header
name: x-refresh-token
schema:
type: string
required: true
responses:
'200':
description: Successful refresh. You will get IdToken and AccessToken back
content:
application/json:
schema:
type: object
properties:
IdToken:
type: string
example: abc
AccessToken:
type: string
example: abc
'401':
description: Unauthorized. Invalid credentials presented or the refresh token has already been revoked.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Invalid credentials provided'
/login:
post:
summary: Login with your credentials
description: Supply login and password to authenticate.
requestBody:
content:
application/json:
schema:
type: object
properties:
username:
type: string
example: masha@mail.com
password:
type: string
example: myPassW0rd
responses:
'200':
description: Successful login. You will get IdToken, AccessToken and RefreshToken in the response body
content:
application/json:
schema:
type: object
properties:
RefreshToken:
type: string
example: abc
IdToken:
type: string
example: abc
AccessToken:
type: string
example: abc
'400':
description: Bad request. You did not provide any credentials at all, so request is incorrect.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'No credentials provided'
'401':
description: Unauthorized. Invalid credentials presented.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Invalid credentials provided'
/me:
get:
summary: Get my username
description: Current user's username by cookie
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
username:
type: string
example: mariakazakova92@gmail.com
'401':
description: Unauthorized. Invalid cookie presented or cookie was not included in the request or cookie is incorrect.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
/logout:
post:
summary: Logout using your credentials
description: You must provide access token in the request body. When you revoke your tokens, you won't be able to use them for accessing the backend.
requestBody:
content:
application/json:
schema:
type: object
properties:
accessToken:
type: string
example: abc
responses:
'200':
description: Successful operation. Your refresh token was revoked and cannot be used for refreshing tokens anymore until you log in again.
'401':
description: Unauthorized.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Logout error'
/users/{username}:
get:
summary: Get user info
description: Information about the user, their rides, cars etc.
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
- in: path
name: username
description: User's name as it appears in the DynamoDB database
schema:
type: string
required: true
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
user:
type: object
properties:
username:
type: string
firstName:
type: string
roles:
type: array
items:
type: string
example: [ "driver", "carProvider" ]
availableCars:
type: array
items:
type: string
example: [ "ho-123", "renault-789" ]
providedCars:
type: array
items:
type: string
example: [ "renault-789" ]
settings:
$ref: '#/components/schemas/Settings'
'401':
description: Unauthorized. Invalid credentials presented.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Invalid credentials provided'
patch:
summary: Update user data
description: Update user data like settings etc.
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
- in: path
name: username
description: User's email
schema:
type: string
required: true
requestBody:
required: true
description: Partial settings object is also possible in one request
content:
application/json:
schema:
type: object
properties:
settings:
$ref: '#/components/schemas/Settings'
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
user:
type: object
properties:
username:
type: string
firstName:
type: string
roles:
type: array
items:
type: string
example: [ "driver", "carProvider" ]
availableCars:
type: array
items:
type: string
example: [ "ho-123", "renault-789" ]
providedCars:
type: array
items:
type: string
example: [ "renault-789" ]
settings:
$ref: '#/components/schemas/Settings'
'401':
description: Unauthorized. Invalid credentials presented.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Invalid credentials provided'
/bookings/finish/id:
post:
summary: Finish ride
description: Finish one ride of a user
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
- in: query
name: username
description: User's name as it appears in the DynamoDB database
example: maria@mail.com
schema:
type: string
required: true
- in: query
name: carId
example: ho-123456
description: User's car id (license plate)
required: true
schema:
type: string
- in: query
name: startTime
example: 1659716808
description: Timestamp (seconds, not JS milliseconds) of the booking start time
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
type: object
properties:
rideCompletionText:
type: string
example: abc
required: true
endDateTime:
type: number
example: 12345678
required: false
responses:
'200':
description: Successfully finished the ride
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: Finished ride successfully
'400':
description: Bad request. You did not provide the necessary information for a successful finish of the ride.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Bad Request'
'401':
description: Unauthorized. You likely did not supply the user's access token. The token should be valid and not expired.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
'403':
description: Forbidden. You probably tried to modify someone else's data.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Forbidden'
'500':
description: Server-side error
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Error finishing the ride'
/bookings/id:
get:
summary: Get booking by ID
description: Information about the booking
parameters:
- in: query
name: username
description: User's name as it appears in the DynamoDB database
example: ilya_nice
schema:
type: string
required: true
- in: query
name: carId
example: ho-123456
description: User's car id (license plate)
required: true
schema:
type: string
- in: query
name: startTime
example: 1659716808
description: Timestamp (seconds, not JS milliseconds) of the booking start time
required: true
schema:
type: string
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
booking:
type: object
properties:
bookingOwner:
type: object
properties:
username:
type: string
firstName:
type: string
sessionId:
type: string
roles:
type: array
items:
type: string
example: [ "driver", "carProvider" ]
availableCars:
type: array
items:
type: string
example: [ "ho-123", "renault-789" ]
providedCars:
type: array
items:
type: string
example: [ "renault-789" ]
settings:
$ref: '#/components/schemas/Settings'
bookingOwnerId:
type: string
example: "ilya_nice"
carNumber:
type: string
example: "ho-123456"
bookingStartTime:
type: string
example: "2022-10-02T19:27:43.000Z"
bookingDescription:
type: string
example: "Поездка в Новолукомль"
'401':
description: Unauthorized. Invalid credentials presented.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
'404':
description: Not Found. Do not rely on the wording of these errors! They may change on the backend side any time. Look at error codes. Check if your fetching library throws an error on response code 500 or still considers it a success and never goes to the `catch` part of the `try/catch` clause.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Could not find booking by ID'
'500':
description: Server side error. Do not rely on the wording of these errors! They may change on the backend side any time.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Error getting booking details'
patch:
summary: Edit a booking
description: Edit a new booking by supplying field that you want to change
requestBody:
required: true
content:
application/json:
schema:
properties:
startDateTime:
type: number
example: 1666439360
description: "New timestamp in seconds (!). Warning: providing Javascript milliseconds does not work!"
required: false
endDateTime:
type: number
example: 1666439360
description: "New timestamp of the end of ride in seconds. It is not required when creating a booking, but could be provided if known"
required: false
description:
type: string
description: New name of your ride
required: false
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
- in: query
name: username
description: User's name as it appears in the DynamoDB database
example: maria@mail.com
schema:
type: string
required: true
- in: query
name: carId
example: ho-123456
description: User's car id (license plate)
required: true
schema:
type: string
- in: query
name: startTime
example: 1659716808
description: Timestamp (seconds, not JS milliseconds) of the booking start time
required: true
schema:
type: string
responses:
'200':
description: Successful edit
content:
application/json:
schema:
type: object
properties:
booking:
type: object
properties:
bookingOwnerId:
type: string
example: mary@gmail.com
carNumber:
type: string
example: "ho-123456"
bookingStartTime:
type: string
example: "2022-10-29T13:47:44.000Z"
bookingDescription:
type: string
example: Masha - visit parents
'400':
description: Bad request. You did not provide the necessary information the successful editing of the booking.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Bad Request'
'401':
description: Unauthorized. You likely forgot to include the cookie in the request, or the cookie is incorrect.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
'404':
description: Booking not found
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Could not find booking by ID'
'500':
description: Server side error. Do not rely on the wording of these errors! They may change on the backend side any time.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Error saving your booking'
delete:
summary: Delete ride
description: Delete one ride of a user
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
- in: query
name: username
description: User's name as it appears in the DynamoDB database
example: maria@mail.com
schema:
type: string
required: true
- in: query
name: carId
example: ho-123456
description: User's car id (license plate)
required: true
schema:
type: string
- in: query
name: startTime
example: 1659716808
description: Timestamp (seconds, not JS milliseconds) of the booking start time
required: true
schema:
type: string
responses:
'200':
description: Successfully deleted the booking
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: Booking removed
'400':
description: Bad request. You did not provide the necessary information for a successful deletion of the booking.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Bad Request'
'401':
description: Unauthorized. You likely did not supply the user's access token. The token should be valid and not expired.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
'500':
description: Server-side error
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Error getting booking details'
/bookings:
get:
summary: Get all bookings by some criterion (car, user etc.)
description: List of bookings for a particular car or a particular user. For example, for family Honda, this should return a list of all bookings, including created by Masha, Ilya and Papa.
When `username` is included in query params together with `carId`, then user details are also returned
parameters:
- in: query
name: carId
example: ho-123456
description: User's car id (license plate)
required: true
schema:
type: string
- in: query
name: username
example: masha@mail.com
description: User's name, if you want to refine the search to find only the rides for a particular user
required: false
schema:
type: string
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
bookings:
type: array
items:
type: object
properties:
bookingOwnerId:
type: string
example: mariya_kalib
carNumber:
type: string
example: "ho-123456"
bookingStartTime:
type: string
example: "2022-10-19T13:47:44.000Z"
bookingDescription:
type: string
example: Masha - visit parents
'401':
description: Unauthorized. You either gave a car number that the current user cannot access, or you forgot to include the Authorization header in the request.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
'404':
description: Bookings not found
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Could not find booking by ID'
'500':
description: Server side error. Do not rely on the wording of these errors! They may change on the backend side any time.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Error getting booking details'
post:
summary: Create a booking
description: Create a new booking by supplying required parameters
requestBody:
required: true
content:
application/json:
schema:
properties:
username:
type: string
example: masha@mail.com
required: true
carId:
type: string
example: ho-123456
required: true
startDateTime:
type: number
example: 1666439360
description: "Timestamp in seconds (!). Warning: providing Javascript milliseconds does not work!"
required: true
endDateTime:
type: number
example: 1666439360
description: "Timestamp of the end of ride in seconds. It is not required when creating a booking, but could be provided if known"
required: false
description:
type: string
description: Name of your ride
required: false
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
booking:
type: object
properties:
bookingOwnerId:
type: string
example: mariya_kalib
carNumber:
type: string
example: "ho-123456"
bookingStartTime:
type: string
example: "2022-10-29T13:47:44.000Z"
bookingDescription:
type: string
example: New title of your booking
'401':
description: Unauthorized. You likely forgot to include the cookie in the request, or the cookie is incorrect.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
'404':
description: Bookings not found
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Could not find booking by ID'
'500':
description: Server side error. Do not rely on the wording of these errors! They may change on the backend side any time.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Error saving your booking'
/account:
delete:
summary: Delete user account by credentials
description: Delete the user's account and their rides and information. Sign up once again to create a new user
parameters:
- in: header
name: Authorization
description: "Access token. The format should be `Authorization: Bearer <your-token>`"
required: true
schema:
type: string
responses:
'200':
description: Successfully deleted the user
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: User removed
'401':
description: Unauthorized. You likely did not supply the user's access token. The token should be valid and not expired.
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Unauthorized'
'500':
description: Server-side error
content:
application/json:
schema:
type: object
properties:
status:
type: string
example: 'Error getting booking details'
components:
schemas:
Settings:
type: object
properties:
rideCompletionText:
type: string
example: 'Машина в гараже'
notifications:
type: object
properties: