Change in Rate Limit headers (X-RateLimit-Remaining and X-RateLimit-Reset)

API
1

Hi everyone,

I have a production application that relies on the Pipedrive API (both v1 and v2) and I’ve always used the rate limit headers, specifically:

  • X-RateLimit-Remaining
  • X-RateLimit-Reset

Up until last week, these headers were consistently present in all responses, and my application used them to manage requests and avoid hitting the rate limits.

However, starting this week my applications began failing because these headers are no longer being returned in the API responses.

The only place where I still see a reference to them is in the access-control-expose-headers, but the actual values for X-RateLimit-Remaining and X-RateLimit-Reset are missing.

Could you please clarify:

  • Was this change intentional (an implementation update)?
  • Or is this a temporary issue/bug with the API?

I’d like to know so I can either permanently adjust my code or handle it as a temporary workaround.

Thanks in advance!

2

Hey,

thank you for reporting this. It was a temporary issue that has now been resolved. The headers are back with actual values now.