Rename a view or replace what it saves; anything omitted stays as it was

PUT /views/{viewId}

Appends inventory.view-saved with the whole view. Idempotent by content: the event carries the view entire, so a replay lands on the same view whatever order edits arrived in.

Access

Requires saved-views:write.

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

Retries

Idempotent by content: the event carries the view entire, so a replay lands on the same view whatever order edits arrived in.

Why every write carries a key: Idempotency and retries.

Facts appended

inventory.view-saved

What a fact is: Facts and the journal.

AI agent tool

No agent tool. Saved list views are the admin's display state (a screen's search and filters), not work; an agent filters the list tools directly.

Connecting an agent: AI agents.

Example

Rename the view; its filters stay as they were.

curl

curl -X PUT 'https://inventory.getmanifold.io/views/view_019fcab9-8258-728b-aebc-3d12621e3967' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "label": "Main warehouse stock"
}'

JavaScript (fetch)

const response = await fetch("https://inventory.getmanifold.io/views/view_019fcab9-8258-728b-aebc-3d12621e3967", {
  method: "PUT",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "label": "Main warehouse stock"
  }),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Request body · application/json

{
  "label": "Main warehouse stock"
}

Response · 200 · application/json

{
  "id": "view_019fcab9-8258-728b-aebc-3d12621e3967",
  "screen": "inventory",
  "label": "Main warehouse stock",
  "query": "",
  "filters": [
    {
      "key": "location",
      "operator": "is",
      "values": [
        "loc_019cadd3-8330-7e12-aa44-2cd5f05da74a"
      ]
    },
    {
      "key": "kind",
      "operator": "is",
      "values": [
        "stock"
      ]
    }
  ],
  "sort": "sku:asc",
  "createdAt": "2026-08-04T03:03:03.000Z",
  "updatedAt": "2026-10-22T08:40: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
`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
`ViewNotFound` viewId	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 shortly.

How refusals work everywhere: Errors.