API Reference

People

People are the employees, contractors and other contacts of a workspace. Create and edit them, switch them on and off, terminate them, manage their jobs and expense reporting, and resend their invites.

Last updated 2026-11-18

Overview

The People API covers the person records of a workspace: employees, contractors, volunteers and other contacts used for payroll, time tracking and expense reporting. Every person and every job is identified by the UUID returned as `id`.

Your integration can list, get, create, update and delete people; activate and deactivate them; terminate them; add and remove jobs; make them expense reporters; and resend their sign-in invite or payroll onboarding email.

Some things stay in the COUNT app: bank accounts, tax identification numbers (SSN), identity checks, and adding a person to or removing them from payroll.

Key concepts

Identification

Reference a person by the UUID returned as `id`, a job by its own `id`, accounts by `accountUuids` from List accounts, and a work location by `locationUuid`. Numeric ids such as `accountIDs`, `locationId` and `originalJobId` are refused.

Deleted people

A deleted person no longer appears in List people, and every route returns 404 for their UUID.

Payroll stays in COUNT

A partner write cannot add the `payroll` role or take it away, set bank accounts or a tax identification number, or delete a job that is synced to the payroll provider. A person already in payroll keeps the role on updates.

The person object

Core fields of a person record. `address`, `remoteWorkAddress`, `jobs`, `accounts` and `vendor` are embedded when present. Sign-in secrets, tax identification numbers (also on a contractor's vendor), bank account and routing numbers, and internal numeric ids are never returned.

Attributes

iduuid

Person identifier (UUID). Use in path parameters.

firstNamestring

Person's first name.

lastNamestring

Person's last name.

emailstring

Email address, or null.

phonestring

Phone number, or null.

typeenum

Kind of person.

One of: Employee, Contractor, Volunteer, Donor, Other

enabledboolean

Whether the person is active in the workspace.

terminatedboolean

Whether the person has been terminated.

rolearray

What the person can do in COUNT: `time tracking`, `sales rep`, `expense reporting`, `payroll`.

positionstring

The title of the person's primary job.

createdAtdatetime

ISO 8601 creation timestamp.

updatedAtdatetime

ISO 8601 last update timestamp.

Example
{
  "id": "f1a2b3c4-d5e6-4789-a012-3456789abcde",
  "firstName": "Jane",
  "lastName": "Smith",
  "email": "jane.smith@acme.com",
  "phone": "+19876543210",
  "type": "Employee",
  "enabled": true,
  "terminated": false,
  "role": [
    "time tracking"
  ],
  "position": "Barista",
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-01-28T14:22:30.000Z"
}

Scope and permissions

Reads need the `people:read` scope; writes need `people:write`. List people needs the `view_people` permission and Get a person `view_people` or `view_payroll`. Every write and every job route needs `manage_people`, except Terminate a person and Resend the payroll onboarding email, which need `manage_payroll`.

MCP equivalent

COUNT_list_people, COUNT_get_person, 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, COUNT_list_person_jobs, COUNT_get_person_job, COUNT_create_person_job, COUNT_update_person_job and COUNT_delete_person_job. MCP creates and updates people with the payroll tools COUNT_create_person and COUNT_update_person. On a client that can show a form, COUNT_terminate_person asks the user to confirm first.

Used by time entries and expense receipts

Time entry create payloads require `peopleUuid` from this API. Expense receipt flows reference people through their expense reporting accounts.

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

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-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 people/partners/people

Returns a paginated list of people in the workspace.

GET
Get a person/partners/people/{uuid}

Retrieves a single person by UUID, with their address, primary job, accounts and vendor.

POST
Create a person/partners/people

Creates a person, optionally with a primary job and expense reporting accounts.

PATCH
Update a person/partners/people/{uuid}

Updates a person's profile, roles, accounts or primary job.

DELETE
Delete a person/partners/people/{uuid}

Deletes a person.

PATCH
Activate or deactivate a person/partners/people/{uuid}/enabled

Sets whether a person is active.

PATCH
Terminate a person/partners/people/{uuid}/terminate

Ends a person's employment.

POST
Resend the sign-in invite/partners/people/{uuid}/resend-invite

Emails the person a new temporary password.

POST
Resend the payroll onboarding email/partners/people/{uuid}/resend-onboarding-email

Emails a payroll employee their onboarding invite again.

POST
Make a person an expense reporter/partners/people/{uuid}/expense-reporter

Gives the person the expense reporting role and the accounts they spend from.

DELETE
Remove a person as an expense reporter/partners/people/{uuid}/expense-reporter

Takes away the expense reporting role and unlinks the person's accounts.

GET
List a person's jobs/partners/people/{uuid}/jobs

Returns the person's jobs, primary first, each with its work location.

GET
Get a job/partners/people/{uuid}/jobs/{jobUuid}

Returns one of the person's jobs.

POST
Create a job/partners/people/{uuid}/jobs

Adds a job to a person in an existing position.

PATCH
Update a job/partners/people/{uuid}/jobs/{jobUuid}

Updates one of the person's jobs.

DELETE
Delete a job/partners/people/{uuid}/jobs/{jobUuid}

Removes one of the person's jobs.