> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Bulk-generate QR Codes
> POST /bulk-operation/generate/
Creates many QR Codes from an uploaded sheet, asynchronously, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.
```
POST https://api.scanova.io/bulk-operation/generate/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```
A label for this operation, shown in [List bulk operations](/api-reference/management-api/bulk-operation/list).
The filled-in sheet, one row per QR Code. The **first row's `qr code id`** column supplies the template QR — its category and field schema are what every other row is validated against.
A custom domain id to use for the generated QR Codes' short links.
Design pattern data applied to all generated QR Codes, typically JSON encoded as a string.
Optional auto-deactivation rule applied to all generated QR Codes: `expire_on`/`activate_on` (future ISO-8601 datetimes) and/or `expire_on_scan_count` (positive integer).
A folder id to save the generated QR Codes into.
```bash cURL theme={null}
curl -X POST "https://api.scanova.io/bulk-operation/generate/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-F "name=September event QR batch" \
-F "file=@event-qrs.xlsx" \
-F 'auto_deactivate={"expire_on":"2026-12-31T23:59:59Z"}'
```
```json 200 theme={null}
{
"operation_id": "bo-8f3a1c",
"message": ["Your file is being processed. We'll email you once it's ready."]
}
```
## This is asynchronous
The `200` response confirms the job was accepted, not that the QR Codes exist yet — the actual work runs on a background worker. Poll [List bulk operations](/api-reference/management-api/bulk-operation/list) (filter locally by `operation_id`) and watch `status` (`new` → `completed`/`partially_completed`/`failed`) and `progress`, then read `result_file`/`log_file` once done. The account also gets an email notification on completion.
`400` for an invalid file/columns, a missing or invalid template QR, or exceeded quota (`BULK_OPERATION` or `TOTAL_QR_CODES`). `403` if the account lacks the `BULK_OPERATION` quota, has an inactive plan, or lacks `BULK_OPERATION_CAN_GENERATE` permission.
## Related
* [Bulk-generate QR Codes (v2 templates)](/api-reference/management-api/bulk-operation/generate-v2) — the v2-template equivalent.
* [Validate a bulk operation file](/api-reference/management-api/bulk-operation/validate) — check the file before spending this call.
* [Download a sample file](/api-reference/management-api/bulk-operation/sample-file) — where to start the sheet from.
* [List bulk operations](/api-reference/management-api/bulk-operation/list) — poll for completion.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.
## OpenAPI
````yaml api-reference/openapi/management-api.json POST /bulk-operation/generate/
openapi: 3.1.0
info:
title: Scanova Management API (v2)
description: >-
The complete Scanova Management API — every endpoint available at
api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
shared users & roles), plus the token-creation and usage-stats endpoints
used to authenticate against it. Every path and request/response shape below
was verified live against a real API key and the actual running backend
(Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
version: 2.0.0
servers:
- url: https://api.scanova.io
description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
- apiKeyAuth: []
paths:
/bulk-operation/generate/:
post:
summary: Bulk-generate QR codes
description: >-
Creates many QR codes from an uploaded sheet, asynchronously. Returns
immediately with an `operation_id` while a Celery task does the work —
poll [List bulk
operations](/api-reference/management-api/bulk-operation/list) for
`status`/`progress`, then fetch `result_file`/`log_file` once complete.
The sheet's first row's `qr code id` supplies the template QR whose
category and field schema every other row is validated against.
operationId: generateBulkOperation
requestBody:
content:
multipart/form-data:
example:
name: September event QR batch
file: (binary file)
custom_domain: null
pattern_info: '{"dotStyle":"round"}'
folder: null
auto_deactivate:
expire_on: '2026-12-31T23:59:59Z'
responses:
'200':
description: Generation started.
content:
application/json:
example:
operation_id: bo-8f3a1c
message:
- >-
Your file is being processed. We'll email you once it's
ready.
'400':
description: >-
Invalid file/columns, missing or invalid template QR, or quota
exceeded.
'403':
description: >-
Missing BULK_OPERATION quota, inactive plan, or missing
BULK_OPERATION_CAN_GENERATE permission.
components:
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: Authorization
description: >-
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.
````