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

# Retrieve a bulk media batch

> GET /media/bulk/{pk}/

Retrieves one bulk media batch, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

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

<ParamField path="pk" type="integer" required>
  The batch's `id`, from [List bulk media batches](/api-reference/management-api/user-media/bulk-list).
</ParamField>

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 12,
    "operation_id": "BM-9F3K2LQP",
    "status": "new",
    "count": 25,
    "upload_count": 8,
    "created": "2026-09-08T09:00:00Z",
    "modified": "2026-09-08T09:05:00Z"
  }
  ```
</ResponseExample>

Poll this endpoint to track upload progress against a batch — `upload_count` increases as files are uploaded with this batch's id, and `status` moves to `completed` once done. `404` if `pk` isn't a batch owned by this account.

## Related

* [Update a bulk media batch](/api-reference/management-api/user-media/bulk-update) — change the batch, e.g. mark it complete.
* [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/{pk}/
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/{pk}/:
    get:
      summary: Retrieve a bulk media batch
      operationId: getBulkMedia
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: One batch.
          content:
            application/json:
              example:
                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'
        '404':
          description: No batch with this id owned by this account.
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.

````