Skip to content

Commit bf09aaf

Browse files
committed
DEV Proposal for better Telemetry error handling
1 parent bdbe4ce commit bf09aaf

1 file changed

Lines changed: 21 additions & 9 deletions

File tree

agency/README.md

Lines changed: 21 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -224,16 +224,9 @@ Body Params:
224224
| ---------- | ------------------------------ | ------------------------------------------------------------------------------------------------------- |
225225
| `success` | Integer | Number of successfully written telemetry data points. |
226226
| `total` | Integer | Total number of provided points. |
227-
| `failures` | [Telemetry](#telemetry-data)[] | Array of failed telemetry for zero or more vehicles (empty if all successful). |
227+
| `failures` | [Telemetry Error](#telemetry-error)[] | Array of errors including the failed telemetry data and error details (empty if all successful). |
228228

229-
400 Failure Response:
230-
231-
| `error` | `error_description` | `error_details`[] |
232-
| --------------- | ------------------------------------ | --------------------------------- |
233-
| `bad_param` | A validation error occurred. | Array of parameters with errors |
234-
| `invalid_data` | None of the provided data was valid. | |
235-
| `missing_param` | A required parameter is missing. | Array of missing parameters |
236-
| `unregistered` | Some of the devices are unregistered | Array of unregistered `device_id` |
229+
Alway returns 200. Any failed data is detailed in the `failures` array of the response.
237230

238231
[Top][toc]
239232

@@ -259,6 +252,24 @@ A standard point of vehicle telemetry. References to latitude and longitude impl
259252

260253
[Top][toc]
261254

255+
## Telemetry Error
256+
Error response for indicating failed telemetry data for the [Telemetry](#vehicle---telemetry) endpoint
257+
258+
| Field | Type | Field Description
259+
| -------------- | ------------------------------ | --------------------------------- |
260+
| `telemetry` | [Telemetry](#telemetry-data) | The failed telemetry data |
261+
| `error` | [Error Message][error-message] | Error message detailing the error |
262+
263+
Errors:
264+
265+
| `error` | `error_description` | `error_details`[] |
266+
| --------------- | ------------------------------------ | --------------------------------- |
267+
| `bad_param` | A validation error occurred. | Array of parameters with errors |
268+
| `missing_param` | A required parameter is missing. | Array of missing parameters |
269+
| `unregistered` | Vehicle is not registered | |
270+
271+
[Top][toc]
272+
262273
## Stops
263274

264275
The `/stops` endpoint allows an agency to register city-managed Stops, or a provider to register self-managed Stops.
@@ -342,3 +353,4 @@ If `stop_id` is specified, `GET` will return an array with a single stop record,
342353
[vehicle-states]: /general-information.md#vehicle-states
343354
[vehicle-events]: /general-information.md#vehicle-state-events
344355
[versioning]: /general-information.md#versioning
356+
[error-message]: /general-information.md#error-messages

0 commit comments

Comments
 (0)