Resource Not Found
resource-not-found
| Type URI | https://docs.panquest.com/qfx/problems/resource-not-found |
|---|---|
| Status | 404 Not Found |
| Title | Resource Not Found |
| Members of its own | issues |
| Belgif REST guide | urn:problem-type:belgif:resourceNotFound |
When
The path names something that does not exist: a collection, an index, a document, a comment, an import, a role, a permission, a storage location or assignment, or a queue. The entry of issues names the path parameter that does not resolve. A path the API does not have at all gets this type too, without issues. Something the body, a query or a header names that does not exist is a bad-request instead.
What to do
Check the identifier the entry of issues names. Sent again unchanged, the request gets the same answer until the resource exists.
Example
HTTP/1.1 404 Not Found
Content-Type: application/problem+json
Content-Language: en
{
"type": "https://docs.panquest.com/qfx/problems/resource-not-found",
"title": "Resource Not Found",
"status": 404,
"detail": "Document not found",
"instance": "urn:uuid:3f1c2a0e-7d4b-4c55-9a2e-5b8f0c1d2e3f",
"parameters": {
"collection-name": "INVOICES",
"document-id": "B6E604029DA47343E5879E3C317FCC36E0E212CB"
},
"issues": [
{
"detail": "Document not found",
"in": "path",
"name": "document-id",
"value": "B6E604029DA47343E5879E3C317FCC36E0E212CB"
}
]
}