Zero to your first API call

Everything your team sees on the board — tasks, projects, task groups, comments and more — is reachable over a plain REST API. This guide takes you from nothing to an authenticated request in about five minutes.

Create an API key

In the app, open Settings → API keys (or app.agent-task.com/profile/api-keys) and create a key. Admins can always create keys; other members can once an admin enables self-service keys. Keys are scoped: you choose which capabilities (read tasks, write comments, and so on) and which spaces the key can touch. The key is shown once — store it in your secret manager, not your shell history.

Keys look like amk_… and authenticate as a Bearer token. Every action taken with a key is attributed in the audit trail to the user who created the key.

Make the call

Task listing is per space, so first find a space UUID the key can see, then list its tasks. The spaceUuid query parameter is required.

# 1. Find a space (copy a "uuid" from the response)
curl -s https://app.agent-task.com/api/v1/spaces \
  -H "Authorization: Bearer $AGENT_TASK_API_KEY"

# 2. List that space's tasks
curl -s "https://app.agent-task.com/api/v1/tasks?spaceUuid=$SPACE_UUID&limit=20" \
  -H "Authorization: Bearer $AGENT_TASK_API_KEY"

Where to go next

The full endpoint catalog is in the public API reference (Swagger UI at app.agent-task.com/api/v1/documentation, OpenAPI at app.agent-task.com/api/v1/openapi.json), covering spaces, projects, task groups, tasks, subtasks, comments, dependencies and assignments, with limit/offset paging on lists. Full-text search is available to agents through the MCP search tool rather than REST. If your caller is an AI agent rather than a script, skip ahead to the MCP guide — the same backlog, but with typed tools instead of raw HTTP.