Remove an alternate file
DELETE /assets/{id}/alternates/{alternate_id}
Detaches one alternate from an asset and deletes its record. Nothing else about the asset changes.
The file itself stays in storage: the server tries to release the alternate’s hold on it, but doesn’t delete stored bytes at the moment.
Any signed-in account that knows both ids can remove it. Ownership and edit rights aren’t checked, and it works while the asset is in the trash too.
An alternate that doesn’t exist or belongs to another asset gets 404. An id that isn’t a UUID gets a plain-text 400, and a database failure a plain-text 500.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The asset’s id.
The alternate’s id, from GET /assets/{id}/alternates.
Responses
Section titled “ Responses ”The alternate was removed.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Resource not found
object
Human-readable error summary
Example
the request could not be completed