not_found: Not found
No budget, stream, approval or reservation with that id exists on this deployment, or no other object the route names (for example an account, a key, a task, a recourse case or an adoption).
It also answers a route whose feature this deployment does not run: the single sign-on routes when single sign-on is not configured, and the Connect webhook (POST /payee/v1/connect/webhook) when the credit card rail's Connect is not configured.
What to do
- Check the id. Ids are scoped to the deployment that issued them.
On the wire
HTTP 404, error type not_found.
On the owner-api routes on the always-detailed list every client receives the body below: the 1.4.0 control, approval, revenue, alert, log and scheduler routes, the 1.5.0 authority and evidence routes, the 1.6.0 webhook, main-switch, developer and payment authorization, receipt and record routes, the 1.7.0 scoped-credential and terms routes, and the 1.8.0 fee ledger and child adoption routes. On every other owner route (the original budget and stream routes, the 1.7.0 consumes, payment-authority and budget adoption routes, and the 1.8.0 tasks, policies, recourse and organisation routes) the body is {"error": "not found", "detail": "…"}, and errorDetail is added only when the request sends Dynamo-Error-Detail: 1:
{
"error": "not found",
"detail": "…",
"errorDetail": {
"type": "not_found",
"code": "not_found",
"message": "…",
"param": null,
"doc_url": "…/errors/not_found.md",
"fix": "check the id; budgets and streams are scoped to this deployment"
}
}
Some routes answer in their own shape, with or without the header:
- the ramp, human payment and developer (top-up, widget, budget link, portal, test fixture) routes always add
errorDetailto{"error": "not found", …}; - the economic account routes answer
{"error": "not_found", "errorDetail": {…}}; a client pinned before 1.8.0 (or, on a single-tenant core, naming no version) gets adoc_urlending inerrors/errors/not_found.md, which forwards to this page; - the payee terms, task and recourse routes (for an object they do not hold) and the single sign-on routes send
{"error": "not_found", "detail": "…"}, with noerrorDetail; the Connect webhook answers{"error": "not_found"}; - the plugin wire answers an unknown stream with 404
{"error": "unknown stream"}, with no code.
On the multi-tenant hosted tier the front door answers an unknown key itself (POST /tenant/v1/keys/{id}/revoke) with {"error": "not_found", "errorDetail": {…}}, whose fix reads "check the id; ids are scoped to your tenant".
See all error codes.