> ## 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-delete files by path

> DELETE /media/delete/

Deletes multiple files at once, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
DELETE https://api.scanova.io/media/delete/?file={path1},{path2}
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField query="file" type="string" required>
  Comma-separated storage file paths to delete — the `file` field values from [List uploaded files](/api-reference/management-api/user-media/list), **not** record ids.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X DELETE "https://api.scanova.io/media/delete/?file=media/uploads/104/2026/09/20260908_512873_logo.png,media/uploads/104/2026/09/20260908_998211_banner.jpg" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

A successful call returns `204 No Content`. `400` with `{"error": ["File does not exist."]}` if none of the given paths matched a file owned by this account.

<Note>
  To delete by id instead of storage path, use [Delete a file](/api-reference/management-api/user-media/delete).
</Note>

## Related

* [List uploaded files](/api-reference/management-api/user-media/list) — get the `file` paths to delete.
* [Delete a file](/api-reference/management-api/user-media/delete) — delete a single file by id.
* [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 DELETE /media/delete/
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/delete/:
    delete:
      summary: Bulk-delete files by path
      description: >-
        Deletes multiple files at once by their storage `file` path (as returned
        in the `file` field of a media record), not by id.
      operationId: bulkDeleteMediaByPath
      parameters:
        - name: file
          in: query
          required: true
          schema:
            type: string
          description: Comma-separated storage file paths to delete.
      responses:
        '204':
          description: Files deleted.
        '400':
          description: None of the given paths matched a file 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.

````