Skip to content
E-commerce platforms

jumpseller.com

Jumpseller sandbox and mock API

# Endpoint Structure All URLs are in the format: ```text https://api.jumpseller.com/v1/path.json?login=XXXXXX&authtoken=storetoken ``` The path is prefixed by the API version and the URL takes as parameters the login (your store specific API login) and your authentication token. <br/><br/> *** # Version The current version of the API is **v1**. If we change the API in backward-incompatible ways, w Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
142
Collections
-
Event types
-
Start this simulation
example request
curl https://your-jumpseller.slurry.io/v1/categories.json \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.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 142.

  • GET/categories.json
  • POST/categories.json
  • GET/categories/count.json
  • GET/categories/{id}.json
  • PUT/categories/{id}.json
  • DELETE/categories/{id}.json
  • GET/checkout_custom_fields.json
  • POST/checkout_custom_fields.json
  • GET/checkout_custom_fields/{id}.json
  • PUT/checkout_custom_fields/{id}.json
  • DELETE/checkout_custom_fields/{id}.json
  • GET/countries.json