turbinelabs.io

Turbine Labs sandbox and mock API

The Turbine Labs API provides CRUD operations for core object types, and is mostly RESTy. The easiest way to interact with the API is with [tbnctl](https://docs.turbinelabs.io/advanced/tbnctl.html). If you want to make direct HTTP calls, however, you can obtain an access token using tbnctl, and then pass it in the Authorization header, prefixed by `Token `: ```console curl -H "Authorization: Token Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations: 44
Collections: -
Event types: -

Start this simulation

example request

curl https://your-turbinelabs.slurry.io/v1.0/admin/user/self \
  -H "Authorization: Bearer slurry_sim_..."

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

GET/admin/user/self
DELETE/admin/user/self/access_token/{access-token-key}
GET/admin/user/self/access_tokens
POST/admin/user/self/access_tokens
GET/changelog/adhoc
GET/changelog/cluster-graph/{clusterKey}
GET/changelog/domain-graph/{domainKey}
GET/changelog/route-graph/{routeKey}
GET/changelog/shared-rules-graph/{sharedRulesKey}
GET/changelog/zone/{zoneKey}
GET/cluster
POST/cluster