Skip to main content

​
Common REST statuses

  • 400 for malformed pagination cursors (INVALID_CURSOR)
  • 401 for missing or invalid credentials
  • 403 for keys that do not have access to the requested operation
  • missing or inaccessible stats IDs are reported in response metadata rather than as 404
  • 422 for validation failures (VALIDATION_ERROR), including invalid parameter combinations such as passing both cursor and since to the partner feed
  • 429 for rate limiting
Each API key has a request allowance. The default is 1000 requests, replenished in full one hour after the previous replenishment. Exhausting the allowance returns 429 with code RATE_LIMITED and, when available, a Retry-After header. Production limits vary by account or environment.

​
Common MCP failures

  • missing MCP credentials
  • invalid API key
  • invalid OAuth access token or audience mismatch
  • API key without access to the requested operation
  • OAuth token without a supported Centaur MCP scope
  • invalid tool arguments
MCP OAuth failures include WWW-Authenticate metadata pointing to the protected resource metadata URL. Scope failures can include insufficient_scope; invalid or wrong-audience tokens can include invalid_token.

​
Operational guidance

  • Log and preserve requestId from REST failures when asking for support.
  • Prefer explicit time bounds and limits when an agent is exploring large result sets.
  • If a response is narrower than expected, check the echoed applied bounds and remember that some rows can be silently suppressed by access or eligibility rules.
  • Use the generated API reference for endpoint-specific error examples and response schemas.
Last modified on August 10, 2026