Book in what actually turned up: inTransit falls and on-hand rises at the destination

POST /transfers/{transferId}/receive

Omit lines to receive everything on the road; name fewer to record a short delivery, which leaves the remainder in transit for a later receipt or a cancellation rather than quietly evaporating. The transfer settles to received only when nothing is still out. Appends inventory.transfer-received. reference is required and is the idempotency key: a retry with the same reference is acknowledged and appends nothing — which is what makes a short receipt safe to resend.

Access

Requires stock:write or receiving:write.

Any one of these scopes is enough.

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

Retries

reference is required and is the idempotency key: a retry with the same reference is acknowledged and appends nothing — which is what makes a short receipt safe to resend.

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.transfer-received

What a fact is: Facts and the journal.

AI agent tool

Agents call this as inventory_receive_transfer (Inventory: Receive transfer), in the stock toolset.

Connecting an agent: AI agents.

Example

Five of the six arrive; the sixth stays in transit.

curl

curl -X POST 'https://inventory.getmanifold.io/transfers/trf_01a15bd0-1918-7e9f-bf21-92e337bede18/receive' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "lines": [
    {
      "sku": "WIDGET-BLUE",
      "quantity": 5
    }
  ],
  "reference": "TR-00042-receipt-1"
}'

JavaScript (fetch)

const response = await fetch("https://inventory.getmanifold.io/transfers/trf_01a15bd0-1918-7e9f-bf21-92e337bede18/receive", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "lines": [
      {
        "sku": "WIDGET-BLUE",
        "quantity": 5
      }
    ],
    "reference": "TR-00042-receipt-1"
  }),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Request body · application/json

{
  "lines": [
    {
      "sku": "WIDGET-BLUE",
      "quantity": 5
    }
  ],
  "reference": "TR-00042-receipt-1"
}

Response · 200 · application/json

{
  "id": "trf_01a15bd0-1918-7e9f-bf21-92e337bede18",
  "number": "TR-00042",
  "fromLocationId": "loc_019cadd3-8330-7e12-aa44-2cd5f05da74a",
  "toLocationId": "loc_019cd06e-3b38-7e92-b496-c92f8184a3aa",
  "status": "in-transit",
  "mode": "two-step",
  "lines": [
    {
      "sku": "WIDGET-BLUE",
      "quantity": 6,
      "despatched": 6,
      "received": 5
    }
  ],
  "reference": "restock-shopfront-2026-10-21",
  "createdAt": "2026-10-21T00:15:27.000Z",
  "updatedAt": "2026-10-22T23:10: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
`TransferNotFound` transferId	No such record in this organization.	Check the id in the path or the body.

`409`

Refusal	What it means	What to do
`TransferNotInState` transferId, status, expected	The transfer is not in a state this call accepts.	Read the record: its `status` says where it stands, and `expected` the states this call accepts.
`TransferQuantityExceeded` transferId, sku, outstanding, requested	More units are named than the transfer still has to move. `outstanding` says how many.	Send at most `outstanding` units.
`TransferModeNotAllowed` mode, policy	The organization's transfer policy does not allow this kind of transfer.	Use the mode `policy` allows.
`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

Running more than one location, step 7: Book them in