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

# Massen-Medien-Batches auflisten

> GET /media/bulk/

Listet die Massen-Medien-Batches des Kontos auf, auf dem **Management-API**-Host (`api.scanova.io`), authentifiziert mit Ihrem rohen Management-API-Schlüssel.

```
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>

Ein Massen-Medien-Batch gruppiert eine Reihe zusammengehöriger Datei-Uploads — zum Beispiel alle Bilder, die in einem Massen-QR-Generierungslauf verwendet werden. `status` wechselt von `new` zu `completed` (oder `failed`), sobald die Uploads für den Batch abgeschlossen sind; `upload_count` verfolgt den Fortschritt gegenüber der deklarierten `count` des Batches.

## Verwandte Themen

* [Massen-Medien-Batch erstellen](/de/api-reference/management-api/user-media/bulk-create) — einen neuen Batch starten.
* [Datei hochladen](/de/api-reference/management-api/user-media/upload) — einzelne Dateien über `bulk_media` in einen Batch hochladen.
* [Massen-Medien-Batch als CSV exportieren](/de/api-reference/management-api/user-media/bulk-export) — die Dateiliste des Batches herunterladen.
* [Übersicht über die Management API](/de/api-reference/management-api/overview) — das Authentifizierungsschema und die Quota-Regeln für diesen Endpunkt.


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

````