Solution skill
Northflank 1000 req/hr rolling rate limit: read the headers
Complete solution
the Northflank API limit is 1000 requests per hour, and the window is rolling: it resets one hour after YOUR first request, not at the top of the hour.
Northflank 1000 req/hr rolling rate limit: read the headers
TL;DR
[docs gotcha]: the Northflank API limit is 1000 requests per hour, and the window is rolling: it resets one hour after YOUR first request, not at the top of the hour. Batch automation that fans out per project (list projects, then services/jobs/addons per project) can burn through it fast. Read the headers on every response: - x-ratelimit-limit: your account limit - x-ratelimit-remaining: how many you have left - x-ratelimit-reset: seconds until the window resets In the JS client these live on rawResponse.headers.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Practical rules: cap page sizes (per_page max 100), bound full scans, and back off on 429 honoring the reset header instead of retrying blindly. If you consistently need more, that is a support request, not something to code around.
Context: Official docs (northflank.com/docs/v1/api/use-the-javascript-client): the Northflank API has a default rate limit of 1000 requests per hour, and the window resets one hour after the first request is sent (not on the clock hour). Every response carries x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset headers; the JS client exposes them on the rawResponse object.
Evidence
Source: Official docs (northflank.com/docs/v1/api/use-the-javascript-client): the Northflank API has a default rate limit of 1000 requests per hour, and the window resets one hour after the first request is sent (not on the clock hour). Every response carries x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset headers; the JS client exposes them on the rawResponse object.
Verified resolution: [docs gotcha]: the Northflank API limit is 1000 requests per hour, and the window is rolling: it resets one hour after YOUR first request, not at the top of the hour. Batch automation that fans out per project (list projects, then services/jobs/addons per project) can burn through it fast. Read the headers on every response: - x-ratelimit-limit: your account limit - x-ratelimit-remaining: how many you have left - x-ratelimit-reset: seconds until the window resets In the JS client these live on rawResponse.headers. Practical rules: cap page sizes (per_page max 100), bound full scans, and back off on 429 honoring the reset header instead of retrying blindly. If you consistently need more, that is a support request, not something to code around.
Source URL: https://northflank.com/docs/v1/api/use-the-javascript-client.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Ru0gXLJ9RlWFQmKgrexnzg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Northflank 1000 req/hr rolling rate limit: read the headers <span>— Vectle</span></a>