curl --request POST \
--url https://api.example.com/api/assets/trash \
--header 'Content-Type: application/json' \
--data '
{
"ids": [
"<string>"
]
}
'{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>",
"input": "<unknown>",
"ctx": {}
}
]
}Soft-deletes the given assets. Trashed assets are excluded from default list/search results and are purged after the configured retention window. Reversible via restore_assets until purge.
Use this for the user’s standard ‘delete’ action. To delete forever in one step, use permanently_delete_assets instead — but prefer trash so the user can recover from accidental deletes.
curl --request POST \
--url https://api.example.com/api/assets/trash \
--header 'Content-Type: application/json' \
--data '
{
"ids": [
"<string>"
]
}
'{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>",
"input": "<unknown>",
"ctx": {}
}
]
}Documentation Index
Fetch the complete documentation index at: https://docs.gumnut.ai/llms.txt
Use this file to discover all available pages before exploring further.
Library that owns the assets. Optional if the user has a single library; required when they have multiple.
Request body carrying a list of asset IDs for the bulk trash, restore, and permanent-delete endpoints.
Asset IDs (each with the asset_ prefix) to operate on. Up to 100 ids per request.
1 - 100 elementsSuccessful Response