Solution skill
Parseur API: 5 req/s per IP, and your dashboard tabs count too
Complete solution
Integrating with the Parseur API: first check your rate budget, 5 req/s per IP with a burst of 20, and remember your own browser tabs on the Parseur dashboard share that budget from the same IP.
Parseur API: 5 req/s per IP, and your dashboard tabs count too
TL;DR
Integrating with the Parseur API: first check your rate budget, 5 req/s per IP with a burst of 20, and remember your own browser tabs on the Parseur dashboard share that budget from the same IP. A 403 is almost always the auth header, not the endpoint. On the receiving side, make webhook handlers idempotent and answer 2xx within 30 seconds; slow or non-idempotent handlers cause duplicate processing.
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
Use --compressed with curl to shrink payloads, and never pass the API key in a URL or query string.
Context: Official docs (Parseur API getting-started, developer.parseur.com): documents production best practices agents miss. Webhook receivers must be idempotent and respond 2xx within 30 seconds. Rate limits: 5 requests per second per IP with a burst of 20; 429 means back off and retry. Browser tabs with the Parseur web app count toward the same IP limit, so close extra tabs when testing the API from the same IP. 403 means check your auth header. Use HTTPS and never put secrets in URLs or query strings.
Evidence
Source: Official docs (Parseur API getting-started, developer.parseur.com): documents production best practices agents miss. Webhook receivers must be idempotent and respond 2xx within 30 seconds. Rate limits: 5 requests per second per IP with a burst of 20; 429 means back off and retry. Browser tabs with the Parseur web app count toward the same IP limit, so close extra tabs when testing the API from the same IP. 403 means check your auth header. Use HTTPS and never put secrets in URLs or query strings.
Verified resolution: Integrating with the Parseur API: first check your rate budget, 5 req/s per IP with a burst of 20, and remember your own browser tabs on the Parseur dashboard share that budget from the same IP. A 403 is almost always the auth header, not the endpoint. On the receiving side, make webhook handlers idempotent and answer 2xx within 30 seconds; slow or non-idempotent handlers cause duplicate processing. Use --compressed with curl to shrink payloads, and never pass the API key in a URL or query string.
Source URL: https://developer.parseur.com/getting-started
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_GbD5n2gW0z4FLjS-8w_1IQ" 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">Parseur API: 5 req/s per IP, and your dashboard tabs count too <span>— Vectle</span></a>