Skip to content

Playground

A writable simulation from one call.

No account and no key to copy around. One request creates a small simulation of a real API, returns its address and key, and deletes it two hours later.

Ask your agent

Paste this into Claude Code, Codex, Cursor or Copilot. The agent makes the call and uses the key itself.

Try Slurry for me: POST https://api.slurry.io/v1/playground with the JSON body {"library":"jira"}, then call the samplePath it returns with its key, create a record and read it back. Do not print the key.

Or use curl

Needs jq. Run both commands from the same machine.

shell
PLAY=$(curl -s -X POST https://api.slurry.io/v1/playground \
  -H "Content-Type: application/json" \
  -d '{"library":"jira"}')

# first call: the samplePath for that API
curl -s "$(echo "$PLAY" | jq -r '.url + .samplePath')" \
  -H "Authorization: Bearer $(echo "$PLAY" | jq -r .key)"

What comes back

Send the key as Authorization: Bearer. It is shown once and stored only as a hash.

201 Created
{
  "url": "https://play-k3v9x2m1qa.slurry.io",
  "key": "slurry_sim_live_...",          // shown once
  "expiresAt": "2026-09-27T14:05:00.000Z",
  "library": "jira",
  "samplePath": "/rest/api/3/search?maxResults=5",
  "signUpUrl": "https://slurry.io/sign-up",
  "allowedIp": "203.0.113.9"
}

How it works

Real enough to build against, small enough to give away.

Two hours
Everything is deleted when it expires. After that the address answers 410 playground_expired.
Your IP only
The simulation only answers the address that created it, so the key is useless anywhere else. Create it from the machine that will call it.
Writable
Create, update and delete like the real API, up to 300 records. Webhooks, uploads and AI design are for accounts.
Limits
One active playground per IP address and three per 24 hours. Requests are rate limited and errors use the usual Slurry error envelope.

APIs you can try

Pass the slug as library. The live list is at GET https://api.slurry.io/v1/playground/libraries.

  • 1password-local-connect -
  • ably-platform -
  • adobe-aem -
  • adyen -
  • airbyte-local-config -
  • akeneo -
  • anchore -
  • apache-airflow -
  • api2cart -
  • apideck-accounting -
  • apideck-ats -
  • api-video -
  • apple-app-store-connect -
  • appwrite-server -
  • asana -
  • autotask -
  • avaza -
  • azure-devops -
  • bigredcloud -
  • billbee -
  • bitbucket -
  • box -
  • braze -
  • buildkite -
  • bulksms -
  • bunq -
  • calendly -
  • callfire -
  • chatwoot -
  • clarity-ppm -
  • clever -
  • clicksend -
  • codat-sync-for-commerce -
  • configcat -
  • confluence -
  • digitalocean -
  • discord -
  • discourse-local -
  • docker-engine -
  • docusign -
  • dracoon-team -
  • drchrono -
  • dynamics-365-business-central -
  • ecwid -
  • enode -
  • exavault -
  • files -
  • fire -
  • formapi -
  • getpostman -
  • gitea -
  • github -
  • gitlab -
  • gmail -
  • gong -
  • google-calendar -
  • google-contacts -
  • google-directory -
  • google-drive -
  • google-meet -
  • grain -
  • graphhopper -
  • hetzner-cloud -
  • hubspot -
  • influxdata -
  • intercom -
  • izettle-products -
  • jira -
  • jira-service-management -
  • jumpseller -
  • just-eat-uk -
  • keycloak-local -
  • klarna-payments -
  • kubernetes -
  • launchdarkly -
  • linode -
  • loket-nl -
  • magento -
  • mandrillapp -
  • mastodon-local -
  • meraki -
  • microsoft-entra-directory -
  • microsoft-forms-excel -
  • microsoft-project -
  • microsoft-teams -
  • microsoft-teams-meetings -
  • monday -
  • netbox -
  • netlify -
  • netsuite -
  • nordigen -
  • notion -
  • okta -
  • onedrive -
  • onsched-consumer -
  • openai -
  • openbanking-uk-account-info-openapi -
  • otter -
  • outlook-calendar -
  • outlook-contacts -
  • outlook-mail -
  • pagerduty -
  • paylocity -
  • payments-service-gov-uk-payments -
  • pendo -
  • personio-de-personnel -
  • pipedrive -
  • plaid -
  • planview-portfolios -
  • postmarkapp-server -
  • power-bi -
  • read-ai -
  • readme -
  • rebilly -
  • recall-ai -
  • reverb -
  • royal-mail -
  • sakari -
  • salesforce -
  • salesforce-marketing-cloud -
  • salesloft -
  • sap-s4hana-projects -
  • sap-successfactors -
  • sendgrid -
  • servicenow-spm -
  • sharepoint-sites -
  • shipengine -
  • slack -
  • smartsheet -
  • snyk -
  • spotify -
  • squareup -
  • storecove -
  • stripe -
  • superset-apache-local-superset -
  • taxamo -
  • telegram-bot-api -
  • telnyx -
  • tfl-gov-uk -
  • tldv -
  • traccar -
  • truora -
  • twilio -
  • twilio-messaging -
  • up-au -
  • velopayments -
  • vercel -
  • viator -
  • victorops -
  • workday -
  • xero-xero-accounting -
  • yapily -
  • youneedabudget -
  • zendesk -
  • zoom-meetings -
  • zuora -

An account keeps simulations for as long as you want, with webhooks, failure rules, fast-forward, forks, snapshots, your own spec and one world of people shared across every API.