Documentation
Rate limits and plans
Each key has its own requests-per-second ceiling, counted in a sliding one-second window across every route. Your plan sets the maximum; you can set a lower value per key, which is how most people keep a staging key from spending the production budget. Every call shows in your usage, the free ones included.
| Limit | Free | Pro |
|---|---|---|
| Links in the account | 100 | 5,000 |
| Links made per day | 100 | 2,000 |
| Analytics range | 30 days | A year |
| Clicks by hour of the day | No | Yes |
| Click exports (CSV and JSON) | No | Yes |
| Requests per second per key | 2 | 10 |
| Active API keys | 2 | 10 |
| QR code credits a month | 100 | 10,000 |
The link and analytics routes never charge credits. Credits pay only for QR code generator, 1 credit per code, and are shared across every key on the account and the website.
Response headers
| Header | Meaning |
|---|---|
X-Request-Id | Unique id for this call. Present on every response. |
X-RateLimit-Limit | The key's requests per second. |
Retry-After | Seconds to wait. Sent with every 429 rate_limited. |
X-Credits-Remaining | Credits left after a metered call. |
X-Cache | hit, miss or off on a metered call, matching meta.cache. |