Skip to content
E-commerce platforms

fulfillment.com

Fulfillment.com APIv2 sandbox and mock API

Welcome to our current iteration of our REST API. While we encourage you to upgrade to v2.0 we will continue support for our [SOAP API](https://github.com/fulfillment/soap-integration). # Versioning The Fulfillment.com (FDC) REST API is version controlled and backwards compatible. We have many future APIs scheduled for publication within our v2.0 spec so please be prepared for us to add data nodes Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
13
Collections
-
Event types
-
Start this simulation
example request
curl https://your-fulfillment.slurry.io/v2/accounting \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 13.

  • GET/accounting
  • GET/inventory
  • POST/oauth/access_token
  • GET/orders
  • POST/orders
  • GET/orders/{id}
  • DELETE/orders/{id}
  • PUT/orders/{id}/ship
  • PUT/orders/{id}/status
  • GET/returns
  • PUT/returns
  • GET/track