> ## 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.

# List bulk media batches

> GET /media/bulk/

Lists the account's bulk media batches, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
GET https://api.scanova.io/media/bulk/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/media/bulk/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "count": 1,
    "next": null,
    "previous": null,
    "results": [
      {
        "id": 12,
        "operation_id": "BM-9F3K2LQP",
        "status": "new",
        "count": 25,
        "upload_count": 0,
        "created": "2026-09-08T09:00:00Z",
        "modified": "2026-09-08T09:00:00Z"
      }
    ]
  }
  ```
</ResponseExample>

A bulk media batch groups a set of related file uploads — for example, all the images used in one bulk QR Code generation run. `status` moves from `new` to `completed` (or `failed`) as uploads for the batch complete; `upload_count` tracks progress against the batch's declared `count`.

## Related

* [Create a bulk media batch](/api-reference/management-api/user-media/bulk-create) — start a new batch.
* [Upload a file](/api-reference/management-api/user-media/upload) — upload individual files into a batch via `bulk_media`.
* [Export a bulk media batch as CSV](/api-reference/management-api/user-media/bulk-export) — download the batch's file list.
* [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 GET /media/bulk/
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:
  /media/bulk/:
    get:
      summary: List bulk media batches
      operationId: listBulkMedia
      responses:
        '200':
          description: Paginated list of bulk media batches.
          content:
            application/json:
              example:
                count: 1
                next: null
                previous: null
                results:
                  - id: 12
                    operation_id: BM-9F3K2LQP
                    status: new
                    count: 25
                    upload_count: 0
                    created: '2026-09-08T09:00:00Z'
                    modified: '2026-09-08T09:00:00Z'
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.

````