invalid-credentials⚓︎

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/invalid-credentials",
    "type_documentation": "https://developers.invers.com/problems/invalid-credentials",
    "title": "The credentials are invalid.",
    "status": 401,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs if the token used for authentication is invalid.

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.

The access token is invalid, expired, or cannot be parsed.

You have specified a token in your request, but the token is not valid.

Possible solutions:

Check if your token has expired. If yes, retrieve a new token and try again
Check if there are any additional or unwanted characters besides the token in your Authorization header
Check if you have transmitted the complete token

The access token is missing or was not submitted correctly.

You have not submitted the token correctly.