Pokee Enterprise APIOverview
A REST API for running long-form agent-driven workflows in a dedicated, persistent sandbox.
The Pokee Enterprise Responses API lets you run long-form, agent-driven workflows inside a dedicated, persistent sandbox. Each tenant gets a private workspace, a stable bearer token, and a set of HTTP endpoints for sessions, files, and streaming messages.
Your endpoint looks like:
https://your-tenant.enterprise.pokee.aiEndpoints
| Path | Methods | Purpose |
|---|---|---|
/health | GET | Liveness check (no auth) |
/v1/sessions | POST | Create a session |
/v1/sessions | GET | List sessions |
/v1/sessions | DELETE | Bulk-delete by status / age |
/v1/sessions/{id} | GET | Get session details |
/v1/sessions/{id} | DELETE | Destroy a session |
/v1/sessions/{id}/messages | POST | Send a message (streams response) |
/v1/sessions/{id}/files | GET | List files in workspace |
/v1/sessions/{id}/files/{path} | GET | Download a file |
/v1/sessions/{id}/files/{path} | PUT | Upload a file |
/v1/sessions/{id}/files/{path} | DELETE | Delete a file |
/v1/usage | GET | Rolling usage + credit balance |
All endpoints except /health require an Authorization: Bearer ${POKEE_KEY} header. Errors come back as JSON {"error": "<name>", "message": "<detail>"} with the HTTP status code matching the failure class (400 / 401 / 402 / 403 / 404 / 409 / 416 / 429 / 500 / 503).