Which statement describes a 429 HTTP status in Stripe?

Which statement describes a 429 HTTP status in Stripe?

• A. 429 Too Many Requests: you breached the limits (100 reads per second live, 100 writes per second live, 25 per second in test mode).
• B. 200 OK.
• C. 401 Unauthorized.
• D. 503 Service Unavailable.

Answer: (A)

Rate limiting is what a 429 response signals. It means you’ve sent requests faster than Stripe allows, hitting the per-second limits designed to protect the API. Stripe enforces specific thresholds: 100 reads per second in live mode, 100 writes per second in live mode, and 25 requests per second in test mode. When you exceed those limits, you receive a 429 and should back off before retrying, preferably with exponential backoff and honoring any Retry-After guidance. The other statuses represent different conditions—200 means success, 401 means invalid or missing authentication, and 503 indicates a temporary Stripe-side outage. The statement that mentions 429 and those rate limits is describing this rate-limiting behavior.

Rate limiting is what a 429 response signals. It means you’ve sent requests faster than Stripe allows, hitting the per-second limits designed to protect the API. Stripe enforces specific thresholds: 100 reads per second in live mode, 100 writes per second in live mode, and 25 requests per second in test mode. When you exceed those limits, you receive a 429 and should back off before retrying, preferably with exponential backoff and honoring any Retry-After guidance. The other statuses represent different conditions—200 means success, 401 means invalid or missing authentication, and 503 indicates a temporary Stripe-side outage. The statement that mentions 429 and those rate limits is describing this rate-limiting behavior.