Finance & ERP · Integration
Clientary
Add Clientary to your product for your customers, and give your AI agents governed access to it.
Clientary is addressed per account rather than centrally: requests go to https://{yourdomain}.clientary.com/api/v2 and authenticate with HTTP Basic where the API token is used as both the username and the password. Tokens are issued per user rather than per account, so every write is attributed to that staff member inside the application, which matters most for hours, where the token's user becomes the person who logged the time. Responses are only JSON if you suffix the path with .json or send an Accept: application/json header; without either, the request falls through to the web application and returns a 302 to the login page, which looks like an auth failure but is not one. The resource set covers clients, contacts, estimates, invoices, payments, expenses, hours, projects, tasks, leads and recurring schedules, so there are no supplier vendors here in the accounting sense, only clients you bill, which is worth knowing before mapping it to a general ledger. fastn stores each customer's subdomain and token together and keeps the per-user attribution intact.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Clientary account so invoices raised in your product appear under their billing
Push tracked time from your application into Clientary hours against the right project and task
Read payment records so your dashboard shows what has actually settled rather than what was invoiced
Create clients and contacts in Clientary automatically when a deal is won in your system
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to list overdue invoices for a customer's account with the days outstanding, with every read audited per tenant
Have an agent draft an invoice from unbilled hours on a project and leave it for a human to send
Let an agent reconcile expenses against projects and flag any without a client attached
Example prompt
Which Clientary invoices are more than thirty days overdue?
Set up Clientary in 4 steps
- 01Enable the Clientary connector from your fastn dashboard.
- 02Have each customer authorise their own Clientary account, so calls run under their credentials rather than a shared key.
- 03Decide which invoices, payments and vendors your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Clientary integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Clientary integration without building it. Your customers connect their own Clientary account inside your product and work their invoices, payments and vendors there, with no per-customer code on your side.
- Handle the part that actually costs time: financial writes must be idempotent and reconcilable, because a duplicate is an accounting problem rather than a bug. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Clientary update is not your on-call problem.
- One integration serves your product and your agents. The same governed Clientary connection powers in-product features and gives AI agents scoped, audited access, so you move financial records without hand-keying them between systems without wiring it twice.
Used by these teams
Compare with
NetSuite
QuickBooks
XeroOften used alongside
Tools the same teams tend to run next to Clientary, across other categories.
Shopify
Stripe
BigCommerce
AfterShipClientary integration FAQ
How do I add a Clientary integration to my product?
Enable the Clientary connector in your fastn dashboard, then let each customer authenticate their own Clientary account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Clientary client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Clientary account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Clientary account and only ever sees their own invoices, payments and vendors. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Clientary integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to list overdue invoices for a customer's account with the days outstanding, with every read audited per tenant
Who maintains the Clientary integration?
fastn does. When Clientary changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Clientary integration safe for financial writes?
Writes are idempotent, so a retry after a timeout does not post a document twice, and every call is logged per tenant so an entry can be traced back to the event that created it. That matters more in finance than anywhere else, because a duplicate is a number somebody has to explain.
Can it handle each customer's own chart of accounts?
Yes. ERP deployments are configured to the business, so account structures, required fields and fiscal calendars differ per customer. Those are mapped per tenant as configuration, not hard-coded.
What about Clientary rate limits during a first import?
Backfills are throttled deliberately. ERP limits are often account-wide rather than per-integration, so an unthrottled import can exhaust a customer's allowance and disrupt their other integrations.
What can I build with the Clientary integration?
A common starting point: let a customer connect their own Clientary account so invoices raised in your product appear under their billing. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Clientary integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Clientary does not change your per-connector cost. You can start free with 3 connected accounts.
Add Clientary to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.