curl -X POST "https://management.scanova.io/qr/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"category": 1,
"info": "{\"type\":\"url\",\"data\":{\"url\":\"https://example.com\"}}",
"qr_type": "dy",
"name": "Product launch flyer"
}'
Management API — QR Codes
Create a QR code
POST /qr/
POST
/
qr
/
curl -X POST "https://management.scanova.io/qr/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"category": 1,
"info": "{\"type\":\"url\",\"data\":{\"url\":\"https://example.com\"}}",
"qr_type": "dy",
"name": "Product launch flyer"
}'
Lists or creates QR codes on the Management API host (
A successful create returns
management.scanova.io), authenticated with your raw Management API key — see the overview if you haven’t set that up yet.
GET https://management.scanova.io/qr/
POST https://management.scanova.io/qr/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
POST /qr/ creates a new QR code using the same serializer and field contract as the regular dashboard’s create-QR endpoint. Rather than re-deriving the full field reference here, see Create QR Code for the complete required/optional field table (category, info, name, qr_type, plus advanced fields like pattern_info, custom_domain, expire_on, lead_list, password, and geo-fencing options) — every field documented there applies identically here.
curl -X POST "https://management.scanova.io/qr/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"category": 1,
"info": "{\"type\":\"url\",\"data\":{\"url\":\"https://example.com\"}}",
"qr_type": "dy",
"name": "Product launch flyer"
}'
201 Created with the newly created QR code, serialized with the full detail shape (the same one returned by GET /qrcode/{qrid}/) — richer than the slim list shape shown above, and including fields like info and pattern_info that the list endpoint omits for performance.
Creating a QR code is subject to the same plan-based QR-count limits (dynamic/static) as creating one from the dashboard, in addition to the MANAGEMENT_API (or INTEGRATION_ZAPIER/INTEGRATION_MCP) quota gate described in the overview.
Related
- List QR codes — the other operation on this same endpoint.
- Retrieve — operate on a single QR code returned by this list.
- Update — operate on a single QR code returned by this list.
- Delete — operate on a single QR code returned by this list.
- Download a QR code image — render one of these QR codes as a PNG/SVG/PDF/etc.
- List trashed QR codes — where a QR code goes after being deleted from this list.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. management.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
201
QR code created
Was this page helpful?
⌘I