Closed alexlatchford closed 7 years ago
Hey @robholland any news on this one?
@alexlatchford The error isn't time based, you are being limited to 5 concurrent requests, so we can't give you an indication of when you'll be able to connect again. You'll need to manage that on your side.
I've filed a PR to fix our return code, sorry about that.
I'm trying to respect the Rate Limiting defined in the docs: https://clearbit.com/docs#rate-limiting
Catching the error thrown on a
rate_limit
call I get:There doesn't seem to be any easy access to the response headers here, any chance I could ask you to add this please. I'll just use an exponential backoff (maxing out at 8s) for now but would be great to get access to the
Retry-After
header in particular to optimise the wait period.Also looks like either the API is throwing the wrong code or the client lib is transforming it to 400, the docs suggest it should be returning a 429.
Thanks, Alex