Developer docs
There are three ways to work with your QR codes and short links from software: the REST API, the MCP server for AI assistants, and connectors for no-code tools. They share one workspace, one plan and one monthly request count.
Pick a route
Choose by who does the work: code you write, an assistant you talk to, or a workflow tool.
| Route | Best for | Signs in with | On Free | From Starter | Docs |
|---|---|---|---|---|---|
| REST API | Scripts, servers and your own app | An API key as a Bearer token, or Sign in with QRSalt | Render QR codes and barcodes | Codes, short links, scans, folders, tags, forms and menus | API reference |
| MCP server | Claude, Cursor, VS Code and other AI clients | Sign in with QRSalt, or an API key in a header | The 2 picture tools | All 13 tools | MCP setup |
| n8n and Make | Workflows you build without code | An API key saved as a credential or connection | Render and read steps | Every action and polling trigger | n8n and Make |
Webhooks and instant triggers start on Business. Reading a code out of an image and the keyless render need no account at all.
The whole API reference is also one Markdown file, docs.md, if you'd like to paste it into an AI chat.
Limits by plan
Calls under /api/v1 and every MCP tool call count towards the month. Rendering and the keyless endpoints don't.
| Plan | Price | Account access | Requests a month | Requests a minute, per key | Webhooks |
|---|---|---|---|---|---|
| Free | $0 | Render only | Not counted | 60 | No |
| Starter | $5 a month | Yes | 500 | 600 | No |
| Pro | $15 a month | Yes | 5,000 | 600 | No |
| Business | $39 a month | Yes | 100,000 (fair use) | 600 | Yes |
Going over either limit answers 429 with the time it resets. The headers and error bodies are in rate limits.
Credentials
Two ways to prove who you are, and two endpoints that need neither.
| Credential | Where you get it | How long it lasts | Used by |
|---|---|---|---|
API key, qr_live_… | Dashboard → API. It is shown once. | Until you revoke it | Your code, MCP clients that take a header, n8n and Make |
| Sign in with QRSalt | OAuth 2.1 with PKCE, started by the app or client | Access token 1 hour, refresh token 90 days | MCP clients that support sign-in, and apps you build |
| None | Nothing to set up | Not applicable | GET /api/qr/free and POST /api/qr/decode |
Give each integration its own key with only the scopes it needs, so you can revoke one without stopping the rest. The scopes section lists what each one allows.