OAUTH_REQUEST_EXPIRED

HTTP status: 400

The OAuth authorization request expired or was already used.

What it means

The consent step referenced an authorization request that is no longer pending — it expired (requests are held for 10 minutes) or was already approved or denied once. Authorization requests are strictly single-use.

Why it happens

• The consent page sat open for more than 10 minutes before a decision.
• The consent decision was submitted twice (double-click, page refresh after deciding, or a duplicated tab).
• The API's cache restarted between the authorization redirect and the consent decision.

How to fix it

• Start the connection again from your MCP client — a fresh request takes seconds.
• Approve or deny promptly once the consent page is open.

Example

Every non-2xx response uses the same envelope; path (when present) is the exact JSON path of the offending field, and requestId identifies the request in support conversations:

{
  "error": {
    "code": "OAUTH_REQUEST_EXPIRED",
    "message": "This authorization request has expired or was already used. Start the connection again from your MCP client.",
    "docsUrl": "https://useautomotion.com/docs/errors/oauth_request_expired"
  },
  "requestId": "req_0123456789abcdef0123456789abcdef"
}

Related errors

• OAUTH_INVALID_CLIENT — Unknown OAuth client or unregistered redirect URI.
• UNAUTHORIZED — The request is missing a valid API key.

See the error index for the full catalog and the API overview for envelope semantics.