Recurly API Rate Limit (429 Too Many Requests)

How to fix it

Try these in order — the most common fix is first.

1. 1. Back off and retry

   1. Use exponential backoff on 429
   Did this fix it? Yes No

2. 2. Cut request volume

   1. Cache account data, use pagination and filters, prefer webhooks for changes
   Did this fix it? Yes No

3. 3. Check the limit headers

   1. Read rate-limit headers in responses to pace calls
   Did this fix it? Yes No

Symptoms

API calls return 429.

Why it happens

• Burst traffic or loops
• Polling instead of webhooks

This guide also covers

• recurly api rate limit
• recurly 429

Other Recurly errors

• How to Cancel Recurly Subscription
• Recurly Payment Declined or Transaction Failed
• Recurly 3D Secure (SCA) Declines on Renewals
• Recurly Webhook Not Received or Missed
• Recurly Refund Creates a New Invoice (Credit Invoice)
• Recurly NetSuite Invoice and Payment Sync Errors
• Recurly QuickBooks Online Integration Errors
• Recurly Admin Console Logs Out Automatically