Build directly on the platform
The Fulfillment.com developer REST API
Fulfillment.com exposes a production REST API (v2) that brands and developers build on directly: push orders, pull order status, and sync tracking and inventory from your own systems. It has run brand integrations in production for over a decade, is fully documented with an OpenAPI (Swagger) spec, and authenticates with an OAuth2 bearer token.
What you can build
Wire your own systems straight to ours. Our REST API has run brand integrations in production for over a decade: push orders, pull order status, and sync tracking and inventory from your own code. It is fully documented and versioned, with a complete OpenAPI (Swagger) spec and a public spec on GitHub, so your team can build against it quickly.
- Push orders
Send orders into the platform from your own store or system. - Pull order status
Read an order and its live status straight from your code. - Sync tracking & inventory
Keep tracking and stock in step across your systems.
Quick example
Production base URL https://api.fulfillment.com/v2.
Authenticate with an OAuth2 bearer token in the Authorization header.
# Pull an order and its live status straight from your own code
curl https://api.fulfillment.com/v2/orders/{id} \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"The full endpoint list, request and response shapes, and auth flow are in the API docs and the OpenAPI spec on GitHub.
Custom and B2B connectivity
Built a system we have not met yet?
Beyond the REST API and 116+ pre-built connectors, teams with unique systems and retailer or B2B compliance needs can talk to our integration team about a custom path.
Developer API FAQ
Does Fulfillment.com have a REST API?
Yes. Fulfillment.com runs a production REST API (v2) that brands and developers build on directly. It has run brand integrations in production for over a decade and is fully documented with an OpenAPI (Swagger) spec published on GitHub.
What is the API base URL?
The production server is https://api.fulfillment.com/v2. The full endpoint list, request and response shapes, and authentication details are in the OpenAPI spec and the published docs.
How does authentication work?
The API authenticates with an OAuth2 bearer token, sent in the Authorization header on each request (Authorization: Bearer YOUR_ACCESS_TOKEN).
What can I do with the API?
Push orders into Fulfillment.com, pull order status, and sync tracking and inventory back into your own systems. It is the same API that has run production brand integrations for over a decade.
Where are the API docs and the spec?
The docs are at fulfillment.github.io/api and the complete OpenAPI spec is public on GitHub at github.com/fulfillment/api, so your team can build against it directly.
Do I have to use the API to integrate?
No. Fulfillment.com offers 116+ pre-built integrations for common platforms, so most brands never write code. The REST API is for teams that prefer to wire their own systems straight into BestOMS, the platform that runs your orders.
Build directly on Fulfillment.com.
Read the API docs, browse the OpenAPI spec on GitHub, or talk to our integration team about a custom path. One platform, one accountable operator.