Rate Limits and Backoff

This article provides shared retry and throttling guidance across runtime APIs.

Shared Limit Signals

• 429 is the primary rate and plan limit signal.
• 413 and 414 indicate payload or request-size constraints.
• 500 can appear in overage-related service impact scenarios.

Backoff Guidance

• Start with short retry delays for short-lived traffic increases.
• Increase delay with each retry attempt.
• Stop retrying on persistent failures and check usage and limits.
• Do not rely on Retry-After.

Operational Checks

• Verify app-level request volume.
• Verify monthly plan consumption.
• Verify payload and URL sizes.

Related Limits Articles

• Service Limits
• Authentication and Authorization
• Request and Response Conventions