credential_scope: This scoped credential cannot call that route or object

A scoped credential (dsc1.hook.…, dsc1.delegator.… or dsc1.payee.…) reaches only the routes of its kind, and only the budget, stream or payee it was minted for. The route or object of this request is outside that scope, or does not exist: both answer the same way, so the answer says nothing about other budgets. Nothing was billed and nothing changed.

What to do

On the wire

HTTP 403, error type authentication_error.

{
  "error": "credential_scope",
  "errorDetail": {
    "type": "authentication_error",
    "code": "credential_scope",
    "message": "a hook credential may not call POST /owner/v1/streams/:id/revoke on this object (fail closed)",
    "param": null,
    "doc_url": "…/errors/credential_scope.md",
    "fix": "this scoped credential cannot call this route or object; use the owner token, or mint a credential of the needed kind for the object"
  }
}

Every client gets errorDetail, with or without Dynamo-Error-Detail: 1.

On the multi-tenant hosted tier, the front door refuses a scoped credential outside its own surface (/owner/ and, for a payee credential, /payee/ plus POST /plugin/v1/meter; for the others, /plugin/) before the core sees it, with the same code and a shorter message naming only the path's first two segments, for example "a hook credential cannot call POST /payee/v1/…". The core checks the object as above.

An unknown or revoked scoped credential answers the route's own 401, the same as a wrong owner token. On the multi-tenant hosted tier the front door answers it with 401 unauthorized ("the credential does not resolve to exactly one tenant (fail closed)").

See all error codes.