Reference
Control API
Create twins, read logs, import specs, and change the scenario with a key.
Every control call needs Authorization: Bearer at_live_... or x-api-key. The key acts as the workspace.
GET /api/v1/twins
POST /api/v1/twins
{ "name", "slug?", "preset?", "description?", "visibility?" }
GET /api/v1/twins/{slug}
POST /api/v1/twins/{slug}/routes
DELETE /api/v1/twins/{slug}/routes
GET /api/v1/twins/{slug}/logs
POST /api/v1/twins/{slug}/scenario
{ "scenario": "default" | "degraded" | "outage" }
POST /api/v1/twins/{slug}/import
GET /api/v1/twins/{slug}/driftpreset is blank, rest, grpc, graphql, orders, payments, or openai. visibility is public or private. POST /routes uses the same fields as the route form: name, method, path, behavior, status, headers, body, delay_ms, priority, collection, and rules.
On the twin itself, without the control prefix: GET /sim/{slug}/__routes, GET /__openapi, GET /__drift on Developer, and POST /__reset to clear state.