Developers
Put device operations in your tools.
Use the organization API from CI, provisioning scripts, or your support console.
Authenticate with an organization API token. Keep it server-side. Embed a shell in your support console, or queue a command and read the result back.
Example command request
POST /api/v1/devices/0199a3c2-…/commands
Authorization: Bearer CPorg_…
Content-Type: application/json
{"script": "uptime"}
Response
HTTP/1.1 200 OK
{"command": {
"id": "0199a3c4-…",
"status": "queued",
"type": "shell",
"script": "uptime",
"exit_code": null,
"stdout": null,
"stderr": null,
"not_before": null,
"claimed_at": null,
"completed_at": null,
"inserted_at": "2026-09-02T14:02:52Z",
"device_id": "0199a3c2-…",
"organization_id": "0199a3b9-…"
}}
The API at a glance.
-
GET
/api/v1/devices - List devices.
-
GET
/api/v1/devices/lookup - Find a device.
-
POST
/api/v1/devices/:id/commands - Queue a command.
-
GET
/api/v1/devices/:id/commands - Read command results.
-
POST
/api/v1/enrollment_links - Create an install link.
-
POST
/api/v1/devices/:id/embeds/shell - Create a shell embed.
-
POST
/api/v1/devices/:id/tunnels - Open a temporary tunnel.