API development
ServiceTitan API Development Services
Most ServiceTitan API work isn't one big app. It's a small, careful server that gets permission from your account, reads the right records, and hands them to something your team actually uses.
Diagram: the contractor's ServiceTitan tenant grants an app access. A server-side integration layer requests an access token, calls the permitted APIs, stores what it needs in its own database, and feeds the custom application.
What API development means on ServiceTitan
ServiceTitan publishes a set of V2 APIs that let approved software read, and in some cases create or change, the records your company keeps in it: customers, jobs, appointments, estimates, invoices, technicians, campaigns and more. API development is the work of building software that uses those APIs well. Not a plugin inside ServiceTitan, and not a screen scraper, but a separate program your admin explicitly lets in.
In practice nearly every project has the same shape. A server-side integration layer sits between your ServiceTitan account and the thing you need. It holds the credentials, requests short-lived access tokens, calls only the APIs it was granted, pages through results, backs off when ServiceTitan throttles requests, and logs what it did. On the other side it feeds the application: an internal tool, a dashboard, a website flow, a report.
That layer is also where the hard decisions live. Which records to keep, for how long, and what happens when a job is deleted or a customer is marked inactive are design questions, not afterthoughts. ServiceTitan's API Terms limit how long API data can be stored unless ServiceTitan's documentation permits it, so storage and refresh are agreed before anything is built. The detail is on the customer and job data sync page.
The API families most projects use
ServiceTitan groups its V2 APIs by area. These are the ones contractor projects reach for most often; the full list is in <a href="https://developer.servicetitan.io/docs/overview/" rel="noopener" target="_blank">ServiceTitan's developer documentation</a>.
CRM
Customers, locations, contacts, leads and bookings. The starting point for website lead flows and anything that needs to know who the customer is.
Job Planning & Management
Jobs, appointments, projects, job types, notes and history. The backbone of operations tools and most reporting.
Sales & Estimates
Estimates and their status: open, sold, dismissed. Used for sales review screens and estimate and invoice integrations.
Accounting
Invoices, payments and related records, for revenue reporting and reconciliation with your books.
Dispatch & Settings
Appointment assignments, technician shifts, business units, technicians and employees. Needed whenever results are grouped by tech, crew or division.
Marketing & Reporting
Campaigns, costs and attribution data, plus a Reporting API that runs reports your team already maintains in ServiceTitan.
Configuration, marketplace app or custom build
Custom development is the right answer less often than people expect. This is the order we check in.
| Need | In ServiceTitan | Custom-built |
|---|---|---|
| The need is common to most contractors | Often solved by configuration, a ServiceTitan add-on, or an app from its marketplace. Usually cheaper and supported by someone else. | Only worth building if the existing options don't fit how your company works. |
| The need is specific to your company | Workarounds: exports, spreadsheets, a report someone rebuilds every Monday. | A tool shaped around your process, your definitions and your people, reading the data directly. |
| Data from other systems | Limited to the integrations ServiceTitan and its marketplace provide for your account. | Joined in the integration layer, such as ad spend, accounting or a custom database, within the API Terms. |
| Who controls changes | The vendor's roadmap. | You. The code and documentation are yours, and changes are made when you need them. |
How an API project is built
- 1
Check with ServiceTitan first
ServiceTitan asks customers to check with its integrations team before engaging an outside developer, and so do we. It's the fastest way to learn what your account allows.
- 2
Register the app with the fewest permissions
The app is registered in ServiceTitan's Developer Portal with read or write scopes for only the resources it needs, and your admin approves it. How ServiceTitan API authentication works.
- 3
Build in the integration environment
ServiceTitan provides a separate integration environment, its sandbox, so development and testing happen away from live jobs.
- 4
Test with the people who'll use it
Real scenarios from the office: a canceled job, a customer with three properties, an estimate sold on the second visit.
- 5
Go live and watch it
Production credentials are configured on the server, the first runs are checked against what ServiceTitan shows, and logging and alerts stay on.
Security and maintenance aren't extras
Credentials live on the server and never reach a browser. Scopes stay as narrow as the job allows, and every write to ServiceTitan is deliberate and logged. We never ask for a staff login, admin rights, or the permission to create API applications in your account.
APIs also change. Adding a permission creates a new version of the app that your admin approves again, report owners can rename columns the integration reads, and ServiceTitan updates its APIs over time. A project includes documentation of what was built and what it can access, and support is discussed up front rather than after something breaks.
This is the same kind of work behind HomeService WebApp, an estimate-recovery application for contractors built on PHP, MySQL, Stripe and the ServiceTitan API. For the broader integration practice, see API integration services. For budgets, see what drives the cost of a ServiceTitan API integration.
In this category
- Custom ServiceTitan API Applications Internal tools and standalone web apps built for one job, on top of your ServiceTitan data.
- ServiceTitan API Authentication & Integration Setup App registration, admin approval, OAuth tokens, app keys, scopes and environments, explained accurately.
- ServiceTitan Customer & Job Data Integration Customers, locations, jobs and appointments kept current in an authorized app, within ServiceTitan's rules.
- Custom ServiceTitan Estimates & Invoice Integrations Estimate reporting, invoice reconciliation and finance tools that read ServiceTitan data carefully.
- How Much Does a Custom ServiceTitan API Integration Cost? The factors that set the price of a ServiceTitan integration, and the rates we publish.
What to have ready before we talk
None of this is required for a first call, but each answer makes the scope and the quote sharper.
- The problem in one sentence, and who has it (owner, office, dispatch, sales, technicians)
- Which ServiceTitan records are involved: customers, jobs, estimates, invoices, technicians, campaigns
- Whether the tool only reads data or must also create or change records
- Other systems that need to be involved, such as accounting, your website or ad platforms
- Whether you've already asked ServiceTitan's integrations team about API access for your account
- How many ServiceTitan accounts or business units are in scope
Related ServiceTitan development
Mesa Web Designers is an independent developer. We are not affiliated with, endorsed by, or a partner of ServiceTitan. ServiceTitan is a trademark of its owner. What an integration can do depends on your ServiceTitan products, the permissions your admin grants, and the APIs available to your account.
Start the conversation
Tell us what you want to build.
Describe the problem and the records involved. We'll tell you whether it fits the API, what access it needs, and what it costs.
- Web apps, portals and integrations start from $575, priced by complexity
- The developer who scopes it builds it and answers the phone
- Built for ServiceTitan contractors nationwide
What do you need built?
Pick what fits (pick any)
Rather talk? (480) 525-7582. 0% financing on any project, 25% down. See all pricing
API development: questions we hear a lot.
Which ServiceTitan API do you build on?
ServiceTitan's V2 APIs, which use OAuth 2.0 client credentials and are grouped by area such as CRM, jobs, estimates, accounting and reporting. The app only gets the areas your admin approves.
When is a marketplace app a better choice than custom development?
When the need is common and an existing app fits how you work. A maintained product from someone else is usually cheaper over time. Custom development makes sense when the need is specific to your company or joins data the existing options don't.
Where does the integration run?
On a server: your own hosting account or one set up for you as part of the project. ServiceTitan credentials never go into a web page or a phone app, and the server keeps logs of what it read and wrote.
Can you keep a full copy of our ServiceTitan data?
Not by default. ServiceTitan's API Terms limit how long API data may be stored unless its documentation permits it, so we design for keeping only what the tool needs and refreshing it, and confirm any longer retention with ServiceTitan before building.
Tell us what you want to build.
Describe the problem and the records involved. We'll tell you whether it fits the API, what access it needs, and what it costs.