Skip to content

Invalid Request

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

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

When you see this

The token request is malformed — it is missing a required parameter, includes an unsupported or duplicated parameter, or is otherwise malformed.

Common Causes

  • A missing required OAuth parameter (for example grant_type).
  • A duplicated or malformed parameter in the token request.
  • A request body that does not conform to the OAuth 2.0 token-endpoint format.

Response Example

{
  "error": "invalid_request",
  "error_description": "The token request is missing a required parameter or is otherwise malformed.",
  "error_uri": "https://docs.ankatech.co/errors/invalid_request",
  "type": "https://docs.ankatech.co/errors/invalid_request",
  "title": "Invalid Request",
  "status": 400,
  "detail": "The token request is missing a required parameter or is otherwise malformed.",
  "instance": "/api/v3/auth/token",
  "timestamp": 1730000000
}

Content-Type: application/json — not application/problem+json. RFC 6749 §5.2 defines the token endpoint's error response, and the Auth API emits that shape deliberately: the RFC 9457 members ride along for clients that read them, but no RFC 9457 media type or envelope is emitted on this endpoint. Switch on the status and the error member, never on the media type.

The Auth API carries no correlation member in the body: correlate through the X-Correlation-Id response header instead. See Error Index & Overview.

How to Resolve

  1. Review the OAuth 2.0 token request format in the Developer Hub Reference.
  2. Include all required parameters exactly once, with valid values.
  3. Re-submit the corrected token request.

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