Start
Authentication and scopes
FleetDeck keys bind every request to explicit phones, permissions and an owning workspace.
Bearer keys
Authorization: Bearer $FLEETDECK_API_KEYUse the header on /api/v1/*, the remote MCP endpoint and the CLI. Credentials belong in a protected environment. Do not put them in URLs, shell arguments, screenshots or logs.
Scopes
| Scope | Permission |
|---|---|
devices:read | List devices and capabilities; acquire sessions; screenshot, inspect and apps; list jobs, saved sequences, touch schedules and runs. |
devices:control | Touch, text, keys, buttons, URLs, app launch/stop, clipboard writes and running saved sequences. |
devices:media | Import JPEG, PNG or MP4 media, including chunked uploads. |
devices:advanced | Read clipboard and execute discovered native extensions. |
jobs:write | Schedule and cancel this key’s jobs; create, pause and delete touch schedules. Creating or resuming also requires devices:control. |
worker:run | Claim/report native bridge actions or run jobs created by the same key. |
Scope checks combine with device grants, current account membership and active device entitlement. Passing one check does not bypass another.
Expiry
User keys accept 1 to 365 days, or no configured expiry. Session expiry is returned by the server and may be shorter than requested. Job child credentials renew in 15-second windows and remain capped by their job deadline and parent expiry.
Dashboard routes
The three /api/agent-keys endpoints use the signed-in dashboard cookie. Mutations also require a same-origin Origin header. Bearer keys cannot create, list, revoke or purge keys.
