Skip to content
einvoicing.dev

Problems·HTTP 404

not-found

No such resource.

What it means

Nothing exists at this path, or the resource belongs to another account. The two cases look the same, so ids cannot be probed.

What to do

Check the path and the id. GET /v1/keys lists this account's keys.

Example

Sent as application/problem+json (RFC 9457). Branch on type, which is stable. Never branch on title or detail, which are prose and may change.

Exampleapplication/problem+json
{  "type": "https://www.einvoicing.dev/problems/not-found",  "title": "No such resource.",  "status": 404,  "detail": ""}

Returned by

All problem types

Every error the API can return, with what to do about each.

API reference

Every operation, its parameters and the errors it can answer with.