x-daily-request-left acting weirdly

API
1

As shown in the series of calls below, the header x-daily-requests-left is sometimes decreasing but also increasing again, whereas x-daily-ratelimit-token-remaining consistently decreases by 5 tokens per POST request, as expected.

I would like to clarify:

  • Is this behavior (increase/decrease of x-daily-requests-left) normal?

  • What is the exact meaning of this header compared to x-daily-ratelimit-token-remaining?

  • Should I rely only on x-daily-ratelimit-token-remaining for calculating my usage?

Logs for reference:

(⎈|eks-eu-west-1-stg:N/A)➜  ~ curl -v -X POST ‘https://api.pipedrive.com/api/v2/persons?limit=1&api_token=xxx’ 2>&1 | grep ‘x-’
< strict-transport-security: max-age=31536000; includeSubDomains
< x-content-type-options: nosniff
< x-correlation-id: 43c74091-b9f9-4321-84ad-26cecca6ff6a
< x-daily-ratelimit-token-limit: 1620000
< x-daily-ratelimit-token-remaining: 1329007
< x-daily-requests-left: 533
< x-ratelimit-limit: 80
< x-ratelimit-remaining: 79
< x-ratelimit-reset: 2
< x-xss-protection: 1; mode=block

(⎈|eks-eu-west-1-stg:N/A)➜  ~ curl -v -X POST ‘https://api.pipedrive.com/api/v2/persons?limit=1&api_token=xxx’ 2>&1 | grep ‘x-’
< strict-transport-security: max-age=31536000; includeSubDomains
< x-content-type-options: nosniff
< x-correlation-id: 74baaefd-5cda-41d2-90ca-b0ca5207845b
< x-daily-ratelimit-token-limit: 1620000
< x-daily-ratelimit-token-remaining: 1329002
< x-daily-requests-left: 478< x-ratelimit-limit: 80
< x-ratelimit-remaining: 79< x-ratelimit-reset: 2
< x-xss-protection: 1; mode=block

(⎈|eks-eu-west-1-stg:N/A)➜  ~ curl -v -X POST ‘https://api.pipedrive.com/api/v2/persons?limit=1&api_token=xxx’ 2>&1 | grep ‘x-’
< strict-transport-security: max-age=31536000; includeSubDomains
< x-content-type-options: nosniff
< x-correlation-id: 1bd6e7da-b9ec-4c4d-ab04-c261069c9c5f
< x-daily-ratelimit-token-limit: 1620000
< x-daily-ratelimit-token-remaining: 1328997
< x-daily-requests-left: 488
< x-ratelimit-limit: 80< x-ratelimit-remaining: 77
< x-ratelimit-reset: 2< x-xss-protection: 1; mode=block

(⎈|eks-eu-west-1-stg:N/A)➜  ~ curl -v -X POST ‘https://api.pipedrive.com/api/v2/persons?limit=1&api_token=xxx’ 2>&1 | grep ‘x-’
< strict-transport-security: max-age=31536000; includeSubDomains
< x-content-type-options: nosniff
< x-correlation-id: 8fe024fe-4175-4f89-ade5-800fb961abc0
< x-daily-ratelimit-token-limit: 1620000
< x-daily-ratelimit-token-remaining: 1328992
< x-daily-requests-left: 507
< x-ratelimit-limit: 80< x-ratelimit-remaining: 79
< x-ratelimit-reset: 2
< x-xss-protection: 1; mode=block
(⎈|eks-eu-west-1-stg:N/A)➜  ~ curl -v -X POST ‘https://api.pipedrive.com/api/v2/persons?limit=1&api_token=xxx’ 2>&1 | grep ‘x-’
< strict-transport-security: max-age=31536000; includeSubDomains
< x-content-type-options: nosniff
< x-correlation-id: b1b51a6a-21cd-4df6-95fe-ab19c3c0e4b5
< x-daily-ratelimit-token-limit: 1620000
< x-daily-ratelimit-token-remaining: 1328987
< x-daily-requests-left: 498< x-ratelimit-limit: 80
< x-ratelimit-remaining: 79< x-ratelimit-reset: 2
< x-xss-protection: 1; mode=block

(repeated calls show token-remaining decreasing steadily, but requests-left sometimes increases again)

2

Hello!

In short, you should rely on x-daily-ratelimit-token-remaining for calculating your API usage.

The x-daily-requests-left is an older legacy header and is not enforced even if it reaches 0 so you can safely ignore its value.

1 Like