QR codes from your own software
Create codes from your shop, CRM or print workflow, and hear about every scan as it happens.
What you get
REST API
Create, read, update and list codes and Smart Links; read their stats.
Webhooks
Get a signed POST on scans and code changes. Every delivery is logged; a hook that keeps failing is paused and you are told.
Keys and logs
Several keys per workspace, revocable, with a log of recent calls.
Templates
Save a design once and apply it to every code the API creates.
How it works
- 1
Open Developers in your dashboard and create a key.
- 2
Call the API with the key in the Authorization header.
- 3
Add a webhook URL to hear about scans as they happen.
What teams build with the QR code API
Shops create a code for every product or order, event platforms issue a code per ticket, print workflows add codes to labels automatically, and CRMs make a personal code for each contact. Because the codes are dynamic, you can change where any of them points later, from the API or the dashboard.
How it works
Create a key under Developers, then call the REST endpoints with the key as a Bearer token. Responses are JSON. You can list, create, update and archive codes, read their statistics, and render static QR codes and barcodes as SVG. Pass a saved design template so every code matches your brand. The full reference, with an OpenAPI 3.1 file, is in the developer docs.
Webhooks send a signed POST when a code is scanned or changed, so your system can react in real time. Every delivery is logged; a hook that fails 5 times in a row is paused and you are told.
API and webhooks questions
Yes, in the dashboard next to your keys, with examples for each endpoint.
Yes, per key per minute. Going over returns HTTP 429; wait a minute and try again.
The API is part of Pro.
Yes. The render endpoint returns a static QR code or a barcode as SVG without saving anything to your account.
Each delivery carries a signature header made with your webhook secret. The docs show how to check it.