Skip to main content
Stableyard limits how many requests a caller can make in a time window. Responses report the quota that applies to them, so read the headers rather than hardcoding numbers.

Rate limit headers

A request can count against several limits at once, for example per app environment and per app. On a success, the headers describe the most constrained of those limits; on a 429, the limit that was exceeded. A response can omit the RateLimit-* headers, so do not treat a missing header as a missing limit.

Handle a 429

  1. Wait for Retry-After before sending the request again.
  2. Reuse the same Idempotency-Key when you retry a write. See Retrying safely.
  3. Spread the load. React to webhooks instead of polling every resource, and page through lists with their cursors.
Not every 429 is a rate limit. payment_option_limit_reached means too many options were created for one payment. See Errors.

Errors

Every error code and which ones to retry.

Idempotency

Retry a write without doing it twice.

Webhooks

Learn about changes without polling.

Environments

Base URLs and what is isolated between environments.