Staying within someone else's limits.
WHAT TO READ FIRST
The documented limits, and how they are measured.
WHAT TO LOOK FOR IN RESPONSES
Headers stating the limit, remaining allowance and reset time.
WHAT TO DO WITH THEM
Pace yourself, rather than discovering the limit by exceeding it.
WHAT TO DO ON A LIMIT RESPONSE
Wait as instructed, then retry.
WHAT TO NEVER DO
Retry immediately Retry in a tight loop
WHY
It extends the block, and some providers suspend access.
WHAT TO BUILD
A limiter in your own client, below the provider's limit.
WHY BELOW
It leaves room for other processes using the same credential.
WHAT TO CONSIDER
That several of your own services may share one credential.
WHAT THAT REQUIRES
Coordinated limiting, not per-process.
WHAT REDUCES CONSUMPTION
Caching Batch endpoints Events instead of polling Requesting only needed fields
WHAT TO DO FOR LARGE BACKFILLS
Run them slowly, off-peak, with a separate credential if permitted.
WHY A SEPARATE CREDENTIAL
It prevents a backfill starving live traffic.
WHAT TO MONITOR
How close to the limit you run.
WHAT TO ALERT ON
Approaching it, before you hit it.
