# Batch Delete Cloud Storage Files

Delete Cloud Storage files by id.
- **Preconditions**: every id must resolve within your team; **the whole batch is rejected and rolled back if any one does not**, including ids that were already deleted.
- **Effect**: a soft delete. Quota is released in the same transaction, and the stored objects are removed on a best-effort basis — a storage failure is logged but does not fail the call, so an object can outlive its record. Tag assignments are not cleaned up.
- **Completion**: synchronous. Confirm released space with `/cloudstorage/info`.

Documented business errors: `39011`. See [Error Codes](../Getting%20Started/error-codes.md) for what each code means. Any operation can additionally return the common codes.

Endpoint: POST /api/cloudstorage/file/delete/batch
Version: 2026-09-05

## Request fields (application/json):

  - `ids` (array, required)
    Cloud storage file IDs to delete.
    Example: ["1800000000001001","1800000000001002"]

## Response 200 fields (application/json):

  - `code` (integer, required)
    Return result code. `0` means success; other codes indicate exceptions.
    Example: 0

  - `msg` (string | null, required)
    Error message.
    Example: null

  - `requestId` (string)
    Operation request ID. This field may be present when the request passes through the API gateway.
    Example: 1d4f3ea968664593860b94b35d4ebf5e

  - `data` (null)
    Example: null