unique-identifier-already-exists⚓︎

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/unique-identifier-already-exists",
    "type_documentation": "https://developers.invers.com/problems/unique-identifier-already-exists",
    "title": "Unique identifier already exists.",
    "status": 409,
    "detail": "…",
    "flow_id": "2e847e2e-6db1-4998-847e-2e6db1c99846"
}

Meaning⚓︎

This problem type occurs when trying to set the value of a unique identifying property to an existing value.

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 VIN: ‘38429DA427AB7C25’ already exists on a different vehicle.

You have specified to set the VIN of a vehicle to value 38429DA427AB7C25, but there is already a vehicle in your fleet with that VIN. Any unique VIN can only exist once in your fleet.

Possible solutions:

Check the VIN
Check if another vehicle already has the VIN
Check if there is a typo in the VIN