not_found

HTTP status

404

Title

Not found

Code

not_found

What it means

No such resource. A resource that belongs to another organisation, and an ID with the wrong prefix for the route, answer the same way.

It is also the catch-all of status 404: an error of that status that has no more specific code answers with this one.

What to do

Check the ID, and that the key is for the organisation and mode (live or test) that owns it.

Example

Errors are RFC 9457 problem details, sent as application/problem+json. See Errors for every field.

{
  "type": "https://docs.furniops.com/errors/not_found",
  "title": "Not found",
  "status": 404,
  "code": "not_found",
  "detail": "An explanation of this occurrence.",
  "request_id": "req_…",
  "doc_url": "https://docs.furniops.com/errors/not_found"
}

Operations that answer it

• PATCH /v1/agents/{agent}
• GET /v1/agreements/{kind}
• POST /v1/agreements/{kind}/acceptances
• GET /v1/assistant/conversations/{conversation}
• DELETE /v1/assistant/conversations/{conversation}
• POST /v1/assistant/conversations/{conversation}/turns
• PATCH /v1/assistant/memories/{memory}
• DELETE /v1/assistant/memories/{memory}
• POST /v1/audit-events/{id}/undo
• GET /v1/billing/credits/purchases/{purchase}
• GET /v1/brand/claims/{id}
• POST /v1/brand/claims/{id}/check
• POST /v1/brand/claims/{id}/withdraw
• GET /v1/catalogue/publication-runs/{id}
• GET /v1/exports/{id}
• GET /v1/mappings/{id}
• POST /v1/mappings/{id}/confirm
• GET /v1/match-pairs/{id}
• POST /v1/match-pairs/{id}/dismiss
• POST /v1/match-pairs/{id}/merge
• POST /v1/match-pairs/{id}/reopen
• GET /v1/media/{id}
• GET /v1/merges/{id}
• POST /v1/merges/{id}/undo
• GET /v1/products/{id}
• GET /v1/proposals/{id}
• POST /v1/proposals/{id}/accept
• POST /v1/proposals/{id}/reject
• GET /v1/request-logs/{id}
• GET /v1/runs/{id}
• GET /v1/source-probes/{id}
• GET /v1/sources/{id}
• PATCH /v1/sources/{id}
• GET /v1/sources/{id}/categories
• POST /v1/sources/{id}/categories
• PUT /v1/sources/{id}/credentials
• DELETE /v1/sources/{id}/credentials
• POST /v1/sources/{id}/inbound-address/rotate
• GET /v1/sources/{id}/inbound-messages
• GET /v1/sources/{id}/mappings
• POST /v1/sources/{id}/records
• POST /v1/sources/{id}/replay
• GET /v1/sources/{id}/runs
• POST /v1/sources/{id}/runs
• POST /v1/sources/{id}/test
• POST /v1/sources/{id}/uploads
• GET /v1/uploads/{id}
• POST /v1/uploads/{id}/complete
• POST /v1/variants/{id}/checks
• GET /v1/vendor-profiles/{id}
• GET /v1/webhook-endpoints/{id}
• PATCH /v1/webhook-endpoints/{id}
• DELETE /v1/webhook-endpoints/{id}
• GET /v1/webhook-endpoints/{id}/deliveries
• GET /v1/webhook-endpoints/{id}/deliveries/{delivery}
• POST /v1/webhook-endpoints/{id}/deliveries/{delivery}/resend
• POST /v1/webhook-endpoints/{id}/recover
• POST /v1/webhook-endpoints/{id}/rotate-secret
• POST /v1/webhook-endpoints/{id}/test