Skip to content
Cloud infrastructure/devops

ably.net:control

Control API v1 sandbox and mock API

Use the Control API to manage your applications, namespaces, keys, queues, rules, and more. Detailed information on using this API can be found in the Ably <a href="https://ably.com/documentation/control-api">developer documentation</a>. Control API is currently in Beta. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
22
Collections
-
Event types
-
Start this simulation
example request
curl https://your-ably-control.slurry.io/v1/me \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/accounts/{account_id}/apps
  • POST/accounts/{account_id}/apps
  • GET/apps/{app_id}/keys
  • POST/apps/{app_id}/keys
  • PATCH/apps/{app_id}/keys/{key_id}
  • POST/apps/{app_id}/keys/{key_id}/revoke
  • GET/apps/{app_id}/namespaces
  • POST/apps/{app_id}/namespaces
  • PATCH/apps/{app_id}/namespaces/{namespace_id}
  • DELETE/apps/{app_id}/namespaces/{namespace_id}
  • GET/apps/{app_id}/queues
  • POST/apps/{app_id}/queues