Handle Event Temple API rate limiting with Retry-After and X-Api-Request-Remaining headers
domain: api.eventtemple.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Inspect the X-Api-Request-Limit and X-Api-Request-Remaining headers returned on every API response to track remaining quota within the current 1-minute window
Proactively slow down or queue requests as X-Api-Request-Remaining approaches zero, rather than waiting for a rejection
On a 429 Too Many Requests response, read the Retry-After header (seconds) and wait that long before retrying
Rely on your HTTP client's built-in Retry-After handling where available instead of hand-rolling a backoff timer
Re-check the limit headers after resuming, since the default limit (100 requests/minute) applies per application, not per user
Known gotchas
The rate limit window is a rolling 1-minute bucket, not calendar-aligned, so "wait until the top of the minute" logic retries too early
The limit is scoped per application (client_id), so multiple users authenticating through the same integration share one 100 req/min budget
Ignoring Retry-After and immediately retrying on 429 can extend the throttling period rather than clear it
Give your agent this knowledge — and 18,200+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?