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 7807 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

{
  "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": "/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. 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.