Handle PrizePicks API errors and rate limits.

The error envelope

HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json

{ "error": { "code": "RATE_LIMIT_EXCEEDED", "message": "Too many requests. Try again after the current minute." } }

Every code and what to do

Code casing differs between the authentication layer and the data layer, so compare exact strings. Successful authenticated responses include X-RateLimit-Remaining with the monthly requests left.

How limits are counted

Both limits are per account, shared across every key. The month is the UTC calendar month; the minute is the UTC calendar minute. A request is counted once its key authenticates, before parameter validation, so 400 and 503 responses still use allowance. The public demo endpoints are not metered.

A retry policy that respects the codes

async function withRetry(call, { maxAttempts = 4 } = {}) {
  for (let attempt = 1; ; attempt++) {
    try {
      return await call();
    } catch (err) {
      const retryable = err.code === "RATE_LIMIT_EXCEEDED" || err.status === 503;
      if (!retryable || attempt >= maxAttempts) throw err; // 400/401/403/monthly quota: stop
      const retryAfter = Number(err.retryAfter);
      const base = Number.isFinite(retryAfter) && retryAfter > 0 ? retryAfter * 1000 : 2 ** attempt * 1000;
      await new Promise((r) => setTimeout(r, base + Math.random() * 1000)); // jitter
    }
  }
}

This expects errors shaped like the ApiError in the JavaScript guide. It caps attempts, adds jitter so several workers do not retry in lockstep, and never retries a monthly-quota or authentication failure.

Spend fewer requests

• Use limit=200 when you read whole boards.
• Filter by league and stat on the server instead of downloading everything.
• Poll /changes with a saved cursor rather than re-reading every projection.
• Cache shared responses on your backend; never fetch per page view.
• Validate parameters locally before sending, since rejected requests still count.

PrizePicks API is an independent data service. It is not affiliated with or endorsed by PrizePicks. Observations, completeness, and freshness are separate claims; consult source status before relying on a stored line.