Resources

Changelog

Notable changes to the Partner API and this documentation.

2026-11-19

Rate limits per user of each app

The Partner API and the Practice Manager API now allow 100 requests per minute per user of each app, with a ceiling of 10,000 per minute per app across all its users, counted across every server. Before, the limit was 100 per minute for the whole app. Token requests, and Practice Manager calls made with an API key and no user token, count 100 per minute per clientId. Every response carries `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` for whichever limit is closer to running out, and a 429 includes `Retry-After`.

2026-11-19

fixed-assets, reports, bills, transactions

Fixed assets

The asset register is on the Partner API and MCP. /partners/fixed-asset-types lists, gets, creates, updates and deletes asset types (each with its cost, accumulated depreciation and depreciation expense accounts and default depreciation settings). /partners/fixed-assets lists the register (status, type, search, sort, paging), gets one asset with its posted depreciation, updates and deletes drafts, merges two drafts (POST /merge-drafts) and projects depreciation (GET /{uuid}/projected-depreciation-schedule). POST /{uuid}/register, /unregister and /dispose run the lifecycle; a disposal posts its catch-up depreciation and journal together and refuses a sale missing the account its outcome needs. GET and POST /{uuid}/journal-links and DELETE /{uuid}/journal-links/{linkUuid} manage the journal lines behind an asset's cost, GET /{uuid}/audit-log returns its history, and /{uuid}/attachments lists, adds (multipart or URL) and deletes its files. GET /partners/fixed-asset-depreciation-rates returns the country's reference rates. POST /partners/reports/depreciation-schedule, /asset-register and /fixed-asset-reconciliation generate the fixed asset reports. Bill lines and transaction category changes accept `fixedAssetAssignment` with `fixedAssetUuid` / `fixedAssetTypeUuid`. These routes need the new `fixed-assets` scope (a bare `read` / `write` grant includes it; the reports need `reports:read`) plus View Fixed Assets to read and Administer Fixed Assets to change. The same routes work on client workspaces under /firm-partners/workspace. The MCP catalog adds 22 fixed asset tools and 3 report tools.

2026-11-18

payment-batches

Payment batches

In New Zealand workspaces, /partners/payment-batches builds and pays batch payments: GET lists batches (status, limit, offset) and GET /{uuid} returns one with its lines and approvers; POST creates a draft, POST /{uuid}/lines adds approved bills, DELETE /{uuid}/lines/{lineUuid} removes one, POST /{uuid}/approvers sends it for approval (GET /approvers lists who can approve), POST /{uuid}/approve and /reject decide it, POST /{uuid}/cancel cancels it, and POST /{uuid}/file returns the bank file of a ready batch and moves it to downloaded. Whoever creates a batch cannot approve it. These routes need the new `payment-batches` scope, which neither `bills` nor a bare `read` / `write` grant includes (COUNT's own MCP connector excepted), and the batch payment permissions. The same routes work on client workspaces under /firm-partners/workspace. The MCP catalog adds 11 payment batch tools, which are not offered inside COUNT AI chat.

2026-11-18

vendor-bank-accounts

Supplier bank accounts

In New Zealand workspaces, GET /partners/vendor-bank-accounts lists the bank accounts suppliers are paid into by batch payment (optionally one supplier, or those changed since `updatedSince`), GET /partners/vendor-bank-accounts/{vendorUuid} returns one supplier's account, and GET /partners/vendor-bank-accounts/{vendorUuid}/changes its change history. POST /partners/vendor-bank-accounts/{vendorUuid}/changes asks to add, replace or remove the account: the change waits for someone other than the requester to approve it in COUNT, and only one can wait per supplier (409). Reads return the full account number. These routes need the new `vendor-bank-accounts` scope, which neither `vendors` nor a bare `read` / `write` grant includes (COUNT's own MCP connector excepted), plus View Vendor Bank Details to read and Manage Vendors to request. The same routes work on client workspaces under /firm-partners/workspace. The MCP catalog adds COUNT_list_vendor_bank_accounts, COUNT_get_vendor_bank_account, COUNT_list_vendor_bank_account_changes and COUNT_request_vendor_bank_account_change, which are not offered inside COUNT AI chat.

2026-11-18

deleted-records, vendors, customers, products-and-services, people, taxes, tags, projects, tasks, time-entries, expense-receipts, budgets, chart-of-accounts, journal-entries, recurring-invoice-templates, transactions, invoices, credit-memo, bills

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

bills, invoices, journal-entries, transactions, tags

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

taxes, invoices, credit-memo, recurring-invoice-templates, bills, customers, chart-of-accounts, products-and-services

Line taxes on invoices and bills, split by US and NZ

Documented the line tax fields the reference was missing and how each behaves in US and NZ workspaces. Bill lines take one tax code in `lineItems[].taxUuid` (NZ: the GST code; US: ignored, bills carry no tax), and bill responses show it as `appliedTax`. Invoice, credit memo and recurring template lines take tax code UUIDs in `taxes`, the document takes `productsPriceType` (`tax-exclusive` or `tax-inclusive`), and `nonTaxable` and `customerExemptionOverridden` now say what they do in each country: in the US a Non-Taxable line keeps its code, in NZ it is cleared. The Taxes page lists the five NZ GST codes, where each reports on the GST return (Zero Rated in boxes 5 and 6, No GST nowhere), and which accounts each fits. Customer `taxExcluded` is a tax exemption, not tax-exclusive pricing, and customer and account `taxes` take tax UUIDs. A US / NZ switch in the header, and on every page with country-specific rules, shows one country's notes at a time; links can open in either view with `?region=us` or `?region=nz`.

2026-11-18

Breaking — see policybills, invoices, recurring-invoice-templates, transactions, journal-entries, tasks, expense-receipts, documents, reconciliations

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

taxes, people

Create, edit and delete tax codes and people

Tax codes are no longer read-only. GET, PATCH and DELETE /partners/taxes/{uuid} and POST /partners/taxes get, create, edit (name, rate, description, enabled) and delete a code, with the COUNT app's rules: no two codes with the same name and rate, system codes keep their name and rate, a code posted to the ledger keeps its rate, and the rate cannot be negative. GET /partners/taxes/sales-tax-rate looks up the US sales tax rate for an address without saving anything. People gain POST /partners/people, PATCH and DELETE /partners/people/{uuid}, PATCH .../enabled (send the status you want), PATCH .../terminate, POST .../resend-invite, POST .../resend-onboarding-email, POST and DELETE .../expense-reporter, and list, get, create, update and delete under .../jobs, where a job's title names an existing position. Bank accounts, tax identification numbers and adding or removing the payroll role stay in the COUNT app, and person responses no longer include sign-in tokens, tax identification numbers (including on a contractor's vendor), bank account numbers or internal ids. Tax writes need workspace:write; people writes need people:write. The same routes work on a client workspace through the Practice Manager API under /firm-partners/workspace. The MCP catalog adds 17 tools: COUNT_get_tax, COUNT_create_tax, COUNT_update_tax, COUNT_delete_tax, COUNT_get_sales_tax_rate, COUNT_delete_person, COUNT_set_person_enabled, COUNT_terminate_person, COUNT_resend_person_invite, COUNT_resend_payroll_onboarding_email, COUNT_add_expense_reporter, COUNT_remove_expense_reporter, and five person job tools.

2026-11-14

reports, taxes, workspace-events, journal-entries, projects

Cash flow forecast, GST return and audit report, tax codes, workspace events, and 17 MCP tools

Documented the six partner routes the reference was missing. POST /partners/reports/cash-flow-forecast forecasts cash for the next 13 weeks, with an optional what-if scenario (customer payment delays, bill payment dates and one-off or repeating adjustments) returned as scenarioForecast. GET /partners/reports/gst-return calculates an NZ GST return without filing it, including the reconciliation that decides whether COUNT would let it file, and GET /partners/reports/gst-audit-report lists the transactions behind it, flags the ones with a GST issue, and pages 200 rows at a time. GET /partners/taxes lists the workspace tax codes and their UUIDs. GET /partners/workspace-events returns what changed since the user last checked: invoices paid, failed invoice payments, new bills and bank feed syncs. GET /partners/journal-entries/{uuid} returns one posting with every line. Taxes and workspace events are also reachable through the Practice Manager client-workspace routes. npm run check:parity now reports 186 documented routes against 186 backend routes. The MCP catalog adds COUNT_list_taxes, COUNT_list_workspace_events, COUNT_get_journal_entry, COUNT_generate_cash_flow_forecast, COUNT_get_gst_return, COUNT_get_gst_audit_report, COUNT_propose_transaction_categories, four position tools (COUNT_get_all_positions, COUNT_create_position, COUNT_update_position, COUNT_delete_position), and five firm tools for client status and client questionnaires. COUNT_delete_project is now COUNT_archive_project, and DELETE /partners/projects/{uuid} is documented as the archive it is, with its real response (result.success). Also, COUNT_get_bulk_task_status, which the server no longer registers, is removed.

2026-10-30

firm

Create client workspaces with a firm API key

POST /firm-partners/firm/clients creates a client workspace with its own books, owned and paid for by the firm, with no consent screen. The same key reaches it at once through /firm-partners/workspace with count-workspace-id set to the returned workspace.id. It needs firm:write and a key with access to all client workspaces. Send externalReference, your own id for the client, to make retries safe: a firm client with that reference is returned with 200 and created: false, and a concurrent call gets 409. GET /firm-partners/firm/clients now returns externalReference. Client workspace routes now also cover budgets, bank connections, reconciliations, opening balances, account sub-types, workspace settings and webhooks.

2026-10-23

tasks, documents, projects, time-entries, customers, reports, firm-tasks

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-10-08

documents

Rename documents through the update route

PUT /partners/documents/{uuid} documents newFileName, which renames a file within its folder; a name with any of \ / : * ? " < > | $, or longer than 255 characters, is refused with 400. The reference no longer lists folderPath on that route, which the backend never read.

2026-10-06

documents

Document types and periods

Documents now carry a document type, listed under a type group, and the period they cover. GET /partners/document-types lists the types a workspace can use: COUNT's built-in types for its country plus its own custom types. Document responses gain documentType (with its documentTypeGroup), documentTypeSource, periodStartDate, periodEndDate and periodSource. The document list filters by documentTypeUuids and documentTypeGroupUuids. PUT /partners/documents/{uuid} sets or clears a document's type (documentTypeUuid) and period (periodStartDate and periodEndDate); a value set this way is marked person and is never overwritten by COUNT's AI classifier.

2026-10-03

bills, invoices, credit-memo, reconciliations, reports

Bill submit and refunds, reconciliation drafts, report filters, 30 MCP tools, and the Claude plugin

Documented the five partner routes the reference was missing: POST /partners/bills/{uuid}/submit, POST /partners/bills/{uuid}/assign-transaction (pay a bill, or refund a vendor memo with an income transaction), PATCH /partners/invoices/{uuid}/add-transactions (including credit memo refunds), and PATCH and DELETE /partners/reconciliations/{uuid} for correcting or discarding a draft. The account transactions report gains a reference-number range (checkNumberFrom/checkNumberTo) and the unknown-counterparty drill-down (unknownCustomerAr/unknownVendorAp), both accrual-only. Invoice and credit memo lines accept free-text Custom lines with categoryAccountUuid and name. Corrected the reference where it disagreed with the backend: dueDate is required on invoices and estimates, bills move through submitted and rejected as well as draft and approved, and a bill does have its own assign-transaction route. npm run check:parity now reports 178 documented routes against 178 backend routes. The MCP catalog adds 30 tools — customer contacts, addresses, notes, merge and revenue overview, GST settings, bill submit and memo refunds, reconciliation draft update/delete, COUNT_find_tool, COUNT_report_problem, and saved AI skills — moving the advertised count from 180 to 210. New pages cover the COUNT Claude plugin (/tools/claude-plugin) and the MCP brain, workspace memory and problem reports (/guides/mcp-brain-and-memory), and the FAQ gains the connector and API topics COUNT_knowledge serves to agents.

2026-09-22

customers, workspace, invoices, projects, transactions

Customer sub-resources, merge, GST settings, and the last bulk routes

Closed every remaining gap between the reference and the backend partner routes — 20 endpoints that existed in count-dev but had no documentation. Customers gained its sub-resources: contacts, addresses, and notes each get full list/create/update/delete coverage, plus GET /partners/customers/{uuid}/revenue-overview and the two-step merge flow (POST /partners/customers/merge/preview, then POST /partners/customers/merge), which repoints every record onto a target customer and cannot be undone through the API. Workspace gained GET and PATCH /partners/workspace/gst-settings, including the manage_settings permission the PATCH requires and the 409 that locks the accounting basis after a return is filed. Also documented GET /partners/invoices/generate/number, POST /partners/projects/bulk, and POST /partners/transactions/review-bulk. npm run check:parity now reports 173 documented routes against 173 backend routes.

2026-09-07

invoices, credit-memo, recurring-invoice-templates, bills, transactions, journal-entries, chart-of-accounts, vendors, tags, expense-receipts, tasks, people

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-09-01

reports

Account transactions report and a complete MCP tool catalog

Documented POST /partners/reports/account-transactions, the general-ledger detail report, which was the only backend partner route missing from the reference. Brought the MCP tool catalog back in line with the remote server: added the six report tools (aged receivables/payables, sales by product-service, sales by customer, customer activity, account transactions), ten remote-only Payroll tools covering people, pay stubs, PTO accrual caps, and locations, and a new remote-only Firm Practice Manager category of eleven firm-wide task, time-entry, and project tools. The advertised tool count moves from 153 to 180; the three deprecated-name invoice aliases stay excluded.

2026-07-28

connections, reconciliations, opening-balance, workspace, transactions, bills, invoices

Connections, reconciliations, opening balance, workspace cutover, and transaction bulk ops

Documented Partner API groups for bank Connections (including Plaid Hosted Link connect/complete/reconnect), Reconciliations (create draft + complete), Opening Balance (get/set conversion balance), and Workspace (PATCH cutoverDate). Added PATCH /partners/transactions/change-category-bulk and exclude-bulk. Removed non-existent POST /partners/bills/bulk and /partners/invoices/bulk from the reference. Extended the MCP tool catalog with the matching COUNT_* tools plus remote-only COUNT_get_bulk_task_status and COUNT_remember/recall/forget.

2026-07-09

Prompt Library and corrected MCP tool reference

Added a Prompt Library (/tools/prompt-library) of curated, copy-pasteable prompts for driving COUNT workflows through an MCP-connected agent, covering invoicing, bills, transactions, journal entries, reporting, payroll, projects/contacts, and month-end close. Indexed into site search. Also corrected src/data/cliMcpReference.ts, which was missing the Budgets tool category, COUNT_split_transaction, COUNT_list_account_sub_types, a remote-only Payroll category, and 4 of 7 shared meta tools (COUNT_knowledge, COUNT_playbooks, COUNT_resolve_references, COUNT_validate_payload) — the MCP Server page now flags remote-only tools.

2026-07-09

OpenAPI spec, Postman collection, inline Try it, and versioning policy

Added an OpenAPI 3.0 spec and Postman collection generated at build time from the reference data (npm run generate:openapi / generate:postman, validated in check:parity). Endpoint pages now include an inline "Try it" panel that shares credentials with the standalone Try it tool. Added a Versioning & Deprecation Policy page, cross-linked from breaking changelog entries.

2026-06-30

transactions, chart-of-accounts

Transaction split, COA balance, and bill-picker filters

Added PUT /partners/transactions/{uuid}/split for explicit transaction splits. Chart of accounts list now returns systemBalance when includeBalances=true. Documented bill-assignment list filters (reviewed, pending, excluded, currency, status) and exposed read-only billId/invoiceId UUIDs on transaction responses.

2026-06-29

budgets, invoices, chart-of-accounts, customers, documents

Budgets API and documentation parity

Added the Budgets API reference (14 endpoints), invoice send-history, and account sub-types list. Introduced an automated parity check (`npm run check:parity`) that compares documented routes against count-dev. Normalized customer path parameters to `{uuid}` and fixed the documents chunk-upload progress path.

2026-06-21

chart-of-accounts, vendors, products-and-services, recurring-invoice-templates, credit-memo, bills, journal-entries, tags, people, projects, tasks, time-entries, expense-receipts, reports, workspace-stats, invoices, transactions

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.

2026-06-15

COUNT CLI and MCP Server documentation

Added COUNT CLI and MCP Server guides covering install, OAuth login, local vs remote MCP, tool categories, resources, and Claude Code / Cursor configuration.

2026-06-10

Redesigned Partner API documentation

Launched the redesigned Partner API documentation with a single consistent layout, persona journeys, guides, and code samples in six languages.

2026-06-05

webhooks, documents

Webhooks and Documents reference

Added full API reference groups for Webhooks and Documents, including chunked upload and signature verification guidance.

2026-06-01

Downloadable starter templates and signature generator

Added downloadable starter templates in six languages and an in-browser HMAC signature generator with deep links from endpoint pages.

2026-05-20

workspace-stats

Workspace stats endpoint

Added workspace stats endpoint for aggregated dashboard metrics.

2026-05-10

webhooks

Expanded webhook events

Expanded webhook events to cover bills and invoices.