Skip to content

/problems/referenced-resource-not-found⚓︎

Problem

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

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/referenced-resource-not-found",
    "type_documentation": "https://developers.invers.com/problems/referenced-resource-not-found",
    "title": "A referenced resource cannot be found.",
    "status": 400,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs when the request references a resource that does not exist. Note that this only refers to resources that are not referenced via path parameters.

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

Validation of the ‘telematics_unit’ data failed: The telematics unit with ID ‘WP0ZZZ99ZTS392742’ is unknown to the cloud of the manufacturer of the telematics unit.

You are trying to add a new vehicle but the telematics unit ID in the request body is unknown to the cloud of the manufacturer of the telematics unit.

Possible solutions:

  • Make sure that the telematics unit ID is correct
Validation of the ‘telematics_unit’ data failed: The vehicle model with ID ‘01F627BM9AAMF396YZK2AGZFY6’ cannot be found.

The vehicle model referenced in the request’s body does not exist.

Possible solutions:

  • Make sure that the vehicle model ID is correct

  1. The flow_id is specific to each API call, so it will be different in your case. However, type, title and status will match your actual error response if you receive the error described on this page. ↩