---
title: "Tasks API · COUNT Partner API"
description: "Tasks are units of work with assignees, statuses, deadlines, and optional project links. Partner responses expose UUIDs; numeric foreign keys on the task root…"
canonical: "https://developers.getcount.com/reference/tasks"
source: "https://developers.getcount.com/reference/tasks"
---
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-06-21

## 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). The partner endpoint is JSON-only — multipart attachments are not supported. Default list visibility includes `firm-team` and `team-only` tasks; pass `visibility=firm-only` to include firm-only rows such as system-generated INTERNAL_TASK records.

## Key concepts

### Required type on create

Every create request must include `type` — the task type identifier for your workspace (for example INTERNAL_TASK).

### 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 defaults to firm-team and team-only tasks. Retrieve firm-only tasks by passing `visibility=firm-only` on get and list when needed.

### 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 assignee, status, and project objects expose UUIDs.

#### Attributes

`id` uuid

Task identifier (UUID).

`name` string

Task title.

`type` string

Task type identifier. Required on create.

`description` string

Task details.

`priority` string

Priority level (for example low, medium, high).

`deadline` date

Due date (YYYY-MM-DD).

`customId` string

Optional external reference id.

`visibility` enum

Visibility scope. INTERNAL_TASK rows are always created as firm-only.

One of: `firm-team`, `team-only`, `firm-only`

`assignee` object

Assigned workspace user, or null.

`project` object

Linked project, or null.

`tags` array

Tags attached to the task.

`createdAt` datetime

ISO 8601 creation timestamp.

`updatedAt` datetime

ISO 8601 last update timestamp.

Example

```json
{
  "id": "22334455-6677-8899-aabb-ccddeeff0011",
  "name": "Review wireframes",
  "type": "INTERNAL_TASK",
  "description": "Review and approve wireframes before development.",
  "priority": "medium",
  "deadline": "2026-04-15",
  "customId": "TASK-1042",
  "visibility": "firm-team",
  "assignee": {
    "uuid": "f1a2b3c4-d5e6-4789-a012-3456789abcde",
    "firstName": "Jane",
    "lastName": "Smith"
  },
  "project": {
    "uuid": "11223344-5566-7788-99aa-bbccddeeff00",
    "name": "Website Redesign"
  },
  "tags": [],
  "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.

## Related

- [Projects API](https://developers.getcount.com/reference/projects)
- [People API](https://developers.getcount.com/reference/people)

## Recent changes

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

[GET List tasks `/partners/tasks` Returns a paginated list of tasks.](https://developers.getcount.com/reference/tasks/list-tasks) [GET Get a task `/partners/tasks/{uuid}` Retrieves a single task by UUID.](https://developers.getcount.com/reference/tasks/get-task) [POST Create a task `/partners/tasks` Creates a new task.](https://developers.getcount.com/reference/tasks/create-task) [PATCH Update a task `/partners/tasks/{uuid}` Updates an existing task. Only the fields you send are changed.](https://developers.getcount.com/reference/tasks/update-task) [DELETE Delete a task `/partners/tasks/{uuid}` Deletes a task by UUID.](https://developers.getcount.com/reference/tasks/delete-task)