FazerCards Glossary
Retry-After header
An HTTP response header (RFC 7231) telling the client how long to wait before retrying a request — used by FazerCards on HTTP 429 rate-limit responses (per-category ceilings: catalog 30/min, order-create 60/min, order-status 120/min, account 30/min, payments 15/min).
When FazerCards returns HTTP 429 (Too Many Requests), the Retry-After header carries the number of seconds the client should wait before retrying. A correctly-behaving client sleeps for at least that long — preferably with a small jitter so concurrent workers do not desync into the next window together — before the next request. Hammering after 429 makes it worse and can extend the throttling window. Production integrations cache catalog data locally (5–15 min TTL) instead of refetching it on every order to avoid hitting the 30/min catalog limit.
Key facts
- Value is in seconds.
- Per-category limits on the public API (see rate-limit term).
- Add jitter to avoid worker desync into the next window.
- Cookbook recipe: /docs/cookbook#rate-limit-handling.