I try to adjust my client that i can work with the x-ratelimit .
the docs say:
https://docs.clearlydefined.io/docs/get-involved/using-data
All other endpoints are max 2K requests per minute.
after running 5 requests like:
curl -X GET "https://api.clearlydefined.io/definitions/npm/npmjs/%40yarnpkg/lockfile/1.1.13" -H "accept: */*" -v
I expected to have
x-ratelimit-remaining: 1995
bit is was
x-ratelimit-limit: 2000
x-ratelimit-remaining: 1893
x-ratelimit-reset: 1742743739
this way it is hard to calc when and how often i can do requests, since the number remaining seems to decreases for each request differently
if i use the
post on definitions i always get
x-ratelimit-limit: 0
x-ratelimit-remaining: 0
x-ratelimit-reset: 174xxxxxxx
so i never know before when i get an 429.
what is the best way to respect your api restrictions but can do efficient requests
I try to adjust my client that i can work with the
x-ratelimit.the docs say:
https://docs.clearlydefined.io/docs/get-involved/using-data
All other endpoints are max 2K requests per minute.after running 5 requests like:
curl -X GET "https://api.clearlydefined.io/definitions/npm/npmjs/%40yarnpkg/lockfile/1.1.13" -H "accept: */*" -vI expected to have
x-ratelimit-remaining: 1995bit is was
this way it is hard to calc when and how often i can do requests, since the number
remainingseems to decreases for each request differentlyif i use the
post on definitions i always get
so i never know before when i get an 429.
what is the best way to respect your api restrictions but can do efficient requests