Start
Tutorial: call a twin from CI
Issue a key, point the test base URL at the twin, and flip the scenario from the pipeline.
On Keys, create a key. It is shown once and starts with at_live_. Store it as a CI secret. A private twin rejects calls that do not send it. A public twin does not need it for /sim/{slug}, but the control API always does.
curl -sS https://apitwin.dev/api/v1/twins \
-H 'authorization: Bearer at_live_...'
curl -sS -X POST https://apitwin.dev/api/v1/twins/YOUR-SLUG/scenario \
-H 'authorization: Bearer at_live_...' \
-H 'content-type: application/json' \
-d '{"scenario":"outage"}'Outage makes the twin return 503 and leaves state unchanged. Set the scenario back to default when the drill is over. Degraded applies the latency and error rate saved on the Faults tab.