Detach a companion file from an asset
DELETE /assets/{id}/companions/{companion_id}
Removes one companion file from an asset, for example a texture the model no longer uses. The asset itself isn’t changed, and the path can be attached again later; the new file gets a new id.
The stored bytes aren’t deleted: the server tries to release the companion’s hold on them, and nothing currently deletes stored files. If that release runs into an error, the companion is still removed and the answer is still 204, so a 204 doesn’t confirm the hold was released. The asset’s cached companion list is cleared on this server and other servers are told to drop theirs, but if that notice fails a list elsewhere can still show the removed file for a while.
You need to be signed in, and any account can remove any companion: the asset’s owner and edit rights aren’t checked, and companions of an asset in the trash can be removed too. A 404 means no companion with that id belongs to that asset, including one already removed; two removals at the same moment can both get 204. An id that isn’t a UUID gets a plain-text 400, and a server error a plain-text 500, not the JSON shown.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The id of the asset the companion belongs to.
The companion’s id, from GET /assets/{id}/companions.
Responses
Section titled “ Responses ”The companion 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