resource-not-found⚓︎

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/third-party/resource-not-found",
    "type_documentation": "https://developers.invers.com/problems/third-party/resource-not-found",
    "title": "An associated third-party resource does not exist.",
    "status": 404,
    "detail": "…",
    "flow_id": "e1b8e6dd-7df4-435c-b8e6-dd7df4835c4d"
}

Meaning⚓︎

This type of problem occurs when a required resource at a third-party API no longer exists.

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⚓︎

The associated vehicle does not exist at the Mercedes-Benz API.

The INVERS OneAPI tried to perform an operation via the Mercedes-Benz API but the telematics unit ID (in this case, the VIN, i.e. the vehicle identification number) is unknown to the Mercedes-Benz API.

This can happen when the vehicle is removed directly via the Mercedes-Benz API without archiving the corresponding vehicle in the INVERS OneAPI.

Possible solutions:

Make sure you only remove vehicles via the INVERS OneAPI