Folks:
Is it possible to implement proactive rate limiting via “leaky bucket” headers in the responses? I would really like to do that by injecting a delay before sending the request if needed rather than relying solely on getting a 429 response back when we’re hitting the API too hard…
If so, how would this be done? I’ve been playing around with the current .Net SDK and can’t seem to easily access the raw response headers.
I asked an AI about it and was told that such headers exist, but the example code it generated didn’t even compile. <deadpan>How shocking.</deadpan>
3 posts - 2 participants