ServiceTitan API and integrations: what connects, what it costs, and how to get access

Most owners ask about the ServiceTitan API for one reason. They want data that lives in ServiceTitan to show up somewhere else: the accounting system, a dashboard, a customer or subcontractor portal, or a supplier tool. This page covers the three ways to do that, who sets each one up, what it costs, and the one clause in ServiceTitan's own terms that most write-ups on this topic skip.

Everything here comes from ServiceTitan's own help center, developer documentation and published API Terms, re-checked on 28 October 2026.

What are the ways to connect ServiceTitan to other systems?

• Built-in links: ServiceTitan builds and supports a handful of accounting integrations itself.
• Partner connectors: Other companies build links and list them on the ServiceTitan Marketplace.
• The API: A developer reads and writes ServiceTitan data directly, with keys your admin approves.

Start at the top of that list. A built-in link is the least work and the least to maintain. Move down only if the link you need does not exist, or does not move the specific data you want.

What does ServiceTitan connect to directly?

ServiceTitan's help center documents these accounting integrations as built in:

Integration	What it does
QuickBooks Desktop	Connects QBD Pro, Premier or Enterprise to sync invoices and payments
QuickBooks Online	Cloud-based, with real-time financial syncing
Sage Intacct	Aimed at enterprise accounting, with its own multi-month setup (below)
Xero	Automates the flow of invoices, payments and customer records
NetSuite	A certified SuiteApp built by ServiceTitan itself, syncing inventory activity's financial impact into NetSuite
General CSV	A file export for systems without a direct link. Not a live sync

Two things worth knowing before you assume a bigger system is "supported." ServiceTitan built the NetSuite link itself as a certified SuiteApp, so it behaves like the QuickBooks or Xero links above. Sage 300 CRE and Viewpoint Vista or Spectrum, which come up constantly in construction accounting conversations, are not ServiceTitan's own integrations. Both reach ServiceTitan through the same third-party connector, built by a company called Agave, so if your accounting system is one of those, you are already in partner-connector territory, not the built-in list.

ServiceTitan's own marketing pages also use round numbers like "100+ integrations" and "450+ API endpoints." Those are marketing figures, not a documented count you can hold them to, so confirm the exact link you need with your account manager rather than assuming it exists because the website implies a large number.

How does the ServiceTitan Sage Intacct integration work?

This is the most involved of the built-in links, and the help center is specific about it. It syncs customers, vendors and items as records, and sales invoices, payments, inventory transactions and credit memos as transactions, bidirectionally between the two systems. Setup has six parts: connecting the accounts, pulling Intacct objects into ServiceTitan, mapping business units to Intacct reporting dimensions, mapping price book items to item GL groups, mapping payment types to GL accounts, and configuring inventory tracking.

You start by contacting your Customer Success Manager, not by signing up anywhere yourself. ServiceTitan's own guidance is that implementations typically take 3 to 4 months, though the actual time depends on how clean your price book and GL mapping already are. If your finance team is waiting on this, plan the quarter around it, not the month.

Is there a ServiceTitan integration with Acumatica?

Yes, through the same partner, Agave, that handles Sage 300 CRE and Viewpoint. Agave's ServiceTitan-to-Acumatica connector is broader than most owners expect: alongside vendors, bills and invoices, it also syncs customers, projects and service orders, customer locations, materials and items, warehouses, purchase orders, purchase receipts, payments, technicians and timecard entries. You set it up by creating an Agave account, logging into both systems from inside Agave, choosing which data objects to share, and setting a sync frequency (manual or hourly). Neither Agave's listing nor the separate BizTech Services connector on the Acumatica Marketplace publishes a price, so get a quote from each and ask what happens when a record fails to sync.

What is the ServiceTitan Marketplace, and how do integration partners join?

The Marketplace is ServiceTitan's list of approved integration and service partners, organized into more than 20 categories, including Accounting and Tax, Suppliers, Procurement, Payments and Financing, HR and Payroll, Fleet and GPS, Business Intelligence and Analytics, and Inventory. A company that wants to list goes through ServiceTitan's own partner application and review. If you want a tool listed and it is not there yet, ask the vendor directly whether it is a ServiceTitan partner, since plenty of integrations exist that are not built or sold by ServiceTitan. NiceJob integrations shows what one review tool actually syncs with ServiceTitan.

For a servicetitan inventory integration specifically, start in the Suppliers, Procurement and Inventory categories, then ask the partner exactly what moves: purchase orders, receipts, stock counts, or all three. Partner listings vary a lot in depth, and the marketing copy on each one tends to oversell what actually syncs versus what you have to trigger manually.

How do I get access to the ServiceTitan API?

ServiceTitan's help center lays out the steps for version 2 of the API:

1. Turn on permissions. An administrator on your account enables "Generate API Application Key" and "Manage API Application Access." You need to sign in with a standard ServiceTitan account; Enterprise Hub and Partner Portal logins do not work for this.
2. Sign in to the developer portal. Go to developer.servicetitan.io and choose "Login to My Apps," then either the Integration Environment or Production Environment option depending on where the app will run.
3. Create an app. In My Apps, click "+New App," add your tenant IDs, and select the API scope, which is the set of endpoints (Jobs, Projects, Invoices, Payroll, Pricebook and so on) the app is allowed to touch. Copy the application key from the Keys section.
4. Connect the app in ServiceTitan. In Settings, go to Integrations, open API Application Access, click Connect New App, select the app, click Connect, then Allow Access.
5. Generate the client ID and secret. These live in the app's Application Details section and go to your developer.

Authentication is OAuth 2.0, machine to machine. In plain terms: your app sends the client ID and secret to ServiceTitan's OAuth endpoint and gets back a short-lived access token, then sends that token plus the application key with every API call. Keep the client secret private; anyone who has it can read your account's data.

Does the ServiceTitan API have limits?

Yes, two defaults apply to every app on every tenant:

• Regular APIs: 60 calls per second, per application, per tenant.
• Reporting APIs: one run of the same report per minute, per tenant.

The reporting limit is the one that catches people building a dashboard. If your dashboard calls the same report every time someone opens a page, it will get throttled the moment two people open it close together. The fix is the same one experienced developers use everywhere: pull the report on a schedule, store a copy, and have the dashboard read the stored copy instead of re-running the report live.

Is there a fee for API access, and who can build a private app without ServiceTitan's approval?

ServiceTitan does not charge a separate fee or usage charge for API access itself; your plan, any partner connector you buy, and your developer's time are the real costs. For comparison, Service Fusion gates its API behind its top plan, as described in Service Fusion API. What most pages on this topic get wrong, or skip, is the approval question.

ServiceTitan's published API Terms draw a clear line that is more permissive than it sounds: a "Custom Application" is one you make available to a single ServiceTitan customer only, and that does not require ServiceTitan's written approval. Only an "Authorized Application," meaning one you want to distribute to multiple ServiceTitan customers or list in the Marketplace, needs ServiceTitan's written sign-off, plus its certification process. In practice, if a build is just for your own account and will never be sold to another ServiceTitan user, you can register the app and build it through the normal developer portal flow, no special pre-approval needed.

That is genuinely different from how some comparable platforms handle this. Jobber, for example, restricts private custom integrations to "specific, approved" customers and developers, and caps a Draft app at 5 paying accounts. ServiceTitan's terms do not impose that gate on a single-tenant build. If someone tells you a private ServiceTitan integration needs a lengthy approval process before it can even start, that is not what ServiceTitan's own terms say, though it is still worth confirming your specific account has API access enabled, since that is an admin setting, not a given. Whether to move up from Jobber at all is covered in Jobber vs ServiceTitan.

What can I build with the ServiceTitan API?

The projects that come up most often for service businesses on ServiceTitan:

• Profit dashboards. Job revenue, labor and material cost, by technician, branch or customer, joined with payroll or QuickBooks data that the built-in reports don't connect to each other.
• Accounting links the built-in options don't cover. A system outside the five above, or coding rules your accounting link doesn't support.
• Customer or property manager portals. A page where a commercial client sees open jobs, quotes and invoices without calling your office.
• Alerts. A text or Slack message when a job runs over budget or a quote sits unsigned for too long.
• Scheduled data copies. A nightly export into your own database, so reports run against the copy and stay well inside the reporting API's rate limit.

Should I use a built-in link, a partner, or a custom build?

Use a built-in link first if it moves what you need; it is the cheapest to run and ServiceTitan maintains it. Use a partner connector when one exists for your accounting or supplier system at a fair price, understanding that "partner" can mean the same company (often Agave) behind several different named integrations. Use the API when what you want is a specific report, portal or rule that nothing else sells. A custom build costs more up front than a connector subscription, but gives you exactly the data and logic you asked for, and you are not limited to what a partner app chose to expose. See my ServiceTitan reports guide for where the built-in reports stop short.

How I'd approach this

When an owner asks me about the ServiceTitan API, I start by asking what the actual blocker is: a number they can't see anywhere, a system that doesn't talk to ServiceTitan, or a customer who wants self-service visibility. More often than not, a built-in link or an existing Marketplace partner already solves it, and I'll say so rather than quote a build.

When it does need custom work, the first real step is confirming with your ServiceTitan admin that API Application Access is switched on, and registering the app as a single-tenant Custom Application rather than assuming you need ServiceTitan's sign-off first, since you usually don't for a one-account build. From there I design around the rate limits from day one, mainly by scheduling pulls instead of hitting live reports, and I build it in accounts you control, so the result is yours either way.