Practice Manager

Working in Client Workspaces

Read and write a client’s books through the Practice Manager API. Each request names the client in the count-workspace-id header; the routes and payloads are the Partner API’s.

Choosing the client

Client workspace routes live under /firm-partners/workspace. Add the count-workspace-id header with the id of a row from List client workspaces. The header is not part of the signature, so one signed path works for every client.

A client workspace request
GET https://api.getcount.com/firm-partners/workspace/invoices?page=1&limit=20
x-client-id: <firm key clientId>
x-timestamp: 1761041045
x-signature: <HMAC of "GET:/workspace/invoices:1761041045:">
count-workspace-id: 5e4d3c2b-1a09-4f8e-8d7c-6b5a49382716

The firm’s own practice workspace is listed too, as the last row, and works the same way — that is where the staff, customers and services used by firm time entries live.

Available routes

Differences from the Partner API

  • No bearer token. The firm key and the count-workspace-id header replace the per-workspace OAuth token.
  • No Idempotency-Key. Sending the header returns 400. A retried create can create a duplicate, so look the record up before retrying a write whose response you did not receive.
  • Acting member. Writes are made as a member of your firm who belongs to the client workspace, and that member’s role there decides role-restricted actions — for example, approving a bill without submitting it first.
  • Scope names. Chart of accounts, account sub-types and opening balances use the accounts scope, recurring invoice templates use invoices, document types use documents, and workspace stats use reports.

Portal-only clients

A client with isPracticeManagerOnly: true is managed in Practice Manager but has no books. Only these routes work for it; everything else returns 403 with type: "WORKSPACE_PORTAL_ONLY":

  • Every method on /tasks, /documents, /projects, /time-entries.
  • Listing only (GET on the collection) for /chart-of-accounts, /people, /customers, /vendors, /document-types.

Access errors

Before the route runs, COUNT checks the header, the client and the key, in this order:

StatusmessageMeaning
400Missing count-workspace-id header (client workspace uuid).Add the header.
404Workspace not found.No workspace has that id.
403This workspace is not managed by your firm.The workspace is not one of the firm’s clients.
403This API key cannot access this client workspace.The key is limited to other clients.
403No member of your firm belongs to this client workspace.Add a firm member to the client in COUNT.
403This workspace does not have an active subscription.The client’s subscription has lapsed (type: "WORKSPACE_SUBSCRIPTION_INACTIVE").
403This workspace is portal-only and does not include bookkeeping.See Portal-only clients above.

Check before you call

List client workspaces tells you which clients a key can reach and which are portal-only, so you can skip calls that would fail.