You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`bad_param`| A validation error occurred | Array of parameters with errors |
101
109
|`missing_param`| A required parameter is missing | Array of missing parameters |
102
110
|`already_registered`| A vehicle with `device_id` is already registered ||
103
111
104
-
403 Unauthorized Response:
105
-
106
-
**None**
107
-
108
112
### Vehicle - Update
109
113
110
114
The `/vehicles` update endpoint is used to change vehicle information, should some aspect of the vehicle change, such as the `vehicle_id`. Each vehicle must already be registered.
@@ -113,16 +117,24 @@ The `/vehicles` update endpoint is used to change vehicle information, should so
113
117
**Method:**`PUT`
114
118
**Payload:** An array of [Vehicles](/data-types.md#vehicles)
115
119
116
-
200 Success Response:
120
+
#### Responses
121
+
122
+
Possible Responses:
123
+
200
124
+
400
125
+
401
126
+
406
127
+
409
128
+
500
117
129
118
-
See [Bulk Responses][bulk-responses]
130
+
See [Responses][responses], [Bulk Responses][bulk-responses], and [schema][schema] for details.
|`device_id`| UUID | Optional | If provided, retrieve the specified vehicle |
142
154
143
-
200 Success Response:
144
-
145
155
If `device_id` is specified, `GET` will return an array with a single vehicle record, otherwise it will be a list of vehicle records with pagination details per the [JSON API](https://jsonapi.org/format/#fetching-pagination) spec:
146
156
147
157
```json
@@ -157,9 +167,17 @@ If `device_id` is specified, `GET` will return an array with a single vehicle re
157
167
}
158
168
```
159
169
160
-
404 Failure Response:
170
+
#### Responses
161
171
162
-
_No content returned on vehicle not found._
172
+
Possible Responses:
173
+
200
174
+
400 (with `vehicle_id` parameter)
175
+
401
176
+
404
177
+
406
178
+
500
179
+
180
+
See [Responses][responses], [Bulk Responses][bulk-responses], and [schema][schema] for details.
|`device_id`| UUID | Optional | If provided, retrieve the specified vehicle |
179
197
180
-
200 Success Response:
181
-
182
198
If `device_id` is specified, `GET` will return an array with a vehicle status record, otherwise it will be a list of vehicle records with pagination details per the [JSON API](https://jsonapi.org/format/#fetching-pagination) spec:
183
199
184
200
```json
@@ -194,9 +210,17 @@ If `device_id` is specified, `GET` will return an array with a vehicle status re
194
210
}
195
211
```
196
212
197
-
404 Failure Response:
213
+
#### Responses
198
214
199
-
_No content returned on vehicle not found._
215
+
Possible Responses:
216
+
200
217
+
400 (with `vehicle_id` parameter)
218
+
401
219
+
404
220
+
406
221
+
500
222
+
223
+
See [Responses][responses], [Bulk Responses][bulk-responses], and [schema][schema] for details.
200
224
201
225
[Top][toc]
202
226
@@ -211,9 +235,17 @@ The Trips endpoint serves two purposes:
211
235
**Method:**`POST`
212
236
**Payload:** Array of [Trips](/data-types.md#trips)
213
237
214
-
200 Success Response:
238
+
### Responses
239
+
240
+
Possible Responses:
241
+
201
242
+
400
243
+
401
244
+
404
245
+
406
246
+
500
215
247
216
-
See [Bulk Responses][bulk-responses]
248
+
See [Responses][responses], [Bulk Responses][bulk-responses], and [schema][schema] for details.
217
249
218
250
### Trip Errors:
219
251
@@ -233,9 +265,17 @@ The vehicle `/telemetry` endpoint allows a Provider to send vehicle telemetry da
233
265
**Method**: `POST`
234
266
**Payload**: An array of vehicle [Telemetry][vehicle-telemetry]
235
267
236
-
200 Success Response:
268
+
### Responses
269
+
270
+
Possible Responses:
271
+
201
272
+
400
273
+
401
274
+
404
275
+
406
276
+
500
237
277
238
-
See [Bulk Responses][bulk-responses]
278
+
See [Responses][responses], [Bulk Responses][bulk-responses], and [schema][schema] for details.
239
279
240
280
### Telemetry Errors:
241
281
@@ -255,9 +295,17 @@ The vehicle `/events` endpoint allows the Provider to submit events describing t
255
295
**Method:**`POST`
256
296
**Payload:** An array of vehicle [Events](/data-types.md#events)
257
297
258
-
200 Success Response:
298
+
### Responses
259
299
260
-
See [Bulk Responses][bulk-responses]
300
+
Possible Responses:
301
+
201
302
+
400
303
+
401
304
+
404
305
+
406
306
+
500
307
+
308
+
See [Responses][responses], [Bulk Responses][bulk-responses], and [schema][schema] for details.
261
309
262
310
### Event Errors:
263
311
@@ -279,9 +327,17 @@ The `/stops` endpoint allows an agency to register city-managed Stops, or a prov
279
327
**Method:**`POST`
280
328
**Payload**: An array of [Stops][stops]
281
329
282
-
200 Success Response:
330
+
### Responses
331
+
332
+
Possible Responses:
333
+
201
334
+
400
335
+
401
336
+
406
337
+
409
338
+
500
283
339
284
-
See [Bulk Responses][bulk-responses]
340
+
See [Responses][responses], [Bulk Responses][bulk-responses], and [schema][schema] for details.
285
341
286
342
#### Stops Register Errors:
287
343
@@ -315,9 +371,17 @@ See [Bulk Responses][bulk-responses]
0 commit comments