Tasks

​

Endpoints

​

Example: import tasks

curl "https://unify.bundleup.io/v1/tasks/tasks?limit=100" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "BU-Connection-Id: conn_abc123"

const unify = client.unify('conn_abc123');
const tasks = await unify.tasks.tasks({ limit: 100 });

unify = client.unify("conn_abc123")
tasks = unify.tasks.tasks({"limit": 100})

unify = client.unify('conn_abc123')
tasks = unify.tasks.tasks(limit: 100)

{
  "data": [
    {
      "id": "ENG-142",
      "title": "Login button does nothing on Safari",
      "status": "In Progress",
      "url": "https://linear.app/acme/issue/ENG-142",
      "description": "Steps to reproduce...",
      "created_at": "2026-09-02T08:14:00Z",
      "updated_at": "2026-09-10T16:40:00Z"
    }
  ],
  "metadata": { "next": "Mg==" }
}

​

Response notes

• status is the provider’s own status name (To Do, In Progress, Done, or whatever the customer configured). Trackers let teams define their own workflows, so there’s no fixed list. Map statuses in your product if you need categories.
• description is the provider’s text, in its own format (Markdown, HTML or plain text, depending on the tool).
• id is what you pass to GET /v1/tasks/tasks/{id}.

​

Provider differences

• What a “project” is depends on the tool: a project, a board, a list, a team or a workspace.
• Single tasks aren’t available everywhere. Some tools only address a task through its parent project, so an ID alone can’t fetch it. Basecamp is one. For those, use the list endpoint, or the Proxy.
• Writes (creating tasks, changing status, commenting) aren’t part of the Unified API. Use the Proxy.