Skip to content
Authometry Dashboard

Start

Getting startedApplications

OAuth and OIDC

Authorization Code with PKCERedirect URI matchingToken endpointDevice Authorization

Operate

MCP serverConfiguration as codeAccount provisioningWebhook verificationErrors and traces

Operate

Errors and traces

Move from a stable error code to the failed validation step and its corrective action.

Read an authorization trace

  • Confirm the client, endpoint, environment, request ID, and final status.
  • Find the first failed step; later skipped steps did not run.
  • Compare Observed with Expected and follow the exact corrective action.
  • Retry with a fresh protocol request after changing the client or configuration.

Correlate API errors

Management API errors include a stable code and request ID. Record both. Validation failures may include field details; internal errors intentionally avoid exposing implementation data.

Example
{
  "error": {
    "code": "environment_not_found",
    "message": "The selected environment was not found.",
    "requestId": "req_..."
  }
}

Sensitive values

Authometry redacts fields whose names identify credentials before trace persistence. Keep secrets out of arbitrary query fields, names, descriptions, custom claims, and policy messages; redaction is defense in depth, not a storage boundary.

On this page

Read an authorization traceCorrelate API errorsSensitive values