/problems/unknown-resource⚓︎
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/unknown-resource",
"type_documentation": "https://developers.invers.com/problems/unknown-resource",
"title": "The requested resource does not exist.",
"status": 404,
"detail": "…",
"flow_id": "3ec94dff-d9cb-4c5a-894d-ffd9cb2c5a4f"
}
Meaning⚓︎
This problem type occurs if a requested resource does not exist in the OneAPI. So, there is no matching path.
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 resource ‘/vehiclse’ does not exist.
You have specified a path in your request that does not exist.
Possible solutions:
- Check if your used path is valid
- Check if there is a typo in your path
- Check our API Reference to find the proper paths
Further reading⚓︎
-
The
flow_id
is specific to each API call, so it will be different in your case. However,type
,title
andstatus
will match your actual error response if you receive the error described on this page. ↩