---
title: "People API · COUNT Partner API"
description: "People are workspace members — employees, contractors, and other payroll or expense-reporting contacts. Partner responses expose UUIDs as `id` and omit…"
canonical: "https://developers.getcount.com/reference/people"
source: "https://developers.getcount.com/reference/people"
---
API Reference

# People

People are workspace members — employees, contractors, and other payroll or expense-reporting contacts. Partner responses expose UUIDs as `id` and omit internal numeric foreign keys.

Last updated 2026-06-21

## Overview

The People API lets your integration list and retrieve people records in a workspace. People include employees, contractors, and other contacts used for payroll, time tracking, and expense reporting.

Partner routes are read-only: you can list people and retrieve a single person by UUID. Create, update, and delete are not available under `/partners/people`. Every person is identified by a UUID returned as `id` in responses.

## Key concepts

### Read-only partner access

Partner integrations can list and retrieve people but cannot create, update, or delete them through the Partner API. Manage people through the COUNT product or internal APIs.

### Identification

Reference a person by the UUID returned as `id`. Internal numeric ids and workspace foreign keys are stripped from partner JSON.

### Primary job fields

List and retrieve responses may include `paymentUnit` and `rate` derived from the person's primary job when one exists.

## The person object

Core fields returned on people records. Nested associations (jobs, address, department) may be embedded when present.

#### Attributes

`id` uuid

Person identifier (UUID). Use in path parameters.

`firstName` string

Person's first name.

`lastName` string

Person's last name.

`email` string

Email address.

`phone` string

Phone number.

`type` string

People type (for example employee, contractor).

`enabled` boolean

Whether the person is active in the workspace.

`role` array

Workspace roles assigned to the person (for example payroll).

`paymentUnit` string

Primary job payment unit when a primary job exists (for example hourly, salary).

`rate` number

Primary job rate when a primary job exists.

`createdAt` datetime

ISO 8601 creation timestamp.

`updatedAt` datetime

ISO 8601 last update timestamp.

Example

```json
{
  "id": "f1a2b3c4-d5e6-4789-a012-3456789abcde",
  "firstName": "Jane",
  "lastName": "Smith",
  "email": "jane.smith@acme.com",
  "phone": "+19876543210",
  "type": "employee",
  "enabled": true,
  "role": [
    "payroll"
  ],
  "paymentUnit": "hourly",
  "rate": 45,
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-01-28T14:22:30.000Z"
}
```

Used by time entries and expense receipts

Time entry create payloads require `peopleUuid` from this API. Expense receipt flows may also reference people indirectly through account assignments.

Filtering

Use `search` for partial matches on first name, last name, email, and phone. Filter by `type`, `enabled`, `roles`, and other query params documented on List people.

## Related

- [Time Entries API](https://developers.getcount.com/reference/time-entries)
- [Tasks API](https://developers.getcount.com/reference/tasks)

## 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 people `/partners/people` Returns a paginated list of people in the workspace.](https://developers.getcount.com/reference/people/list-people) [GET Get a person `/partners/people/{uuid}` Retrieves a single person by UUID.](https://developers.getcount.com/reference/people/get-person)