Attach a sidecar file to a 3D model asset
POST /assets/{id}/companions
Streams the file body content-addressed into storage, then attaches it to the asset at the given relative path. If a companion already exists at that path it is replaced (the old pin is removed; the storage object lives on if other pins reference it).
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Header Parameters
Section titled “Header Parameters ”Relative path the model file references this companion at. Slashes are allowed for subdirectory layouts (‘textures/foo.png’). Limited to 512 chars.
MIME type of the companion bytes. If absent we default to application/octet-stream.
Request Body required
Section titled “Request Body required ”Responses
Section titled “ Responses ”Companion attached
A sidecar file (texture, MTL, .bin, etc.) attached to a 3D model asset under a relative path. The viewer’s LoadingManager rewrites the model’s relative resource references through these entries so external resources resolve to the right content-addressed blob.
object
Relative path the model file references this companion at — e.g. ‘character.mtl’ for an OBJ’s sibling .mtl, or ‘textures/foo.png’ for a glTF texture in a subdirectory.
Example
textures/character-a.pngExample
image/pngMalformed request
object
Human-readable error summary
Example
the request could not be completedAuthentication 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 completedUnexpected server error
object
Human-readable error summary
Example
the request could not be completed