Skip to main content
POST
/
api
/
assets
/
restore
Restore assets from trash
curl --request POST \
  --url https://api.example.com/api/assets/restore \
  --header 'Content-Type: application/json' \
  --data '
{
  "ids": [
    "<string>"
  ]
}
'
{}

Query Parameters

​
library_id
string | null

Library that owns the assets. Optional if the user has a single library; required when they have multiple.

Body

application/json

Request body carrying a list of asset IDs for the bulk trash, restore, and permanent-delete endpoints.

​
ids
string[]
required

Asset IDs (each with the asset_ prefix) to operate on. Up to 100 ids per request.

Required array length: 1 - 100 elements

Response

Successful Response

Acknowledgment body returned by destructive endpoints (delete / trash / restore / permanently delete / remove-from-album / empty-trash).

Carries no fields — the HTTP 200 + empty JSON object is itself the success signal. Exists so MCP tools generated from these endpoints have a real outputSchema (rather than the null schema FastMCP emits for 204 responses), which ChatGPT's MCP submission tooling requires.