Fulfillment Manager API · lineProperties

Which live definitions apply to each of these SKUs

GET /line-item-properties/applicable

Which live (unarchived) definitions apply to each of these SKUs (comma-separated), in display order: a definition scoped by tag or product is judged against the product inventory holds the SKU under now.

What the order form offers on a line. Appends nothing: a read of the settings.

Access

Requires orders:read.

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

AI agent tool

No agent tool. the order form's per-SKU lookup of which properties to offer; an agent reads the definitions with fulfillment_get_line_properties, and the service holds every line it writes to them

Connecting an agent: AI agents.

Example

curl

curl -X GET 'https://fulfillment.getmanifold.io/line-item-properties/applicable?skus=PEN-BRASS%2CMUG-12OZ' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://fulfillment.getmanifold.io/line-item-properties/applicable?skus=PEN-BRASS%2CMUG-12OZ", {
  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

{
  "items": [
    {
      "sku": "PEN-BRASS",
      "propertyIds": [
        "lip_0192f3a0-6c1e-7a10-8b2c-3d4e5f607181",
        "lip_0192f3a0-6c1e-7a10-8b2c-3d4e5f607182",
        "lip_0192f3a0-6c1e-7a10-8b2c-3d4e5f607183"
      ]
    },
    {
      "sku": "MUG-12OZ",
      "propertyIds": [
        "lip_0192f3a0-6c1e-7a10-8b2c-3d4e5f607182",
        "lip_0192f3a0-6c1e-7a10-8b2c-3d4e5f607183"
      ]
    }
  ]
}

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.

`502`

Refusal	What it means	What to do
`InventoryUnavailable` reason	The inventory service did not answer, so nothing changed.	Try again shortly.

`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.