Detach a blob attachment | API reference

Description

Removes an active attachment binding from its document slot through a signed attachment.detach event. Requires write access through an authorizing container path. A blob left with no active binding is kept for the attachment-retention grace period before garbage collection.

Authentication

Requires a signed-in session: the client sends its session token as a bearer token in the Authorization header.

Parameters

Name	In	Type	Details
`blobId`	path	string	required
`bindingId`	path	string	required

Request body

application/jsonBlobAttachmentDetachRequest

A signed attachment.detach that removes an active binding from its slot.

4 fields

authorizingContainerPathRefsContainerManifestRefArrayArrayrequired
Container paths that authorize the write.
bodyany JSON valuerequired
containerRekeyslist of ContainerMutationRequestoptional
- at most 16 items
Container rekeys to commit first in the same transaction.
eventobject with any fieldsrequired

Other fields are allowed.

Responses

200 OK

application/jsonBlobAttachmentDetachResponse

Confirms which binding was detached.

4 fields

bindingIdstringrequired
blobIdstringrequired
documentIdstringrequired
slotIdstringrequired

Other fields are allowed.

Other responses

Status	Meaning	Body
400	Bad Request	`application/json`ErrorResponse
401	Unauthorized	`application/json`SessionFailureResponse
402	Payment Required	`application/json`PaymentRequiredErrorResponse
403	Forbidden	`application/json`ErrorResponse
404	Not Found	`application/json`ErrorResponse
409	Conflict	`application/json`BlobMutationFailureResponse
500	Internal Server Error	`application/json`ErrorResponse
503	Service Unavailable	`application/json`ErrorResponse