Skip to content

Access Denied

URI: https://docs.ankatech.co/errors/access_denied
HTTP Status: 403 Forbidden

This error also corresponds to the RFC 6749 OAuth 2.0 error code access_denied of the same name. The RFC 7807 type suffix uses the identical underscore form so the two identifiers match.

When you see this

The authorization request was denied. The resource owner or authorization server refused to grant the requested access.

Common Causes

  • The resource owner declining to authorize the request.
  • A policy at the authorization server refusing the grant.
  • A request that does not satisfy the conditions required to authorize access.

Response Example

{
  "type": "https://docs.ankatech.co/errors/access_denied",
  "title": "Access Denied",
  "status": 403,
  "detail": "The authorization request was denied.",
  "instance": "/oauth/token",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

Content-Type: application/problem+json — the response follows RFC 7807 Problem Details.

How to Resolve

  1. Confirm the request is permitted for the resource owner and client.
  2. Address any policy condition that caused the denial.
  3. Re-attempt authorization once the request is permitted.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.