internal-server-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/internal-server-error",
    "type_documentation": "https://developers.invers.com/problems/internal-server-error",
    "title": "Internal Server Error",
    "status": 500,
    "detail": "Internal Server Error occurred during request. Make sure to provide the 'flow_id' for troubleshooting or support requests.",
    "flow_id": "f5a05d3b-b39c-47e9-a05d-3bb39c97e986"
}

Meaning⚓︎

This problem type should never occur. If it does, an error has occurred within the INVERS API. In this case, INVERS will automatically be notified about the problem and our development team will start investigating the issue.

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

Internal Server Error occurred during request. Make sure to provide the ‘flow_id’ for troubleshooting or support requests.

You have sent a request and received an internal server error in response. This should not happen and you probably did not make any error.

Possible solutions:

Contact the INVERS support if the problem persists. Provide them the flow_id of your request