error⚓︎

Problem

This is a description of a specific error response that you can receive when using the INVERS OneAPI via REST.¹

Check out our API Basics to learn more about the basic structure of all error responses and to find out how you should handle them.

{
    "type": "/problems/telematics-unit/error",
    "type_documentation": "https://developers.invers.com/problems/telematics-unit/error",
    "title": "An error occurred on the telematics unit",
    "status": 500,
    "detail": "…",
    "flow_id": "f5a05d3b-b39c-47e9-a05d-3bb39c97e986"
}

Meaning⚓︎

This problem type occurs when an error occurrs on the telematics unit.

Details⚓︎

Use the error response’s type property to handle specific errors and exception handling within your application. It’s comparable to an error code.
The detail property contains additional, more human-readable information about the problem or error. This is explanatory text and you should not have any exception handling and error handling code depend on it, as it may change.

Detail examples⚓︎

The following examples are typical texts which you might receive in the error response’s detail property. Note that it is not a complete list of all possible cases. Therefore expect to receive error responses with a detail property value not listed below.

Example problem details⚓︎

An error occurred on the CloudBoxx device. The requested CloudBoxx resource state is incomplete or busy.

Possible solutions:

Reset or reboot the telematics unit
Update the telematics unit firmware
Contact the INVERS support if the problem persists. Provide them the flow_id of your request