All integrations

Clientary

BUSINESS · COMMERCE & FINANCE

Clients, estimates, invoices and tracked hours from their own practice.

Connecting Clientary in practice

Every user in a Clientary account has their own token, and Clientary uses it for attribution — time tracked through the API is recorded against the staff user whose token made the call — so one shared service token misattributes every entry. The base URL is the customer’s own subdomain, and a request without Accept: application/json or a .json suffix does not get JSON.

Worth knowing

  • The token is used as both username and password in HTTP Basic auth; the alternative is an OAuth 2.0 access token via the authorization code flow with PKCE, discoverable under /.well-known/.
  • Because the token identifies the acting staff member, the choice of credential changes what the application’s own reports say about who did the work.
  • Either the Accept header must be application/json or the resource URL must end in .json; JSONP is not supported, so a browser-side integration needs a proxy.
  • The base URL is https://{yourdomain}.clientary.com/api/v2/…, so the account subdomain is effectively part of the credential and cannot be discovered from the token.

Checked against Clientary API introduction (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

clientary_delete_api_v2_clients_client_id_payment_profiles_idWRITE

Delete a payment profile via DELETE /api/v2/clients/{client_id}/payment_profiles/{id}

api
clientary_delete_api_v2_clients_idWRITE

Delete a client via DELETE /api/v2/clients/{id}

api
clientary_delete_api_v2_contacts_idWRITE

Delete a contact via DELETE /api/v2/contacts/{id}

api
clientary_delete_api_v2_estimates_idWRITE

Delete an estimate via DELETE /api/v2/estimates/{id}

api
clientary_delete_api_v2_expenses_idWRITE

Delete an expense via DELETE /api/v2/expenses/{id}

api
clientary_delete_api_v2_hours_idWRITE

Delete an entry via DELETE /api/v2/hours/{id}

api
clientary_delete_api_v2_invoices_idWRITE

Delete an invoice via DELETE /api/v2/invoices/{id}

api
clientary_delete_api_v2_invoices_invoice_id_payments_idWRITE

Delete a payment via DELETE /api/v2/invoices/{invoice_id}/payments/{id}

api
clientary_delete_api_v2_leads_idWRITE

Delete a lead via DELETE /api/v2/leads/{id}

api
clientary_delete_api_v2_projects_idWRITE

Delete a project via DELETE /api/v2/projects/{id}

api
clientary_delete_api_v2_recurring_idWRITE

Delete a recurring schedule via DELETE /api/v2/recurring/{id}

api
clientary_delete_api_v2_tasks_idWRITE

Delete a task via DELETE /api/v2/tasks/{id}

api
clientary_get_api_v2_clientsREAD

Get all clients via GET /api/v2/clients

api
clientary_get_api_v2_clients_client_id_contactsREAD

Get contacts for client via GET /api/v2/clients/{client_id}/contacts

api
clientary_get_api_v2_clients_client_id_estimatesREAD

Get estimates for client via GET /api/v2/clients/{client_id}/estimates

api
clientary_get_api_v2_clients_client_id_expensesREAD

Get expenses for client via GET /api/v2/clients/{client_id}/expenses

api
clientary_get_api_v2_clients_client_id_invoicesREAD

Get invoices for client via GET /api/v2/clients/{client_id}/invoices

api
clientary_get_api_v2_clients_client_id_payment_profilesREAD

Get payment profiles for client via GET /api/v2/clients/{client_id}/payment_profiles

api
clientary_get_api_v2_clients_client_id_projectsREAD

Get projects for client via GET /api/v2/clients/{client_id}/projects

api
clientary_get_api_v2_clients_idREAD

Get a client via GET /api/v2/clients/{id}

api
clientary_get_api_v2_contactsREAD

Get all contacts via GET /api/v2/contacts

api
clientary_get_api_v2_contacts_idREAD

Get a contact via GET /api/v2/contacts/{id}

api
clientary_get_api_v2_estimatesREAD

Get all estimates via GET /api/v2/estimates

api
clientary_get_api_v2_estimates_idREAD

Get an estimate via GET /api/v2/estimates/{id}

api
clientary_get_api_v2_expensesREAD

Get expenses by date via GET /api/v2/expenses

api
clientary_get_api_v2_expenses_idREAD

Get an expense via GET /api/v2/expenses/{id}

api
clientary_get_api_v2_hours_idREAD

Get a specific entry via GET /api/v2/hours/{id}

api
clientary_get_api_v2_invoicesREAD

Get all invoices via GET /api/v2/invoices

api
clientary_get_api_v2_invoices_idREAD

Get an invoice via GET /api/v2/invoices/{id}

api
clientary_get_api_v2_leadsREAD

Get all leads via GET /api/v2/leads

api
clientary_get_api_v2_leads_idREAD

Get a lead via GET /api/v2/leads/{id}

api
clientary_get_api_v2_paymentsREAD

Get all payments via GET /api/v2/payments

api
clientary_get_api_v2_projectsREAD

Get all projects via GET /api/v2/projects

api
clientary_get_api_v2_projects_idREAD

Get a project via GET /api/v2/projects/{id}

api
clientary_get_api_v2_projects_project_id_estimatesREAD

Get estimates for project via GET /api/v2/projects/{project_id}/estimates

api
clientary_get_api_v2_projects_project_id_expensesREAD

Get expenses for project via GET /api/v2/projects/{project_id}/expenses

api
clientary_get_api_v2_projects_project_id_hoursREAD

Get hours for project via GET /api/v2/projects/{project_id}/hours

api
clientary_get_api_v2_projects_project_id_invoicesREAD

Get invoices for project via GET /api/v2/projects/{project_id}/invoices

api
clientary_get_api_v2_recurringREAD

Get all recurring schedules via GET /api/v2/recurring

api
clientary_get_api_v2_recurring_idREAD

Get a recurring schedule via GET /api/v2/recurring/{id}

api
clientary_get_api_v2_recurring_id_invoicesREAD

Get invoices for recurring schedule via GET /api/v2/recurring/{id}/invoices

api
clientary_get_api_v2_tasksREAD

Get tasks via GET /api/v2/tasks

api
clientary_get_api_v2_tasks_idREAD

Get a task via GET /api/v2/tasks/{id}

api
clientary_get_projects_project_id_tasksREAD

Get tasks for project via GET /projects/{project_id}/tasks

api
clientary_get_staffREAD

Get all staff via GET /staff

api
clientary_get_staff_idREAD

Get a staff user via GET /staff/{id}

api
clientary_post_api_v2_clientsWRITE

Create a new client via POST /api/v2/clients

api
clientary_post_api_v2_clients_client_id_contactsWRITE

Create a new contact via POST /api/v2/clients/{client_id}/contacts

api
clientary_post_api_v2_clients_client_id_invoicesWRITE

Create a new invoice for client via POST /api/v2/clients/{client_id}/invoices

api
clientary_post_api_v2_clients_client_id_payment_profilesWRITE

Create a payment profile via POST /api/v2/clients/{client_id}/payment_profiles

api
clientary_post_api_v2_estimatesWRITE

Create a new estimate via POST /api/v2/estimates

api
clientary_post_api_v2_estimates_id_messagesWRITE

Send an estimate via POST /api/v2/estimates/{id}/messages

api
clientary_post_api_v2_expensesWRITE

Create a new expense via POST /api/v2/expenses

api
clientary_post_api_v2_invoicesWRITE

Create a new invoice via POST /api/v2/invoices

api
clientary_post_api_v2_invoices_id_messagesWRITE

Send an invoice via POST /api/v2/invoices/{id}/messages

api
clientary_post_api_v2_invoices_invoice_id_paymentsWRITE

Post a new invoice payment via POST /api/v2/invoices/{invoice_id}/payments

api
clientary_post_api_v2_leadWRITE

Create a new lead via POST /api/v2/Lead

api
clientary_post_api_v2_projectsWRITE

Create a new project via POST /api/v2/projects

api
clientary_post_api_v2_projects_project_id_hoursWRITE

Create a new entry via POST /api/v2/projects/{project_id}/hours

api
clientary_post_api_v2_recurringWRITE

Create a new recurring schedule via POST /api/v2/recurring

api
clientary_post_api_v2_taskWRITE

Create a new task via POST /api/v2/task

api
clientary_put_api_v2_clients_idWRITE

Update a client via PUT /api/v2/clients/{id}

api
clientary_put_api_v2_contacts_idWRITE

Update a contact via PUT /api/v2/contacts/{id}

api
clientary_put_api_v2_estimates_idWRITE

Update an estimate via PUT /api/v2/estimates/{id}

api
clientary_put_api_v2_expenses_idWRITE

Update an expense via PUT /api/v2/expenses/{id}

api
clientary_put_api_v2_hours_idWRITE

Update an entry via PUT /api/v2/hours/{id}

api
clientary_put_api_v2_invoice_idWRITE

Update an invoice via PUT /api/v2/invoice/{id}

api
clientary_put_api_v2_leads_idWRITE

Update a lead via PUT /api/v2/leads/{id}

api
clientary_put_api_v2_projects_idWRITE

Update a project via PUT /api/v2/projects/{id}

api
clientary_put_api_v2_recurring_idWRITE

Update a recurring schedule via PUT /api/v2/recurring/{id}

api
clientary_put_api_v2_tasks_idWRITE

Update a task via PUT /api/v2/tasks/{id}

api

Put Clientary behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.