API keys

Authenticate programmatic access to RunMyCrew.

What API keys are for#

Use a key to trigger workflows, read runs, or manage resources from your own code. For calling other apps from inside a workflow, use connections instead.

Create a key#

POST /api/v1/api-keys
{ "name": "CI pipeline" }
 
# → token shown ONCE:
{ "key_preview": "fuse_live_…abcd", "token": "fuse_live_…" }

Using a key#

Send it as a header — either works:

x-api-key: fuse_live_…
# or
Authorization: Bearer fuse_live_…

See the full Authentication reference for workspace scoping.

Rotate & revoke#

Keys are stored as SHA-256 hashes — the plaintext can’t be recovered, so treat the one-time token like a password. List keys with GET /api-keys and revoke instantly with DELETE /api-keys/{id}. Rotate by creating a new key, switching your clients over, then deleting the old one.