Practice Manager

Practice Manager API

Build on an accounting firm’s practice in COUNT: its clients, team, tasks, time and projects, plus each client’s books — with one firm API key instead of one connection per client.

Who it is for

The Practice Manager API is for software that works for an accounting firm across its whole client base: practice management tools, workflow and reporting products, and a firm’s own internal automation. Where the Partner API connects your app to one business’s books at a time, a Practice Manager key belongs to a firm and reaches every client that firm manages in COUNT.

Partner APIPractice Manager API
Acts forOne business (workspace)One accounting firm and its clients
Base path/partners/firm-partners
CredentialsPartner app clientId + secret, plus an OAuth token per workspaceFirm API key (clientId + secret) — no per-client authorization
Choosing a clientImplied by the access tokencount-workspace-id header on each request
Firm-level data—Firm profile, clients, members, firm tasks, time entries, projects
Request signingHMAC-SHA256Same HMAC-SHA256 scheme, signed relative to /firm-partners

What you can do

Firm routes under /firm-partners/firm act on the practice itself:

  • Firm, Clients & Members — Read the authorized firm’s profile, the client workspaces it manages, and its team, and create new client workspaces. Client workspace ids from this group are what every client workspace route takes.
  • Firm Tasks — The firm’s own work queue: tasks owned by the practice, for internal work or for a client, assigned to firm members and filterable across every client at once.
  • Firm Time Entries — Time the firm’s own staff log against its billing customers, projects, services and tasks — the practice’s timesheets, not a client’s payroll.
  • Firm Projects — Open projects across the firm’s own workspace and every client workspace, for linking firm tasks.

Client workspace routes under /firm-partners/workspace act on one client’s books. They are the Partner API’s workspace routes for Customers, Invoices, Credit Memos, Recurring Invoice Templates, Bills, Transactions, Chart of Accounts, Taxes, Vendors, Supplier Bank Accounts, Payment Batches, Products & Services, Journal Entries, Budgets, Fixed Assets, Tags, Webhooks, Documents, People, Projects, Tasks, Time Entries, Expense Receipts, Connections, Reconciliations, Opening Balance, Workspace, Reports, Workspace Stats, Workspace Events, Deleted Records — same request and response shapes, with the client chosen per request. See Working in Client Workspaces.

Your first three calls

Every request is HMAC-signed with your key’s secret — see Authentication & API Keys for the signing recipe. Once signing works, this sequence is the usual starting point:

Getting oriented
# 1. Who am I? The firm the key belongs to.
GET https://api.getcount.com/firm-partners/firm/details

# 2. Which clients can this key reach? Each row's id is a client workspace.
GET https://api.getcount.com/firm-partners/firm/clients

# 3. Read one client's books — name the client in the count-workspace-id header.
GET https://api.getcount.com/firm-partners/workspace/invoices
count-workspace-id: <id from step 2>

# Adding a client? Create it, then use the returned workspace.id the same way.
POST https://api.getcount.com/firm-partners/firm/clients
{ "name": "Maple Grove HOA", "country": "US", "externalReference": "hoa-27" }

Every endpoint page in the Practice Manager API reference has complete signed request samples in cURL, Node.js, Python, PHP, Go and C#.

Current limits

Key-based access only, for now

Requests authenticate with the firm API key alone and act as the firm’s owner. The API also has an OAuth flow that lets a specific firm member authorize your app, but its consent screen is not available yet, so it is not documented here.
  • The Idempotency-Key header is not supported on /firm-partners: requests that send it get 400. Make writes safe to retry yourself.