curl -X POST "https://api.scanova.io/qr/download/multi/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"data": [
{
"name": "Summer Sale Landing",
"data": "data:image/png;base64,iVBORw0KGgo...",
"size": 600
},
{
"name": "Product Launch Poster",
"data": "data:image/png;base64,iVBORw0KGgo...",
"size": 600
}
]
}'
QR Codes
Download many rendered QR Code images
POST /qr/download/multi/
POST
/
qr
/
download
/
multi
/
curl -X POST "https://api.scanova.io/qr/download/multi/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"data": [
{
"name": "Summer Sale Landing",
"data": "data:image/png;base64,iVBORw0KGgo...",
"size": 600
},
{
"name": "Product Launch Poster",
"data": "data:image/png;base64,iVBORw0KGgo...",
"size": 600
}
]
}'
Batch form of Download a rendered QR Code image: send a list of download requests, get back a single ZIP.
Same gates as the single endpoint —
POST https://api.scanova.io/qr/download/multi/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
QR_CODE_CAN_DOWNLOAD, plus RASTER_EXPORTING or VECTOR_EXPORTING depending on the formats requested.
array
required
A non-empty list of download requests. Each entry takes the same fields as the single-download body:
name, data, qrid, size, for_print.curl -X POST "https://api.scanova.io/qr/download/multi/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"data": [
{
"name": "Summer Sale Landing",
"data": "data:image/png;base64,iVBORw0KGgo...",
"size": 600
},
{
"name": "Product Launch Poster",
"data": "data:image/png;base64,iVBORw0KGgo...",
"size": 600
}
]
}'
The response is a binary ZIP archive, not JSON. Nothing is persisted server-side — for large selections that you’d rather receive by email, use Export QR Codes instead.
Related
- Download a rendered QR Code image — the single-file form of this endpoint.
- Export QR Codes — an asynchronous export for large selections.
- QR Manager overview — the quotas, role permissions, and Trash model shared by every endpoint in this module.
- 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. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
A ZIP archive containing one file per request, as a binary attachment.
Was this page helpful?