Bulk Delete Files

Bulk Delete Files

Moves multiple files to trash in a single request. This performs a soft delete, allowing the files to be restored later if needed.

Method: POST
URL: {{base_url}}/files/bulk-delete

Authentication

This endpoint requires authentication.

• Recommended: Bearer token in the Authorization header:

Authorization: Bearer {{access_token}}

Notes:

• If your collection/folder already sets auth, this request can inherit auth.

• Ensure {{access_token}} is a valid, non-expired token.

Headers

Required variables

Set these variables at the environment or collection level:

Body (raw JSON)

Send the request body as raw JSON.

Example body:

{
  "file_ids": [
    37
  ]
}

Notes:

• You can include one or multiple file IDs in the array.

• All specified files will be moved to trash.

Sample request

curl --request POST "{{base_url}}/files/bulk-delete" \
  --header "Authorization: Bearer {{access_token}}" \
  --header "Content-Type: application/json" \
  --data '{
    "file_ids": [37]
  }'

Sample success response

A successful request typically returns HTTP 200 OK.

{
  "success": true,
  "message": "1 file(s) moved to trash"
}

Common errors

• 400 Bad Request

  • Missing file_ids

  • Invalid file ID format

• 401 Unauthorized / 403 Forbidden

  • Missing/invalid Authorization header

  • Expired {{access_token}}

• 404 Not Found

  • One or more files do not exist

Notes

• This endpoint performs a soft delete on multiple files.

• The files are not permanently deleted and can be restored using the Restore File from Trash endpoint.

• To permanently remove files, use the Permanently Delete File endpoint.

• This endpoint is useful for bulk operations in file managers or gallery interfaces.