Detach and delete a file, answering with the asset as it was

DELETE /assets/{assetId}

A product's file takes products:write (403 AssetOwnerScopeRequired). Appends inventory.asset-removed; the object is deleted from the bucket after the fact commits. Idempotent: a retry meets 404 and appends nothing.

Access

Requires products:write or stock:write.

Any one of these scopes is enough.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

Retries

Idempotent: a retry meets 404 and appends nothing.

A retry with the same key answers 200, with what the first call recorded.

Why every write carries a key: Idempotency and retries.

Facts appended

inventory.asset-removed

What a fact is: Facts and the journal.

AI agent tool

Agents call this as catalog_remove_asset (Catalog: Remove asset), in the catalog toolset. It is marked destructive, so the agent asks before running it.

Connecting an agent: AI agents.

Example

From Attach a photo to a SKU, step 5: Remove it.

curl

curl -X DELETE 'https://inventory.getmanifold.io/assets/ast_01a15861-f150-7e8f-9a0b-1c2d3e4f5a6b' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://inventory.getmanifold.io/assets/ast_01a15861-f150-7e8f-9a0b-1c2d3e4f5a6b", {
  method: "DELETE",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}` },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Response · 200 · application/json

{
  "id": "ast_01a15861-f150-7e8f-9a0b-1c2d3e4f5a6b",
  "owner": {
    "_tag": "sku",
    "sku": "WIDGET-PHOTO"
  },
  "filename": "front.png",
  "contentType": "image/png",
  "size": 27,
  "uploadedAt": "2026-08-17T09:00:00.000Z"
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: inventory-manager.openapi.json. Base URL https://inventory.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

`401`

Refusal	What it means	What to do
`Unauthorized` reason	The token is missing, expired or not one Manifold issued.	Get a fresh token and send the call again.
`TokenAlreadyUsed` tokenId	A single-use app token was already spent.	Mint a new token for this call.

`402`

Refusal	What it means	What to do
`SubscriptionRequired` status	The organization's subscription has lapsed, so writes are refused.	An owner settles billing. Reads still work meanwhile.

`403`

Refusal	What it means	What to do
`AssetOwnerScopeRequired` assetId, required	The file belongs to a record your token cannot read.	Use a token whose roles read that record.
`TenantRequired` userId	The token names no organization.	Choose the organization, then get a new token.
`ScopeRequired` required	The token's roles do not grant the scope this call needs.	Ask an owner or admin for a role that grants it.

`404`

Refusal	What it means	What to do
`AssetNotFound` assetId	No such record in this organization.	Check the id in the path or the body.

`409`

Refusal	What it means	What to do
`MirroredFromSource` source	This area is fed by your source system until the organization goes live.	Make the change in the source system, or go live first.

`503`

Refusal	What it means	What to do
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Send the same request again, with the same key.

How refusals work everywhere: Errors.

Used in

Attach a photo to a SKU, step 5: Remove it