WEBVTT

00:00:00.000 --> 00:00:06.000
Why can a connected service ask your website to slow down?

00:00:06.000 --> 00:00:13.000
Rate limits restrict how many requests are allowed within a defined scope.

00:00:13.000 --> 00:00:18.000
Understand the limit before retrying.
6 rate-limit checks.

00:00:18.000 --> 00:00:30.000
Read the provider limit
Different services define different limits and counting rules.
Provider rules · Counting period · Permitted request rate

00:00:30.000 --> 00:00:42.000
Check what is being counted
The restriction may apply to an account, client or resource.
Account or application · Client context · Relevant resource

00:00:42.000 --> 00:00:54.000
Recognise a 429 response
Too Many Requests indicates the client has exceeded an allowed rate.
HTTP 429 · Request rate · Temporary restriction

00:00:54.000 --> 00:01:06.000
Look for retry guidance
A Retry-After header may say when to try again.
Response headers · Retry guidance · Suitable waiting period

00:01:06.000 --> 00:01:18.000
Avoid repeated immediate retries
An uncontrolled loop can keep producing requests during the restriction.
Controlled retry · Reduced request rate · Useful error handling

00:01:18.000 --> 00:01:30.000
Review the user experience
Explain the delay and preserve the task appropriately.
Helpful feedback · Recorded failure · Managed recovery

00:01:30.000 --> 00:01:39.000
Your checklist
Read the provider limit · Check what is being counted · Recognise a 429 response · Look for retry guidance · Avoid repeated immediate retries · Review the user experience

00:01:39.000 --> 00:01:47.000
Follow the service guidance and avoid an uncontrolled retry loop.
jerseyweb.je