Errors - Docket

Docket returns RFC 9457 problem documents for REST failures:

{
  "type": "https://clearthedocket.com/problems/unsupported_api_version",
  "title": "Unsupported API version",
  "status": 400,
  "code": "unsupported_api_version"
}

Branch on code. Do not branch on title or detail, and do not show either provider-owned string as your application error message.

Authorization errors

Signal	Meaning	Client action
`401`	The token is missing, invalid, expired, or its authority changed.	Stop and begin authorization again.
`403` with `WWW-Authenticate: Bearer error="insufficient_scope"`	The current token lacks the required scope.	Ask the person to approve the narrower required scope.
`404`	A resource may be absent or hidden from the caller.	Do not treat it as proof that the resource does not exist.

Client revocation, consent reduction, client disablement, user removal, and live grant reduction invalidate authority immediately. Do not retry a request by silently widening scopes.

Version errors

unsupported_api_version means a client asserted a version other than the current 0.1.0 contract. Omit Docket-Version to accept the current contract, or send Docket-Version: 0.1.0 exactly.

Read authentication behavior

Discover the authorization server and request only the scopes a client needs.