Skip to content

Tenant Selection Required

URI: https://docs.ankatech.co/errors/tenant_selection_required
HTTP Status: 400 Bad Request

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

When you see this

The credentials are valid for more than one tenant, so the token request is ambiguous. You must specify which tenant to authenticate against.

Common Causes

  • A user who administers multiple tenants authenticating without specifying a tenant.
  • Omitting the tenant selector when the identity maps to several tenants.
  • A token request that cannot be resolved to a single tenant.

Response Example

{
  "type": "https://docs.ankatech.co/errors/tenant_selection_required",
  "title": "Tenant Selection Required",
  "status": 400,
  "detail": "The credentials map to multiple tenants. A tenant must be selected explicitly.",
  "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. Include the tenant selector (for example a tenant_id) in the token request.
  2. Choose the specific tenant you intend to authenticate against.
  3. Re-submit the token request with the tenant specified.

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