API Reference

Time Entries

Time entries record minutes logged by a person against projects, customers, and billable services. Partner responses use UUIDs; entries in processed pay periods are read-only.

Last updated 2026-11-18

Overview

The Time Entries API provides full CRUD for logged time in a workspace. Create one or more rows in a single POST by passing `peopleUuid` and a `timeEntries` array. Updates use PATCH (not PUT).

Soft-deleted entries are excluded from list and return 404 on retrieve. Entries tied to a processed pay period cannot be updated or deleted until the pay period is adjusted.

Key concepts

Batch create

POST accepts `peopleUuid` plus `timeEntries: [{ date, minutes, ... }]`. The server validates the daily minutes cap across all rows for the same person and date.

UUID filter params

List filters use `peopleUuids`, `projectUuids`, `customerUuids`, and `productServiceUuids` (comma-separated). Direct numeric filters are stripped server-side.

Date window

Both `startDate` and `endDate` (YYYY-MM-DD) must be provided together for the createdAt range filter to apply. Passing only one is ignored.

Processed pay periods

PATCH and DELETE return 400 when the entry belongs to a processed pay period.

The time entry object

Fields returned on a time entry. Nested people, project, customer, and productService expose UUIDs.

Attributes

iduuid

Time entry identifier (UUID).

datedate

Calendar date of the entry (YYYY-MM-DD).

minutesinteger

Minutes logged. Daily total per person cannot exceed 1440 (24 hours).

descriptionstring

Optional notes for the entry.

billableboolean

Whether the time is billable.

wagenumber

Wage rate applied when set.

peopleobject

Person who logged the time.

projectobject

Linked project, or null.

customerobject

Linked customer, or null. May auto-fill from project.

productServiceobject

Billable product or service, or null.

createdAtdatetime

ISO 8601 creation timestamp.

updatedAtdatetime

ISO 8601 last update timestamp.

Example
{
  "id": "33445566-7788-99aa-bbcc-ddeeff001122",
  "date": "2026-03-15",
  "minutes": 120,
  "description": "Wireframe review session",
  "billable": true,
  "wage": 45,
  "people": {
    "uuid": "f1a2b3c4-d5e6-4789-a012-3456789abcde",
    "firstName": "Jane",
    "lastName": "Smith"
  },
  "project": {
    "uuid": "11223344-5566-7788-99aa-bbccddeeff00",
    "name": "Website Redesign"
  },
  "customer": {
    "uuid": "dfa3219e-6af8-4c53-997a-037534f63a35",
    "customer": "Acme Corporation"
  },
  "productService": {
    "uuid": "aa11bb22-cc33-dd44-ee55-ff6677889900",
    "description": "Consulting services"
  },
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-01-28T14:22:30.000Z"
}

peopleUuid required on create

Create requires a non-empty `peopleUuid` from the People API. On update, `peopleUuid` cannot be cleared — passing null or empty string returns 400.

Subscription required

Time entry routes require an active workspace subscription (`checkSubscription` middleware).

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

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