What we do
Tools
Industries
Department
How we workLet's talk →
Home/ServiceTitan/ServiceTitan API Documentation
ServiceTitan

ServiceTitan API Documentation, and Who Holds Which Key

The developer has the docs open. The owner has the ServiceTitan login. Neither one can finish the setup alone, and that's usually where a ServiceTitan integration sits for two weeks. Here's where the documentation is, and exactly which part each person does.

Where the documentation is

The API reference and guides are on ServiceTitan's developer portal, developer.servicetitan.io. Sign in with a ServiceTitan account, not an Enterprise Hub or Partner Portal login.

The setup steps for the shop's side are in ServiceTitan's help center, in the article on getting started with API Dev Portal V2.

Two environments. The integration environment is for building and testing, and for existing customers it's a clone of production, data included. Request it from the portal.

The handoff between the shop and its developer

Step Who does it Watch for
Turn on the two API permissions A ServiceTitan admin at the shop enables Generate API Application Key and Manage API Application Access for whoever will set this up. Without them, the developer portal won't offer the right options, and it looks like a login problem.
Create the app In the portal, My Apps, then +New App. Add the tenant ID and tick the API Scope the app needs. Ask for the scopes the integration actually uses. Each one is something the shop is agreeing to share.
Copy the app key Keys, then Application Key. This goes with every API call, in the ST-App-Key header. It identifies the app, not the shop. It's not the client secret.
Connect the app to the shop In ServiceTitan: Settings, search Integrations, API Application Access, Connect New App, then Allow Access. Only someone with Manage API Application Access can do this. It's the step owners don't expect to be theirs.
Generate the client ID and secret On the same connected app, copy the Client ID and click Generate next to Client Secret, then pass both to the developer securely. Credentials made in the integration environment don't work in production, and the other way round.
First call The developer requests an access token with the client ID and secret (OAuth 2.0 client credentials), then calls the API with the token and the app key. Most endpoints carry the tenant ID in the path, so a missing or wrong tenant fails even with a good token.

Why a ServiceTitan integration stalls after the credentials arrive

Keys from one environment, host from the other

How you'll know: 401 or Access Denied, though every value was copied correctly.

Fix: Integration credentials go to the integration hosts (the ones with -integration in the name), production credentials to production. Keep them in separate config so a deploy can't mix them.

The app key in the wrong place

How you'll know: The token request works, and then every API call is refused.

Fix: The token proves who's calling. The app key still has to travel in the ST-App-Key header on each request.

The app never appears under Connect New App

How you'll know: The admin goes to connect it and the list doesn't show it.

Fix: Check that the tenant ID on the app matches the shop, and that you're signed in to the same environment the app was created in. A shop with several tenants needs an app, client ID and secret for each.

Planning around a webhook that might not exist

How you'll know: The design assumes an event for every change, and the one you need isn't offered.

Fix: Webhook events are chosen per app in the developer portal, and the list differs by module. Confirm the event before building on it. Where there isn't one, poll for recently changed records on a schedule.

Past the reference: the parts no endpoint covers

The ServiceTitan API covers the core of the business: customers and locations, jobs and appointments, invoices and payments, technicians and the Pricebook. The ServiceTitan Marketplace sits next to it, with ready-made apps for accounting, marketing and payments. If one of those does what you need, use it. It's a fixed feature set, though, so a shop with its own rules usually ends up with something custom against the API.

Some jobs aren't in the API at all. Before reaching for anything clever, look for a built-in import. The Pricebook, for one, has an Excel import for bulk changes. When a task really does exist only on a ServiceTitan screen, n-frames automates that screen with a browser script, kept as small as possible because screens change.

Most of what we build is the plain part: job and invoice data flowing to the accounting or reporting system on a schedule the shop can trust, with retries, logging and an alert when a run fails. The ServiceTitan dispatch page covers the scheduling side.

Questions people ask

Does ServiceTitan have a public API?

Yes. It's a documented REST API on developer.servicetitan.io, using OAuth 2.0 client credentials plus an app key. Access isn't anonymous: a shop's admin has to connect your app to their ServiceTitan account before any data comes back.

Do you need to be a certified ServiceTitan partner to use the API?

Not to build for one shop. A contractor, or a developer working for one, signs in to the portal as a ServiceTitan customer, creates the app and connects it from the shop's own settings. Software companies building one app for many contractors go through ServiceTitan's partner route, which has its own terms.

What is the ServiceTitan Marketplace?

ServiceTitan's directory of ready-made integrations, from ServiceTitan and third parties, for things like accounting sync, marketing attribution and payments. It's the first place to look. If no app there fits the shop's rules, the API is the way to build exactly what's needed.

Does ServiceTitan support webhooks?

Yes, for some events. You pick them per app in the developer portal, and what's offered depends on the module. For changes without an event, an integration checks for recently modified records on a schedule instead.

Does ServiceTitan process payments through the API?

ServiceTitan processes card payments itself through ServiceTitan Payments. The API's role is the records: reading invoices and payments so they can reach your accounting or reporting system without being typed in again.

Where can I find ServiceTitan API documentation?

On developer.servicetitan.io, after signing in with a ServiceTitan account. The steps for the shop's side, permissions and connecting an app, are in ServiceTitan's help center. n-frames handles both halves when a shop wants the integration built rather than learn the portal.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.