Try it

Call a living API. No account needed.

These demo worlds were designed by Slurry from real API descriptions. Copy a request into your terminal and look at the data, the headers and the pagination.

Salesforce demo

demo-salesforce.slurry.io

curl https://demo-salesforce.slurry.io/services/data/v62.0/query?q=SELECT+Id,Name,StageName,Amount+FROM+Opportunity+LIMIT+5 \
  -H "Authorization: Bearer slurry_sim_live_goUY5TJ_S-BlWD_5sOPNGN3amuHtRevr"

Stripe demo

demo-stripe.slurry.io

curl https://demo-stripe.slurry.io/v1/customers?limit=5 \
  -H "Authorization: Bearer slurry_sim_live_pyUJZLftgZWIcqIClvHPqoGFPgg6G5wZ"

Jira demo

demo-jira.slurry.io

curl https://demo-jira.slurry.io/rest/api/3/search?maxResults=5 \
  -H "Authorization: Bearer slurry_sim_live_ob_6GjKamji7lxhmMJyFXN-yT0ok1WCd"

Look for x-slurry-simulated: true and x-slurry-operation in the response headers. Add -H "Slurry-Force: 5xx" to see a forced failure.

Want to write data too? Start a private playground: your own writable simulation for two hours, locked to your IP address, no account needed.

How demos work

The same engine your simulations run on.

Shared and public: Demo keys are published on purpose and everyone calls the same world, so treat anything you see there as public test data.
Still alive: The behaviour plan keeps running: records move through their states on a schedule, so a request in an hour returns different data from a request now.
Reset from time to time: We put demos back to their original seed regularly. Your own simulations only reset when you ask.
Rate limited: Demos are rate limited like any simulation. A 429 carries the same error envelope and Retry-After header your own simulations use.

Your own simulations add everything a demo leaves out: writes that persist, webhooks, failure rules, fast-forward, forks and snapshots, your own spec, and an IP allow-list and private key.

See plans Read the quickstart