Delete File (Move to Trash)

## Delete File (Move to Trash) Moves a file to **trash** instead of permanently deleting it. The file can typically be restored later depending on the system's trash management. **Method:** `DELETE` **URL:** `{{base_url}}/files/{{file_id}}` --- ## Authentication This endpoint requires authentication. - **Recommended:** Bearer token in the `Authorization` header: ``` http 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. --- ## Required variables Set these variables at the **environment** or **collection** level: | Variable | Required | Description | | --- | --- | --- | | `base_url` | Yes | Base API URL (e.g. `https://app.getgabs.com/partners/wp-gallery/manage`) | | `access_token` | Yes | Access token used to authorize the request | | `file_id` | Yes | ID of the file to delete | --- ## Path Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `file_id` | integer | Yes | Unique identifier of the file to move to trash | Example request URL: ``` {{base_url}}/files/34 ``` --- ## Sample request ``` bash curl --request DELETE "{{base_url}}/files/{{file_id}}" \ --header "Authorization: Bearer {{access_token}}" ``` --- ## Sample success response A successful request typically returns **HTTP 200 OK**. ``` json { "success": true, "message": "File moved to trash" } ``` --- ## Common errors - **400 Bad Request** - Invalid or missing `file_id` - **401 Unauthorized / 403 Forbidden** - Missing/invalid `Authorization` header - Expired `{{access_token}}` - **404 Not Found** - File with the given `file_id` does not exist --- ## Notes - This endpoint performs a **soft delete** by moving the file to trash. - The file is **not permanently deleted immediately**. - The file may be restored later if the system supports **trash recovery**. - Permanent deletion may require a separate endpoint or automatic cleanup policy.