Otonomo uses HTTP response codes to indicate the completion status of an API call.
There are three main groups of response codes:
- 2xx success response codes: indicate a successful API call. May also indicate a call for which no new data exists.
- 4xx error status codes indicate an error related to the information provided on the API call (e.g., a required parameter is missing)
- 5xx error status codes indicate Otonomo server errors.
Error code table:
|Response code||Possible reasons|
|200||1. The API call is successful|
2. If not data is returned, then one or more mandatory attributes are not available
|204||No new data is available|
|400||Bad request. This error is likely the result of a wrong or missing parameter on an API call. This response code usually includes a body header that indicates the bad parameter (key) and its related issue (value).|
|401||User credentials or token are not valid. May also result from a lack of driver consent on the OEM side. e.g. when a driver has revoked consent directly on the OEM portal.|
|403||User is not authorised to query the requested resource. May also result from lack of consent on the OEM side. e.g. when a driver has revoked consent directly on the OEM portal.|
|404||Bad URL The resource pointed by the URL does not exist.|
|429||Too many requests. This error is issued when the user has exceeded the API rate limitations. It may also originate from a rate limitation on the data provider side.|
|500||Internal server error.|
Updated almost 3 years ago