> ## 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 a GS1 serial range

> POST /bulk-operation/gs1/serial-range-generate/

Generates a contiguous range of GS1 QR Codes from a starting serial number, asynchronously, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
POST https://api.scanova.io/bulk-operation/gs1/serial-range-generate/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<Note>
  No file upload — this endpoint generates the range programmatically from `start_serial` and `count`.
</Note>

<ParamField body="name" type="string" required>
  A label for this operation.
</ParamField>

<ParamField body="start_serial" type="string" required>
  The first serial number in the range, digits only, max 20 characters.
</ParamField>

<ParamField body="count" type="integer" required>
  How many sequential serials to generate, minimum 1.
</ParamField>

<ParamField body="sample_qrid" type="string">
  An existing GS1 QR's id to copy shared field values from. Provide this **or** `shared_info`, not neither.
</ParamField>

<ParamField body="shared_info" type="array">
  The GS1 field values shared by every serial in the range, as JSON. Provide this **or** `sample_qrid`, not neither.
</ParamField>

<ParamField body="custom_domain" type="integer">
  A custom domain id to use for the generated QR Codes' short links.
</ParamField>

<ParamField body="pattern_info" type="string">
  Design pattern data applied to all generated QR Codes.
</ParamField>

<ParamField body="auto_deactivate" type="object">
  Optional auto-deactivation rule applied to all generated QR Codes.
</ParamField>

<ParamField body="utm_parameters" type="object">
  UTM tracking parameters applied to all generated QR Codes' links.
</ParamField>

<ParamField body="folder" type="integer">
  A folder id to save the generated QR Codes into.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/bulk-operation/gs1/serial-range-generate/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
      "name": "GS1 batch 001-100",
      "start_serial": "00000001",
      "count": 100,
      "sample_qrid": "a1b2c3d4"
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "operation_id": "bo-gs1-001",
    "message": ["Your GS1 serial range is being processed. We'll email you once it's ready."]
  }
  ```
</ResponseExample>

Same asynchronous pattern as [Bulk-generate QR Codes](/api-reference/management-api/bulk-operation/generate) — poll [List bulk operations](/api-reference/management-api/bulk-operation/list). The first assembled GS1 payload in the range is schema-validated before any QR Codes are created, so a malformed `shared_info` shape fails fast.

`400` if the resulting serial exceeds 20 characters at any point in the range, if neither `shared_info` nor `sample_qrid` is provided, or if quota (`BULK_OPERATION` or `TOTAL_QR_CODES`, checked against the full `count`) is exceeded. `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](/api-reference/management-api/bulk-operation/generate) — the general file-upload-based equivalent for non-GS1 categories.
* [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/gs1/serial-range-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/gs1/serial-range-generate/:
    post:
      summary: Bulk-generate a GS1 serial range
      description: >-
        Generates a contiguous range of GS1 QR codes from a starting serial and
        count, without a file upload. Requires either `shared_info` or
        `sample_qrid` to supply the shared GS1 field values applied to every
        serial in the range.
      operationId: generateGs1SerialRange
      requestBody:
        content:
          application/json:
            example:
              name: GS1 batch 001-100
              start_serial: '00000001'
              count: 100
              sample_qrid: a1b2c3d4
              custom_domain: null
              folder: null
      responses:
        '200':
          description: Generation started.
          content:
            application/json:
              example:
                operation_id: bo-gs1-001
                message:
                  - >-
                    Your GS1 serial range is being processed. We'll email you
                    once it's ready.
        '400':
          description: >-
            Serial range too long (>20 characters), neither shared_info nor
            sample_qrid provided, 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.

````