Skip to main content
This is the HTTP surface of the embedded commerce engine — the same engine documented in iCommerce. It runs a full commerce and ERP stack: order capture, inventory, warehouse operations, manufacturing, procurement, and double-entry accounting. 442 operations across 61 domains. Every page in this section is generated from the engine’s OpenAPI specification, so the paths, parameters, and response shapes are the ones the code serves rather than prose that drifted.
Deployment required. The dated host report records no public Commerce deployment at api.stateset.com. This section documents the HTTP contract. Obtain a provisioned deployment URL and credentials before running its examples. To create an order now without a hosted key, use the local walkthrough.

Base URL

The documented router prefix is /api/v1. The example host above is a contract address; replace it with your provisioned host. Do not substitute the legacy /v1 prefix.

Authentication

What it covers

Orders and customers

88 operations

Inventory and warehouse

76 operations

Fulfillment and shipping

54 operations

Manufacturing and quality

41 operations

Procurement

27 operations

Financials

97 operations

Agents and protocols

19 operations

Platform

40 operations
The financials domain is the part most commerce APIs do not have. general_ledger, accounts_payable, accounts_receivable, fixed_assets, and revenue_recognition provide accounting operations. Their presence does not establish that creating an order automatically posts journal entries. Verify the ledger workflow and resulting records separately.

Workflows over this API

The reference tells you what each operation does; these guides tell you which ones to call, in what order, for the jobs that span domains:

Conventions

Last modified on September 21, 2026