forked from TOMP-WG/TOMP-API
-
Notifications
You must be signed in to change notification settings - Fork 0
/
TOMP-API.yaml
2865 lines (2755 loc) · 99.8 KB
/
TOMP-API.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.0
info:
title: Transport Operator MaaS Provider API
description:
An API between MaaS providers and transport operators for booking trips and corresponding assets.
<p>The documentation (examples, process flows and sequence diagrams) can be found at <a href="https://github.com/TOMP-WG/TOMP-API/">github</a>.
version: "0.9.0"
license:
name: Apache 2.0
url: "http://www.apache.org/licenses/LICENSE-2.0.html"
tags:
- name: planning
description: gives information about transport asset availability and pricing [free_bike_status and system_pricing_plans in GBFS].<p> The endpoints in this part can give information about the availability of assets (or assetTypes) and can provide information to take the next step - the booking part.
- name: booking
description: a booking is the main object exchanged between MaaS and a TO [from MaaS-API]. <br>See also <a href='https://github.com/maasglobal/maas-tsp-api/blob/master/specs/Booking.md'>Booking.md</a><p>This section contains functionality to book a leg (part of a trip) for one asset (or assetType), including the non-happy paths (cancel, expire etc).
- name: booking [optional]
description: endpoints that can faciliate processes in the booking process, but are not necessary for a minimal viable product. You can think of getting information, updating (parts of) a booking (not the state!), adding and removing subscriptions (webhook), etc.
- name: trip execution
description: supports the complete trip execution process. It contains f.i. getting an available asset, assigning the asset to the leg, starting, pausing, finishing a leg (all by using the POST /legs/{id}/events) or updating an execution (not the state!).
- name: trip execution [optional]
description: endpoints that can facilitate processes in the trip execution process, but are not necessary for a minimal viable product.
- name: general
description: general operations (e.g. notifications)
- name: operator information
description: gives information about systems, stations, operating hours [from GBFS]
- name: payment
description: arranges financial settlement for legs
- name: support
description: support for the user while the leg is ongoing
- name: TO
description: the Transport Operator's endpoints
- name: MP
description: the MaaS Service Provider's endpoints
# security. Allowed methods basic (in header: Authorization: Basic ZGVtbzpwQDU1dzByZA==),
# bearer (in header: Authorization: Bearer <token>)
# Api-key (in header: X-API-Key: abcdef12345)
# OAuth2 and OpenId are also available
# The exact ways to authenticate will be described in a later version
security:
- BasicAuth: []
- BearerAuth: []
- ApiKeyAuth: []
- OAuth: []
- OpenId: []
paths:
/plannings/:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
post:
description:
Returns plannings for the given travel plan. <p>Start time can be defined, but is optional. If startTime is not provided, but required by the third party API, a default value of "Date.now()" is used. [from MaaS-API /listing].
During the routing phase this service can be used to check availability without any state changes. <p>In the final check, just before presenting the alternatives to the user, a call should be made using `booking-intent`, requesting the TO to provide booking IDs to reference to during communication with the MP.
<p>see (2.1) in the process flow - planning
tags:
- planning
- TO
parameters:
- name: booking-intent
in: query
description: Specifies whether IDs should be returned for the leg options that can be referred to when booking
schema:
type: boolean
default: false
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/planningRequest"
responses:
"201":
description: Available transport methods matching the given query parameters. If no transport methods are available, an empty array is returned.
content:
application/json:
schema:
$ref: "#/components/schemas/planning"
headers:
Location:
description: The URI where the most up to date version of the created planning result can be found. Not required.
schema:
type: string
example: "/plannings/1234"
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"202":
$ref: "#/components/responses/202Accepted"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/plannings/{id}:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Planning identifier
required: true
schema:
type: string
get:
description: Returns the planning result.
tags:
- planning [optional]
- TO
responses:
"200":
description: The planning was found
content:
application/json:
schema:
$ref: "#/components/schemas/planning"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
"410":
$ref: "#/components/responses/410Gone"
/bookings/:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
post:
description:
Creates a new `Booking` for the TO in **Pending** state. The ID of the posted booking should be the ID provided in the previous step (planning).
<p>The Booking may be modified in the response, e.g. location being adjusted for a more suitable pick-up location.
In addition, the service may contain a **meta** attribute for arbitrary TO metadata that the TO needs later, and **token** attribute depicting how long the current state is valid.
<p>The optional webhook can be used to post updates from TO to MP. If it isn't used, the subscription possibility in this API can be used or the events can be posted directly.
<p> see (3.2) in the process flow - booking
tags:
- booking
- TO
requestBody:
description: One of available legs, returned by /plannings, with an ID.
required: true
content:
application/json:
schema:
$ref: "#/components/schemas/bookingRequest"
responses:
"201":
description: A new booking was succesfully created, status pending
content:
application/json:
schema:
$ref: "#/components/schemas/booking"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
Expires:
description: The result is valid until this timestamp. The pending booking is expired after this timestamp. This option can be used, but there is also a facility to use the webhook, mentioned in '#/component/schemas/booking'.
schema:
description: A HTTP date string, see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires
type: string
format: http-date
required: true
"202":
$ref: "#/components/responses/202Accepted"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
"409":
$ref: "#/components/responses/409Conflict"
callbacks: # webhooks
# as described in https://swagger.io/docs/specification/callbacks/
booking-operations:
"{$request.body#/webhook}":
patch:
description: see POST /bookings/{id}/events
responses:
"200":
description: operation ok
get:
description: Optional - Returns bookings that has been created earlier, selected on state.
tags:
- booking [optional]
- TO
parameters:
- name: state
in: query
required: true
schema:
$ref: "#/components/schemas/bookingState"
responses:
"200":
description: The bookings matching the query
content:
application/json:
schema:
type: array
description: The bookings that matched the query (zero or more)
items:
$ref: "#/components/schemas/booking"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/bookings/{id}/events:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Leg identifier
required: true
schema:
type: string
post:
description: This endpoint **must** be used to alter the state of a booking:<br>- The operation 'CANCEL' Cancels the booking (see <4> in the process flow - booking), <br>- the operation 'EXPIRE' informs that the booking-option is expired (seel <5> in the process flow - booking) and <br>- the 'COMMIT' actually makes this booking option a real confirmed booking. (see also (3.2) in process flow - booking). This event should also be used to commit in the 'postponed-commit' scenario.<br> - 'DENY' tells the MP that the leg is cancelled in the post-commit scenario. <p> `CANCEL` - Cancels a confirmed booking. Cancelling twice should still return 204. <br> `EXPIRE` - Typically for sending back a signal from TO to MP to tell the pending state is expired. Expiring twide should return 204. Expiring a booking in a non-pending state will result in 403. <BR> `COMMIT` - Turns the booking in a confirmed state, after all legs are in state pending. Committing twice will result in 204. If the booking is in state CANCELLED or EXPIRED, a commit will result a 403. <BR> `DENY` - Used for the 'postponed-commit' scenario. Whenever a TO cannot give garantees directly to fullfil a booking, it can return a 'COMMIT', but the state of the booking object should be 'POSTPONED-COMMIT'. In the conditions returned in the planning phase is stated until when this phase can be. After this time it will be come expired. Otherwise it can be commmitted when the leg is confirmed or denied (using this event).
tags:
- booking
- MP
- TO
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/bookingOperation"
responses:
"200":
description: The modified booking
content:
application/json:
schema:
$ref: "#/components/schemas/booking"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"204":
$ref: "#/components/responses/204NoContent"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"403":
$ref: "#/components/responses/403Forbidden"
"404":
$ref: "#/components/responses/404NotFound"
"410":
$ref: "#/components/responses/410Gone"
/bookings/{id}:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Booking identifier
required: true
schema:
type: string
get:
description: Returns the booking. See (3.5.2) in the process flow - booking. In the 'meta'-field the digital tickes can be returned (see (3.3) in the process flow - booking)
tags:
- booking
- TO
responses:
"200":
description: The booking was found
content:
application/json:
schema:
$ref: "#/components/schemas/booking"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
"410":
$ref: "#/components/responses/410Gone"
put:
description: Optional - This endpoint should be used to adjust the parameters of the booking. Changes not acceptable to the TO should return 400. If a booking is started and can no longer be adjusted the TO should return 403. The state of the booking should **never** be adjusted using this method. Use /bookings/{id}/events for that. See also (7.2) in the flow diagram - booking.
tags:
- booking
- TO
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/booking"
description: changed booking
required: true
responses:
"200":
description: The booking was modified
content:
application/json:
schema:
$ref: "#/components/schemas/booking"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"403":
$ref: "#/components/responses/403Forbidden"
"404":
$ref: "#/components/responses/404NotFound"
"409":
$ref: "#/components/responses/409Conflict"
"410":
$ref: "#/components/responses/410Gone"
/bookings/{id}/subscription:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Booking identifier
required: true
schema:
type: string
post:
description: Optional - subscribe to a specific booking (=leg & (type of) asset). This is an optional endpoint. This endpoint facilitates notifications in all the phases. (see (7.1) in the flow chart - execution)
tags:
- booking [optional]
- TO
- MP
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/booking"
responses:
"204":
$ref: "#/components/responses/204NoContent"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
"410":
$ref: "#/components/responses/410Gone"
callbacks: # webhooks
# as described in https://swagger.io/docs/specification/callbacks/
booking-operations:
"{$request.body#/webhook}":
patch:
description: see POST /booking/{id}/events
responses:
"200":
description: operation ok
delete:
description: Optional - subscribe to a specific booking (=leg & (type of) asset). This is an optional endpoint
tags:
- booking [optional]
- TO
- MP
responses:
"204":
$ref: "#/components/responses/204NoContent"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
"410":
$ref: "#/components/responses/410Gone"
default:
description: Unexpected error
content:
application/json:
schema:
$ref: "#/components/schemas/error"
/bookings/{id}/notifications:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Booking identifier
required: true
schema:
type: string
get:
description: retrieves all notifications concerning events related to this booking.
tags:
- general
- TO
responses:
"200":
description: The bookings matching the query
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
content:
application/json:
schema:
type: array
description: Notifications related to this booking. Later versions of this API will define the types and use more extensively. For now, this is a catch-all for any messages the TO or MP need to send to each other that does not have its own API call.
items:
$ref: "#/components/schemas/notification"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
"410":
$ref: "#/components/responses/410Gone"
post:
description: notification between MaaS provider and Transport operator in case of user no-show or if specific asset is not available or some other event occurs not covered by other API calls.
tags:
- general
- TO
- MP
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/notification"
responses:
"204":
$ref: "#/components/responses/204NoContent"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
"410":
$ref: "#/components/responses/410Gone"
/legs/{id}/available-assets:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Leg identifier
required: true
schema:
type: string
get:
description: Returns a list of available assets for the given leg. These assets can be used to POST to /legs/{id}/asset if no specific asset is assigned by the TO. If picking an asset is not allowed for this booking, or one already has been, 403 should be returned. If the booking is unknown, 404 should be returned. See (4.7) in the process flow. - trip execution
tags:
- trip execution
- TO
responses:
"200":
description: Available assets for the leg. If no suitable assets are found an empty array is to be returned.
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/asset"
"401":
$ref: "#/components/responses/401Unauthorized"
"403":
$ref: "#/components/responses/403Forbidden"
"404":
$ref: "#/components/responses/404NotFound"
/legs/{id}:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Leg identifier
required: true
schema:
type: string
get:
description: Retrieves the latest summary of the leg, being the execution of a portion of a journey travelled using one asset (vehicle). Every leg belongs to one booking, every booking has at least one leg. Where the booking describes the agreement between user/MP and TO, the leg describes the journey as it occured. See (4.3) in the flow chart - trip execution
tags:
- trip execution
- TO
- MP
responses:
"200":
description: operation successful
content:
application/json:
schema:
$ref: "#/components/schemas/leg"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
put:
description: Updates the leg with new information. Only used for updates about execution to the MP. To request changes as the MP, the booking should be updated and the TO can accept the change and update the leg in turn.
tags:
- trip execution
- MP
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/leg"
description: changed leg (e.g. with different duration or destination)
required: true
responses:
"204":
$ref: "#/components/responses/204NoContent"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
/legs/{id}/events:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Leg identifier
required: true
schema:
type: string
post:
description: This endpoint must be used to alter the state of a leg.<br>
Operations:<br> `PREPARE` the TO can send a message telling the MP that he is preparing the booked leg [To be implemented by the MP] (see (7.2) in the process flow - trip execution),<br>
`ASSIGN_ASSET` can assign an asset to a leg. Can be to assign an asset in case there is still an asset type assigned [Optionally implementable by the MP]. See (4.7) in the process flow - trip execution<br>
`RESERVE` will claim an asset ahead in time [Optionally implementable by the TO],<br>
`SET_IN_USE` will activate the leg or resume the leg [TO and MP] (see (4.6) in process flow),<br>
`PAUSE` will pause the leg [TO and MP] (see (4.6) in process flow),<br>
`START_FINISHING` will start the end-of-leg [Optionally implementable by TO and MP],<br>
`FINISH` will end this leg (see (4.6) in process flow) [TO and MP]
tags:
- trip execution
- MP
- TO
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/legEvent"
responses:
"200":
description: operation successful
content:
application/json:
schema:
$ref: "#/components/schemas/leg"
"204":
$ref: "#/components/responses/204NoContent"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
/legs/{id}/progress:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
- name: id
in: path
description: Leg identifier
required: true
schema:
type: string
get:
description: Monitors the current location of the asset and duration & distance of the leg (see (4.7) in process flow)
tags:
- trip execution
- TO
parameters:
- name: location-only
in: query
description: Specifies if only the location should be returned
schema:
type: boolean
default: false
responses:
"200":
description: operation successful
content:
application/json:
schema:
$ref: "#/components/schemas/legProgress"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
post:
description: Monitors the current location of the asset and duration & distance of the leg
tags:
- trip execution
- MP
requestBody:
content:
application/json:
schema:
$ref: "#/components/schemas/legProgress"
responses:
"204":
$ref: "#/components/responses/204NoContent"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
"404":
$ref: "#/components/responses/404NotFound"
/operator/meta:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
get:
tags:
- operator information
- TO
- MP
summary: describes the running implementations
description: all versions that are implemented on this url, are described in the result of this endpoint. In contains all versions and per version the endpoints, their status
and the supported scenarios.
responses:
'200':
description: successful operation
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/endpointImplementation"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
/operator/stations:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- operator information
- TO
summary: describes all available stations
description: All stations contained in this list are considered public (ie, can be shown on a map for public use). If there are private stations (such as Capital Bikeshare's White House station) these should not be exposed here and their status should not be included [from GBFS]
responses:
"200":
description: successful operation
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/stationInformation"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/operator/available-assets:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
description: Returns a list of available assets.
tags:
- operator information
- TO
responses:
"200":
description: Available assets or asset-types. In case assets are replied, the realtime location is also available.
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/assetType"
"401":
$ref: "#/components/responses/401Unauthorized"
"403":
$ref: "#/components/responses/403Forbidden"
"404":
$ref: "#/components/responses/404NotFound"
/operator/alerts:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- operator information
- TO
summary: informs customers about changes to the system outside of normal operations
description: This feed is intended to inform customers about changes to the system that do not fall within the normal system operations. For example, system closures due to weather would be listed here, but a system that only operated for part of the year would have that schedule listed in the system-calendar.json feed. This file is an array of alert objects defined as below. Obsolete alerts should be removed so the client application can safely present to the end user everything present in the feed. The consumer could use the start/end information to determine if this is a past, ongoing or future alert and adjust the presentation accordingly. [from GBFS]
responses:
"200":
description: returns currently active system alerts
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/systemAlert"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/operator/operating-calendar:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- operator information
- TO
summary: describes the operating calendar for a system. An array of year objects defined as follows (if start/end year are omitted, then assume the start and end months do not change from year to year). [from GFBS]
responses:
"200":
description: successful operation
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/systemCalendar"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/operator/operating-hours:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- operator information
- TO
summary: describes the system hours of operation
description: Describes the hours of operation of all available systems of the transport operator [from GBFS]
responses:
"200":
description: successful operation
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/systemHours"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/operator/information:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- operator information
- TO
summary: describes the system
description: Describes the system including System operator, System location, year implemented, URLs, contact info, time zone. [from GBFS]
responses:
"200":
description: successful operation
content:
application/json:
schema:
$ref: "#/components/schemas/systemInformation"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/operator/pricing-plans:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- operator information
- TO
summary: gives pricing information
description: Describes pricing of systems or assets [from GBFS]
responses:
"200":
description: returns standard pricing plans for an operator
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/systemPricingPlan"
headers:
Content-Language:
description: The language/localization of user-facing content
example: nl
schema:
type: string
format: One IETF BCP 47 (RFC 5646) language tag
required: true
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/operator/regions:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- operator information
- TO
summary: describes regions for a system that is broken up by geographic or political region. It is defined as a separate feed to allow for additional region metadata (such as shape definitions). [from GBFS]
responses:
"200":
description: successful operation
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/systemRegion"
"400":
$ref: "#/components/responses/400BadRequest"
"401":
$ref: "#/components/responses/401Unauthorized"
/payment/journal-entry:
parameters:
- $ref: "#/components/parameters/acceptLanguage"
- $ref: "#/components/parameters/api"
- $ref: "#/components/parameters/apiVersion"
get:
tags:
- payment
- MP
- TO
description: Returns all the journal entries that should be paid per leg
parameters:
- name: from
in: query
description: start of the selection
required: true
schema:
type: string
format: date-time
- name: to
in: query
description: end of the selection