Error reference

rate_limit_exceeded

The token bucket is exhausted (per-key for REST, per-user for MCP).

HTTP 429rate_limitedRetryable0 credits

HTTP 429error.type = rate_limited

How to fix it

Honour Retry-After and back off with jitter. The SDK does this automatically.

Example response

429 rate_limited

// HTTP 429
{
  "error": {
    "type": "rate_limited",
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded. Retry after 7 seconds.",
    "param": null,
    "requestId": "req_…",
    "creditsCharged": 0,
    "retryable": true,
    "docUrl": "https://scoutingapi.com/docs/errors/rate_limit_exceeded"
  }
}

This error is free

Like every ScoutingAPI error, rate_limit_exceeded returns creditsCharged: 0. You are never billed for a failed, empty, blocked or not-found call.

See the full error catalog or the response envelope. The canonical URL for this page is https://scoutingapi.com/docs/errors/rate_limit_exceeded.