What makes ServiceTitan easy or hard to automate
ServiceTitan’s V2 API is broad: customers, locations, jobs, appointments, technicians, dispatch, estimates, invoices, payments, memberships, marketing and more, split into modules with their own scopes. Authentication is OAuth 2.0 client credentials plus an application key, and a tenant admin connects each app in ServiceTitan’s API Application Access settings. Technically, it is a good API to build on.
The rules around it are what make it hard. ServiceTitan recognizes two approved integration paths. Certified Apps are built and hosted by third-party companies that ServiceTitan has reviewed, and they connect without you sharing keys. Customer-Built Apps are created, hosted and maintained by the customer, and are available only on qualifying packages, so confirm yours with ServiceTitan. ServiceTitan explicitly prohibits tunneling, where a third party asks you to create an app and hand over its key, and it may ask you to disconnect integrations that break this rule.
For a contractor, that means the first step is not design. It is confirming your package, deciding whether a Certified App already does the job, and, if not, setting up a Customer-Built App that runs in your own cloud account.
The AI layer
ServiceTitan runs dispatch, pricing and billing. AI helps with the conversations and paperwork around jobs:
- Phones, where a voice or chat agent books routine jobs and triages after-hours calls using your rules.
- Notes, where call transcripts become a summary a technician reads before arriving.
- Follow-up, where unsold estimates and completed jobs get timely, specific messages.
- Dispatch support, where a model explains why the board is at risk and suggests options, and a dispatcher decides.
Limits to plan around
- Package gating. Customer-Built Apps need a qualifying package. Confirm before you scope.
- Zapier is a beta. As of 2026, ServiceTitan’s Zapier integration is in open beta, needs a registration form from an admin and a client ID and secret, and is offered as is without official support. Fine for simple pushes such as booking a job from an email lead, not for core workflows.
- Key ownership. App keys stay with the customer’s own software. No shared keys with outside platforms.
- Module scopes. Each API module needs its own scope. Request only what each workflow uses.
- Rate limits and paging. Large tenants have many jobs and calls. Page through results and use modified-since filters rather than full reads.
How Lumeor typically connects it
For qualifying customers, we build a Customer-Built App that runs in the contractor’s own cloud account, holding the ServiceTitan credentials there, with an LLM step for summaries or drafts and a voice layer on Twilio when phones are involved. Our AI calling platform case study shows the voice side, and the home services booking agent guide walks through the booking flow. Smaller shops often find Jobber easier to integrate.