ServiceTitan APIConnect ServiceTitan without building on its API
ServiceTitan has a REST API. Customers on the Works or Ent Plus package can build their own apps (request access via the dev portal); third-party developers must request access, get integration-environment-only access, and reach customers as certified Marketplace apps. If you're reading the docs because you need ServiceTitan to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across ServiceTitan and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0 client credentials
- AccessPlan-dependent
What the ServiceTitan API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 client credentials (per-tenant Client ID + Secret) plus an App Key; access tokens expire after 900 seconds
- Who can get access
- Customers on the Works or Ent Plus package can build their own apps (request access via the dev portal); third-party developers must request access, get integration-environment-only access, and reach customers as certified Marketplace apps.
- What it covers
- Field-service data such as customers/CRM, jobs, dispatch, pricebook, invoicing/accounting, and reporting.
- Limits
- 60 calls per second per application per tenant for regular APIs, and 1 of the same report per minute per tenant for reporting APIs.
- Worth knowing
- Sharing a customer's App Key with third-party software ('tunneling') is explicitly not allowed; third parties must go through the certified app path.
Official docs: developer.servicetitan.io. Checked September 2026. Vendors change access terms, so confirm with ServiceTitan before you build.
Building on the ServiceTitan API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get ServiceTitan credentials, and manage tokens and refreshes. | Connect your ServiceTitan account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the ServiceTitan task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting ServiceTitan work off someone's desk, the build is the slow part.
What teams usually want the ServiceTitan API for
Inbound job intake
Caddi turns inbound calls, forms, and emails into correctly-scheduled ServiceTitan jobs with the right customer and location.
Invoicing & books sync
Caddi reconciles completed ServiceTitan jobs against accounting and posts invoice-ready records.
ServiceTitan API questions
Does ServiceTitan have an API?
Yes. ServiceTitan has a REST API, authenticated with OAuth 2.0 client credentials (per-tenant Client ID + Secret) plus an App Key; access tokens expire after 900 seconds. The official documentation is at https://developer.servicetitan.io/.
How do I get access to the ServiceTitan API?
Customers on the Works or Ent Plus package can build their own apps (request access via the dev portal); third-party developers must request access, get integration-environment-only access, and reach customers as certified Marketplace apps.
Does the ServiceTitan API have rate limits?
60 calls per second per application per tenant for regular APIs, and 1 of the same report per minute per tenant for reporting APIs.
Can I connect ServiceTitan to my other tools without writing code against its API?
Yes. With Caddi you show the ServiceTitan task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across ServiceTitan and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate ServiceTitan with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for ServiceTitan is reviewed before it runs in production, and every run is logged.
Connect ServiceTitan without the build.
Drop your work email and pick a time. We'll show you Caddi running your ServiceTitan workflow end to end.