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
Copy file name to clipboardExpand all lines: agency/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,10 +50,10 @@ Path Params:
50
50
51
51
If `device_id` is specified, `GET` will return 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:
> Since versioning was not available from the start, the following APIs provide a fallback version if the `Accept` header is not set as specified above:
200
-
> - The `provider` API must respond as if version `0.2` was requested.
201
-
> - The `agency` API must respond as if version `0.3` was requested.
202
-
> - The `policy` API must respond as if version `0.4` was requested.
200
+
>
201
+
> * The `provider` API must respond as if version `0.2` was requested.
202
+
> * The `agency` API must respond as if version `0.3` was requested.
203
+
> * The `policy` API must respond as if version `0.4` was requested.
203
204
204
205
If an unsupported or invalid version is requested, the API must respond with a status of `406 Not Acceptable`. If this occurs, a client can explicitly negotiate available versions.
205
206
@@ -224,4 +225,4 @@ The client can use the returned value verbatim as a version request in the `Acce
0 commit comments