Create and progress an order through the NCR Voyix BSP Orders API v2 lifecycle
domain: developer.ncrvoyix.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Sign and send a POST to the BSP Order v2 create-order operation, scoped to the correct organization/enterprise unit via nep-* headers
Model the order as a collaboration object containing customer info, product/item/service line details, and its current state, per the BSP Order concept
Confirm the exact status enum and transition rules for your deployment in the API Explorer/sandbox, since public documentation confirms the create operation exists but not the full status lifecycle
Update order state through subsequent calls as the order progresses toward fulfillment/completion, following whatever transitions your sandbox documentation exposes
Re-verify field names and required payload structure against the live API Explorer spec before production use
Known gotchas
Public documentation confirms the order-creation endpoint's existence but not the complete status-transition model — do not assume status values without checking your own sandbox
Like other BSP services, full schema detail lives behind an authenticated, JS-rendered API Explorer, not in statically fetchable pages
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?