Skip to main content

invalid_request

Common cases:
  • Required query parameter omitted (e.g. GET /v1/notes without projectId).
  • Enum field given an unknown value (e.g. ?status=BOGUS against /v1/posts).
  • Date filter with the wrong format (?dateFrom=15/05/2026 — must be YYYY-MM-DD).
  • A request body fails validation on a write endpoint.
The error envelope’s details field, when present, names the offending parameter:
To recover, fix the malformed input and retry. The request did not have side effects on the server — invalid_request is rejected before any write would have happened. On the MCP surface, invalid_request also covers confirmation-token failures on the two-phase tools: details.reason is confirmation_invalid (the subject changed since the proposal, or the token belongs to a different action) or confirmation_expired (past the ~5-minute TTL). Recover by calling the tool again without a token to get a fresh proposal — see MCP tools § Two-phase confirmation.