API Rate Limiting Explained: What a 429 Response Means

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

1. 1

   Step 1: Read the provider limit

   0:18

   Different services define different limits and counting rules.

   On-screen labels: Provider rules; Counting period; Permitted request rate.

2. 2

   Step 2: Check what is being counted

   0:30

   The restriction may apply to an account, client or resource.

   On-screen labels: Account or application; Client context; Relevant resource.

3. 3

   Step 3: Recognise a 429 response

   0:42

   Too Many Requests indicates the client has exceeded an allowed rate.

   On-screen labels: HTTP 429; Request rate; Temporary restriction.

4. 4

   Step 4: Look for retry guidance

   0:54

   A Retry-After header may say when to try again.

   On-screen labels: Response headers; Retry guidance; Suitable waiting period.

5. 5

   Step 5: Avoid repeated immediate retries

   1:06

   An uncontrolled loop can keep producing requests during the restriction.

   On-screen labels: Controlled retry; Reduced request rate; Useful error handling.

6. 6

   Step 6: Review the user experience

   1:18

   Explain the delay and preserve the task appropriately.

   On-screen labels: Helpful feedback; Recorded failure; Managed recovery.

Common questions

Go further