Skip to content
E-commerce platforms

api2cart.com

Swagger API2Cart sandbox and mock API

API2Cart Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
146
Collections
-
Event types
-
Start this simulation
example request
curl https://your-api2cart.slurry.io/v1.1/account.cart.list.json \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • POST/account.cart.add.json
  • GET/account.cart.list.json
  • PUT/account.config.update.json
  • GET/account.failed_webhooks.json
  • GET/account.supported_platforms.json
  • POST/attribute.add.json
  • POST/attribute.assign.group.json
  • POST/attribute.assign.set.json
  • GET/attribute.attributeset.list.json
  • GET/attribute.count.json
  • DELETE/attribute.delete.json
  • GET/attribute.group.list.json