ServiceTitan integrations: what connects and how
ServiceTitan connects to other software three ways: its API, Zapier, and Marketplace apps. Here is what each one needs, what it can do, and where each one stops.
ServiceTitan connects to other software three ways: its own API, Zapier, and apps from the ServiceTitan Marketplace. The API can do the most and takes the most work. Zapier handles simple trigger-and-action jobs. Marketplace apps are the fastest start when someone has already built what you need.
We are ServiceTitan coaches, and we run a ServiceTitan data sync across 108 data types. This guide covers what each route needs and where each one runs out.
What are the ways to connect to ServiceTitan?
Pick the route by the size of the job.
- RouteMarketplace appBest forA common need someone already solvedWho builds itThe partnerMain limitYou get what the listing offers
- RouteZapierBest forOne trigger, one action, no codeWho builds itYou or a consultantMain limitPolling triggers, tenant by tenant credentials
- RouteAPIBest forCustom reads, writes and syncsWho builds itA developerMain limitNeeds code and care with rate limits
| Route | Best for | Who builds it | Main limit |
|---|---|---|---|
| Marketplace app | A common need someone already solved | The partner | You get what the listing offers |
| Zapier | One trigger, one action, no code | You or a consultant | Polling triggers, tenant by tenant credentials |
| API | Custom reads, writes and syncs | A developer | Needs code and care with rate limits |
The Marketplace is ServiceTitan's directory of partner products. It describes itself as the place to "connect with valuable products and services that enhance your ServiceTitan experience," and customers start from the partner's own listing (ServiceTitan Marketplace). Categories include Marketing, Catalogs and Pricebooks, Leads and Bookings, Payments and Financing, and Business Intelligence and Analytics, among others.
Does ServiceTitan have an API?
Yes. The V2 APIs use OAuth 2.0 with the machine-to-machine grant flow. Your code calls the OAuth API with a Client ID and Secret, gets an access token back, then calls each API endpoint with that token and an App Key (ServiceTitan help: Get started with API dev portal V2).
The developer portal is at developer.servicetitan.io. Reference pages there load in the browser only, so for setup steps the help center pages are the easiest to read.
How do I get ServiceTitan API access?
The setup has two steps, and your ServiceTitan admin has to be involved in both.
- Permissions. An admin must enable "Generate API Application Key" and "Manage API Application Access." You also must sign in with your ServiceTitan account. Enterprise Hub and Partner Portal logins do not work (ServiceTitan help).
- Create an app. In the developer portal, choose "+New App," add your tenant IDs, and select the endpoints you need under API Scope. When the app is created you copy the Application Key.
- Connect it in ServiceTitan. Go to Settings, then Integrations, then API Application Access, and click "Connect New App." Copy the Client ID and generate the Client Secret (same page).
For testing, you can request a separate integration environment from the developer portal. ServiceTitan marks this help page as stale, so confirm the current screens before you build.
One detail trips people up: scopes are fixed when you create the app. If you later need an endpoint you did not select, the app has to be updated. We found this out the practical way. A write scope on job attachments (tn.frm.jobs:w) has to be on the app before the endpoint will accept an upload. We tested that on 2026-10-09 against a live tenant, and the upload returned a 200 with the new file's ID.
What are the ServiceTitan API rate limits?
For regular APIs, "the standard rate limit is 60 calls per second per application per tenant." For reporting APIs, "the limit is 1 of the same report per minute per tenant" (ServiceTitan help: default API rate limits).
ServiceTitan's API terms also say you may not "exceed or attempt to circumvent any rate limits," and that the company can change the limits at any time (ServiceTitan API terms, section 3.4). Build for slower than the limit, not right at it.
Does ServiceTitan work with Zapier?
Yes, with conditions. The Zapier quick reference lists these prerequisites (Zapier help: ServiceTitan on Zapier):
- A ServiceTitan account on The Works or Legacy package, because API access is only included with those agreements.
- Administrator permissions for whoever sets it up.
- A completed ServiceTitan Zapier registration form.
- A Client ID, Client Secret and Tenant ID from Settings, Integrations, API Application Access.
The same page lists the triggers, and every one is a polling trigger, including New Booking, New Call, New Project, New Lead Notes and Updated Estimate. Actions include Create Customer, Create Lead, Hold Appointment, Reschedule Appointment, Cancel Appointment and Create Job Attachments.
Two limits matter. ServiceTitan does not officially support Zapier, and it only handles API-related (500) errors, so zap setup help comes from Zapier Support. And Zapier credentials cannot be managed through Enterprise Hub, so each tenant needs its own request (Zapier help).
We also maintain our own private Zapier app for ServiceTitan (version 3.21.0), which exposes 232 operations: 85 triggers, 76 searches and 71 creates.
What is the ServiceTitan Marketplace?
It is a directory of partner products, not a single integration. The directory lists 25 categories, from Marketing and Dispatch to Fleet and GPS and Permitting (ServiceTitan Marketplace). It does not state how many apps are listed, so be wary of any article that gives a number.
A Marketplace listing is the right first stop when your need is common: reviews, financing, accounting, fleet tracking. Check each listing for which ServiceTitan packages and permissions it needs, because those details sit with the partner.
What can the API read that you might not expect?
More than most owners assume, and also less. We sync 108 data types from ServiceTitan into our own tables on five projects, including a 24-tenant and a 16-tenant operator.
Two real-world findings from our own probes:
- Permissions are per data type. In a retry of 22 data types across 15 tenants on 2026-10-09, all 330 attempts returned 403, including after fresh tokens. A data type your app is not granted stays closed, and the app keeps working for everything else. So when you scope an integration, list every data type you need before you submit, not after.
- Some operations are off per tenant. Deleting a job attachment through the public API returned a 403, "not enabled for this tenant," on the tenant we tested. Do not design a workflow that assumes delete works.
Both are measured results from our probes, not ServiceTitan documentation. Check your own tenant before committing to either.
Which route should I choose?
- You want one simple thing, like tagging a customer when a job completes. Start with Zapier. It is quick, and the action list covers common cases.
- You want a product someone already built. Search the Marketplace first.
- You want data in your own database, joins across data types, or something custom. Use the API, or hire someone who has done it. Plan for rate limits, scopes and per-tenant permissions from day one.
- You are unsure. Write down the trigger, the data, and who must approve it. If that fits in one sentence, use Zapier. If it takes a page, use the API.
Anything that writes into ServiceTitan should be something the shop turns on on purpose. Start with reads, check the results, then switch writes on one at a time.
Where can The Graphite Lab help?
We coach ServiceTitan shops. If you are weighing a connection, tools like Booking Buddy and Data Cleanse are in our catalog, and our team can tell you which route fits your setup. Browse the full list at graphitelab.ai/platform/products.