Skip to content
Communication/messaging

slack.com

Slack sandbox and mock API

One way to interact with the Slack platform is its HTTP RPC-based Web API, a collection of methods requiring OAuth 2.0-based user, bot, or workspace tokens blessed with related OAuth scopes. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
174
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-slack.slurry.io/api/admin.apps.approved.list \
  -H "Authorization: Bearer slurry_sim_..."

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

  • POST/admin.apps.approve
  • GET/admin.apps.approved.list
  • GET/admin.apps.requests.list
  • POST/admin.apps.restrict
  • GET/admin.apps.restricted.list
  • POST/admin.conversations.archive
  • POST/admin.conversations.convertToPrivate
  • POST/admin.conversations.create
  • POST/admin.conversations.delete
  • POST/admin.conversations.disconnectShared
  • GET/admin.conversations.ekm.listOriginalConnectedChannelInfo
  • GET/admin.conversations.getConversationPrefs