Inconsistent x-daily-requests-left Value in Pipedrive API
Hi everyone,
I'm currently updating my WooCommerce to Pipedrive integration extension ( ). Since Pipedrive introduced a daily request limit, some of my users who perform a full WooCommerce sync to Pipedrive are hitting this limit.
To prevent their API keys from being blocked, I wanted to rely on the x-daily-requests-left value returned in the response headers. However, after multiple tests, I noticed that this value is quite inconsistent. While it generally decreases as API requests are made, I've observed cases where it increases unexpectedly or fluctuates up and down. In one instance, I even hit the 429 rate limit while x-daily-requests-left was still around 7500.
Am I missing something about how this limit is calculated? Is there a more reliable way to anticipate daily request usage?
Thanks in advance!
Tristan
Comments
-
Just following up on this post—after running a few more tests, I noticed something unusual.
x-daily-requests-leftstarts at 10,000, which doesn't match the theoretical minimum of 30,000 tokens. Throughout the day, the value decreases from 10,000 down to around 8,000–7,500 before I hit the 429 daily limit.This discrepancy makes it difficult to accurately track the remaining quota. Has anyone else experienced this, or does anyone know how Pipedrive actually calculates these limits? Any insights would be greatly appreciated!
0 -
Just following up on this post—after running a few more tests, I noticed something unusual.
x-daily-requests-leftstarts at 10,000, which doesn't match the theoretical minimum of 30,000 tokens. Throughout the day, the value decreases from 10,000 down to around 8,000–7,500 before I hit the 429 daily limit.This discrepancy makes it difficult to accurately track the remaining quota. Has anyone else experienced this, or does anyone know how Pipedrive actually calculates these limits? Any insights would be greatly appreciated!
0