API Reference

Tasks

Tasks are units of work with assignees, statuses, deadlines, and optional project links. Partner responses expose UUIDs; numeric foreign keys on the task root are stripped.

Last updated 2026-11-18

Overview

The Tasks API provides full CRUD for tasks in a workspace. Create tasks with a required `type`, assign them to people, link them to projects, and filter list results with rich query parameters.

Updates use PATCH (not PUT). Create and update are JSON-only; files go through the task attachment routes, which take URLs, inline base64 content or multipart uploads. Only `firm-team` and `team-only` tasks are returned; firm-only tasks are never visible through this API, whatever `visibility` you pass.

Key concepts

Required type on create

Every create request must include `type` — the task type identifier, `custom` for ordinary work.

UUID-resolvable foreign keys

Optional FK fields (`assigneeId`, `statusId`, `projectId`, and others) accept either a UUID or a workspace-scoped numeric id. Prefer UUIDs from list responses.

Visibility

List and get return `firm-team` and `team-only` tasks only. Firm-only tasks, including INTERNAL_TASK records, cannot be read, updated or deleted through this API.

Tags

Pass `tags` as an array of UUIDs or positive integer ids — all elements must be the same kind. On update, tags replace the full set atomically.

The task object

Core fields returned on task records. Nested people, status and project objects carry COUNT’s internal numeric `id`, not a UUID — read them for display, not as input to other routes.

Attributes

iduuid

Task identifier (UUID).

namestring

Task title.

typestring

Task type identifier, such as `custom`. Required on create.

descriptionstring

Task details. May be null.

statusenum

Status type of the task’s current status.

One of: not_started, in_progress, waiting_for_client, blocked, ready_for_review, done, canceled

priorityenum

Priority level.

One of: high, medium, low

visibilityenum

Who can see the task. Firm-only tasks are not returned by this API.

One of: firm-team, team-only

deadlineDatedatetime

Due date, at midnight UTC. May be null.

startDatedatetime

Start date. May be null.

completedAtdatetime

When the task was completed, or null.

customIdstring

Readable reference COUNT generates, such as `TODO-42`. Numbered per workspace, so not unique across workspaces.

budgetedMinutesinteger

Time budget in minutes. May be null.

isTimeTrackableboolean

Whether staff can log time against the task.

totalMinutesTrackedstring

Minutes logged against the task, as a numeric string.

creatorEntityenum

Which side created the task.

One of: accounting-firm, client

sourcestring

`ai_agent` for tasks an AI agent created, otherwise null.

assigneeobject

The assigned user: `firstName`, `lastName`, `avatarUrl`, and an internal numeric `id`.

assignerobject

Who assigned the task. Same shape as `assignee`.

createdByobject

Who created the task. Same shape as `assignee`.

taskStatusobject

The status the task is in: `name`, `statusType`, display colors and `order`.

projectsarray

Linked projects.

attachmentsarray

Files attached to the task.

createdAtdatetime

ISO 8601 creation timestamp.

updatedAtdatetime

ISO 8601 last update timestamp.

Example
{
  "id": "22334455-6677-8899-aabb-ccddeeff0011",
  "name": "Review wireframes",
  "type": "custom",
  "description": "Review and approve wireframes before development.",
  "status": "not_started",
  "priority": "medium",
  "visibility": "firm-team",
  "deadlineDate": "2026-04-15T00:00:00.000Z",
  "startDate": null,
  "completedAt": null,
  "customId": "TODO-42",
  "budgetedMinutes": null,
  "isTimeTrackable": false,
  "totalMinutesTracked": "0",
  "creatorEntity": "client",
  "source": null,
  "assignedAt": "2026-01-15T10:30:00.000Z",
  "assignee": {
    "id": 5521,
    "firstName": "Jane",
    "lastName": "Smith",
    "avatarUrl": null
  },
  "assigner": {
    "id": 5521,
    "firstName": "Jane",
    "lastName": "Smith",
    "avatarUrl": null
  },
  "createdBy": {
    "id": 5521,
    "firstName": "Jane",
    "lastName": "Smith",
    "avatarUrl": null
  },
  "taskStatus": {
    "id": 311,
    "name": "Not Started",
    "statusType": "not_started",
    "color": "#ACB2BD",
    "order": 0
  },
  "projects": [
    {
      "name": "Website Redesign"
    }
  ],
  "attachments": [],
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-01-28T14:22:30.000Z"
}

Legacy filters stripped

The list filters `clients`, `openTaskOnly`, and `isForClosing` are always removed server-side on partner routes.

Recent changes

2026-11-18

Incremental sync: updatedSince on every list endpoint, includeDeleted, and the deleted-records feed

Every Partner API list endpoint now takes updatedSince, so an integration can pull only what changed instead of re-reading whole lists. Pass an ISO 8601 date-time and the list returns the records created or changed at or after it, oldest change first, with nextUpdatedSince and hasMore beside the rows; pass nextUpdatedSince back as updatedSince to read the next page, and keep it for the next poll once hasMore is false. Paging by cursor means a record changed mid-walk can no longer move between pages and be skipped, so updatedSince cannot be combined with page above 1 or a sort. includeDeleted=true returns deleted records with isDeleted: true on vendors, customers, products, people, taxes, projects, project tasks, tasks, time entries, recurring invoice templates, the chart of accounts, transactions, invoices, and bills. The chart of accounts returns a flat list of changed accounts in this mode, each naming its parent in parentAccountUuid. Records removed outright — tags, tag groups, journal entry lines, expense receipts, customer contacts, addresses and notes, budgets, and any other hard delete — are listed by the new GET /partners/deleted-records, which keeps 90 days. updatedFrom and updatedTo stay on transactions, invoices, and bills, now read as UTC when they carry no offset. The new Keeping in Sync guide (/guides/keeping-in-sync) puts the pieces together into a 15-minute poll with a sync-now button. The MCP catalog adds COUNT_list_deleted_records, and every list tool takes updatedSince (and includeDeleted where it applies) under query.

2026-11-18Breaking

Every attachment in COUNT through the API and MCP

Attachments can now be listed, added, read back and removed through the Partner API on bills, invoices, recurring invoice templates, transaction receipts, manual journal entries, tasks, expense receipts, Documents and reconciliation bank statements. Each record type gains an `attachments` (or `receipts` / `bank-statement`) route that takes JSON entries, either `{ url }` (COUNT downloads and keeps its own copy) or `{ fileName, contentBase64, contentType? }`, plus an `/upload` route for multipart files. Files are capped per route (5 MB for invoices, templates, transaction receipts and Documents, 10 MB for expense receipts, 20 MB for bills, journal entries and tasks, 25 MB for bank statements), at most 10 per request, virus-scanned, and saved together or not at all. A new `/content` route on each returns one file base64-encoded (up to 10 MB), and GET /partners/documents/{uuid}/download-links returns signed view and download links. Breaking: `documentUrl`, `receiptUrl`, `pdfUrl` and `bankStatementUrl` in responses are now short-lived signed links, and `null` when COUNT cannot prove the file is the workspace's. POST /partners/invoices/{uuid}/attachments now stores a copy of each file and answers 201 with `data.attachments` instead of 200 with `data.invoice`. Invoice upload responses no longer include internal ids (`invoiceId`, `defaultInvoiceAttachmentId`, `recurringInvoiceTemplateId`, `uploadedBy`). Bill create and update accept inline content in `attachments`, and an empty list adds nothing. Attachment adds and content reads are limited to 40 a minute per client and workspace. The MCP catalog adds 35 tools, including a Documents category, and content tools deliver the file as an embedded resource rather than as text.

2026-10-23

Response examples checked against the live API

Every Practice Manager route was called with a firm API key and the reference corrected where it disagreed. Tasks: the due date field is deadlineDate on create and update (deadline is ignored), firm-only tasks are never returned whatever visibility you pass, and creating a task with type INTERNAL_TASK leaves it unreachable through the API, so the examples now use type custom; the task object lists the fields the API returns. Response examples now match the API for the documents list (documents and pagination) and get (data.document), the projects, tasks, time entries and customers lists, and the trial balance, profit and loss, balance sheet and aged receivables and payables reports. Documents no longer list folderPath, mimeType or fileSize, which were never returned. Firm tasks: a malformed clientWorkspaceUuids filter returns 404, and customId is numbered per client workspace. The Idempotency-Key error applies to writes only.

2026-09-07

Accounting Playbooks and Ledger Semantics published as documentation

The workflows and behaviour rules the MCP server serves to agents through COUNT_playbooks and COUNT_knowledge are now readable documentation. Accounting Playbooks (/guides/playbooks) covers nine ordered workflows across 54 steps — invoicing, credit memos, recurring templates, vendor bill payment, chart-of-accounts setup, migration imports, budget planning and round-trip, and month-end review — each naming the exact tool per step. Ledger Semantics & Lifecycles (/guides/ledger-semantics) documents 33 confirmed behaviours across twelve resources: the state each operation is valid in, the fields accepted and then ignored, and the calls that cannot be undone, with every irreversible behaviour collected in one table at the top of the page. Both pages carry the COUNT_playbooks and COUNT_knowledge ids they were ported from so the agent-facing and human-facing copies stay in step. Playbooks, lifecycle sections, and individual behaviour rules are indexed into site search.

2026-06-21

Complete Partner API reference

Documented all remaining API reference groups: Chart of Accounts, Vendors, Products & Services, Recurring Invoice Templates, Credit Memos, Bills, Journal Entries, Tags, People, Projects, Tasks, Time Entries, Expense Receipts, Reports, and Workspace Stats. Added missing invoice endpoints (audit log, attachments, credit application, remove transaction) and group overviews for Invoices and Transactions.

Endpoints