org_not_found: The organisation does not exist
org_not_found is one of the declared organisation refusal reasons, but this release never sends it. An organisation id that does not exist on this deployment answers 404 not_found on the organisation routes (/owner/v1/orgs/{id} and the routes below it). A member acting outside its organisation gets 403 role_forbidden, the same answer as for an absent object.
What to do
- If you handle organisation errors in code, treat
org_not_foundlikenot_found: check the organisation id withGET /owner/v1/orgs.
On the wire
If it is ever sent, it takes the shape of the other organisation reasons: HTTP 409, error type state_error, body {"error": "state", "reason": "org_not_found", "detail": "…"}, with errorDetail (param org) only when the request sends Dynamo-Error-Detail: 1. The 404 not_found for an unknown organisation is {"error": "not found", "detail": "…"}, with errorDetail under the same condition.
See organisations and roles and all error codes.