Skip to main content

Common REST statuses

  • 400 for malformed cursors or invalid query combinations
  • 401 for missing or invalid credentials
  • 403 for keys that do not have access to the requested operation
  • 404 for missing trader or asset subjects on stats reads
  • 422 for validation failures
  • 429 for rate limiting

Common MCP failures

  • missing MCP credentials
  • invalid partner API key
  • partner API key without access to the requested operation
  • invalid tool arguments

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 April 14, 2026