API Reference

Tags

Tags are workspace labels used to classify transactions, journal entries, invoices, bills, and other records. Tag groups organize related tags — each tag may belong to at most one group.

Last updated 2026-11-18

Overview

The Tags API covers both individual tags and tag groups. Tags are simple name labels; tag groups bundle tags under a named, optionally colored container for structured reporting.

Partner responses expose UUIDs as `id`. When creating or updating tag groups, pass `tagUuids` (from list tags) — the server resolves UUIDs to internal ids. A tag can belong to at most one group at a time.

Key concepts

Tags vs tag groups

Tags are flat labels. Tag groups collect tags for UI grouping and reporting. Manage tags at `/partners/tags` and groups at `/partners/tags/groups`.

Where tags go

Bills take tags per line in `lineItems[].tagUuids`, which code that line's expense and tax postings, and bill-level `tagUuids`, which apply to every posting. Manual journal entries take tags per line in `lines[].tagUuids`. Invoices, credit memos and recurring invoice templates take `tagUuids` for the whole document only.

One group per tag

Each tag may belong to at most one group. Assigning a tag that is already in another group returns 400.

Group membership replacement

On tag group update, sending `tagUuids` replaces the entire membership set — tags omitted are removed from the group. Pass `[]` to clear all tags.

Idempotent tag create

Creating a tag with a name that already exists returns the existing tag rather than duplicating it.

The tag object

Fields returned on a tag. Tag groups embedding the tag may appear under `tagGroups`.

Attributes

iduuid

Tag identifier (UUID).

namestring

Tag label. Required and unique per workspace on create.

tagGroupsarray

Tag groups this tag belongs to (at most one in practice).

iduuid

Tag group UUID.

namestring

Group name.

colorstring

Group color.

createdAtdatetime

ISO 8601 creation timestamp.

updatedAtdatetime

ISO 8601 last update timestamp.

Example
{
  "id": "e5f6a7b8-c9d0-1234-efab-345678901234",
  "name": "Office",
  "tagGroups": [
    {
      "id": "f6a7b8c9-d0e1-2345-fabc-456789012346",
      "name": "Department",
      "color": "#4A90D9"
    }
  ],
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-01-28T14:22:30.000Z"
}

List tag groups includes ungrouped tags

GET /partners/tags/groups returns both `tagGroups` and `unGroupedTags` — tags not assigned to any group.

Deleting a tag removes associations

Deleting a tag clears its links to transactions, journal entries, invoices, bills, and other tagged records.

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-18

Line tags, foreign-currency rates, transfers and journal balance checks

Documented behaviour the reference was missing or had wrong. Bill lines take their own tags in `lineItems[].tagUuids`, which code that line's expense and tax postings, and manual journal lines take `lines[].tagUuids`; invoices take `tagUuids` for the whole document, on create and update. Bills and invoices in another currency are booked at the spot rate for their date, and `bookingExchangeRate` with `exchangeRateSource: "user"` sets your own rate; COUNT revalues open foreign AR, AP and accounts at each month end and posts realised gains and losses on payment. A transfer is a transaction categorized to another bank, cash, credit card or loan account, and change-category takes `linkedTransferTransactionUuid` to pair it with an existing row; bulk category change rejects those accounts. Journal entry create accepts unbalanced postings, while update requires debits to equal credits; the reference previously said create rejected them.

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