curl --request DELETE \
--url https://api.example.com/api/assets \
--header 'Content-Type: application/json' \
--data '
{
"ids": [
"<string>"
]
}
'{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>",
"input": "<unknown>",
"ctx": {}
}
]
}Hard-deletes each specified asset — the database record, the stored file, and all associated data (faces, album links, etc.). Irreversible. Prefer trash_assets for the user’s standard delete action so accidents can be recovered.
Up to 100 ids per request; over-cap requests return 422.
curl --request DELETE \
--url https://api.example.com/api/assets \
--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