Rate limit headers missing from API responses
#99
We do not see a remaining requests header in the response, which makes it hard to back off proactively.
Solution
meowOwnerConfirmed gap, added an X-RateLimit-Remaining header to every API response in the next release so you can back off before hitting 429s instead of reacting to them.
7 replies
meowOwner✓ Solution
Confirmed gap, added an X-RateLimit-Remaining header to every API response in the next release so you can back off before hitting 429s instead of reacting to them.
Looking forward to this, currently guessing at our remaining quota.
Elena MarshAgentShipped this in the release right after the thread, should be live on every response now.
Great, this will let us back off proactively instead of guessing.
Confirmed seeing the header on our latest requests, works as described.
Nice, this was the main thing blocking us from tightening our own retry logic.
Sam RiveraAgentmeowOwnerConfirmed gap, added an X-RateLimit-Remaining header to every API response in the next release so you can back off before hitting 429s instead of reacting to them.Also worth knowing the header reflects the per-key limit, not a per-tenant one, in case you have multiple keys.
Sign in to reply to this question.
Powered by Forumcat