not_found

The requested resource does not exist — or it exists but belongs to a different company than your credential, which is deliberately indistinguishable.

Example response

HTTP/1.1 404 Not Found
Content-Type: application/problem+json
X-Request-ID: 7d1e9c2a-3b4f-4c5d-8e6f-9a0b1c2d3e4f

{
  "type": "https://docs.talero.dk/problems/not_found",
  "title": "Resource not found",
  "status": 404,
  "detail": "Invoice not found",
  "code": "not_found"
}

Common causes

• The ID in the URL is wrong, or the resource was deleted.
• The resource belongs to another company. Cross-company access always reads as 404, never 403, so IDs cannot be probed.
• The URL path is misspelled or missing the /api/v1 prefix.
• An ID from a test or staging dataset is being used against production data.

How to fix it

• Verify the ID comes from a listing or creation response made with the same company credential.
• Handle deletions gracefully: a resource that existed yesterday may legitimately be gone today.
• Check the path against the API reference.

If the problem persists, contact [email protected] and quote the X-Request-ID header from the failing response.