The organization's document series

GET /numbering

The organization's document series: one each for orders (and quotes), shipments, invoices, payments and refunds, each a prefix (SO-, SH-, INV-, PAY-, RF- until set) and the next serial.

Every document minted advances its own series, so a series is always past everything it has issued.

Access

Requires settings:read.

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

AI agent tool

Agents call this as fulfillment_get_numbering (Fulfillment: Get numbering), in the fulfillment toolset. It only reads.

Connecting an agent: AI agents.

Example

curl

curl -X GET 'https://fulfillment.getmanifold.io/numbering' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://fulfillment.getmanifold.io/numbering", {
  method: "GET",
  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

{
  "orders": {
    "prefix": "SO-",
    "next": 1047
  },
  "shipments": {
    "prefix": "SH-",
    "next": 1064
  },
  "invoices": {
    "prefix": "INV-",
    "next": 872
  },
  "payments": {
    "prefix": "PAY-",
    "next": 913
  },
  "refunds": {
    "prefix": "RF-",
    "next": 65
  }
}

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: fulfillment-manager.openapi.json. Base URL https://fulfillment.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.

`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.	Try again shortly.

How refusals work everywhere: Errors.