REST API Endpoints

Mission Control’s REST API

Every operation available through the Mission Control dashboard is also available via REST API. This makes it straightforward to integrate Mission Control into CI/CD pipelines, scripts, or custom tooling.

Authentication

All API endpoints require a bearer token. Include it in the Authorization header:

Authorization: Bearer <your-token>

Bearer tokens are configured in Mission Control’s settings. Requests without a valid token receive a 401 Unauthorized response.

Task Endpoints

List tasks

GET /api/tasks

Returns an array of all tasks with their current status, priority, and metadata. Supports query parameters for filtering by status (?status=pending) and sorting (?sort=priority).

Create a task

POST /api/tasks

Body: { title, description, priority, tags }. Returns the created task object with its assigned ID.

Get a task

GET /api/tasks/:id

Returns a single task including its full description, status history, and any associated planning output.

Update a task

PATCH /api/tasks/:id

Update any mutable fields (title, description, priority, tags, status).

Delete a task

DELETE /api/tasks/:id

Permanently removes the task and its associated activity log.

Agent Endpoints

List agents

GET /api/agents

Returns all configured agent profiles and their current availability status.

Dispatch a task

POST /api/tasks/:id/dispatch

Body: { agentId }. Dispatches the task to the specified agent. Returns the updated task with in_progress status.

Validation

All request bodies are validated with Zod schemas. Invalid requests receive a 400 Bad Request response with a structured error object describing which fields failed validation and why.

Rate Limits

The local API does not enforce rate limits by default. If you expose Mission Control to a network, consider adding rate limiting at the reverse proxy layer.