Skip to content
Mesa Web Designers

API development

Custom ServiceTitan API Applications

Some problems need a screen ServiceTitan doesn't have: one list, built for one person's job, with the right records already pulled and nothing else on it.

Data flow

Data moves from ServiceTitan through Integration layer to Your app.

Demonstration of the data path for a custom application. The integration layer is the only part that talks to ServiceTitan.

The spreadsheet somebody rebuilds every Monday

Every ServiceTitan shop has one. The sales manager exports open estimates, deletes the columns nobody reads, sorts by age and color-codes the ones that matter before the 8 a.m. meeting. The install coordinator keeps a whiteboard because no single view shows which replacement jobs have equipment ordered, permits pulled and a crew assigned. The warehouse lead texts techs to find out what's on their trucks.

None of that means ServiceTitan is missing something it should have. It's built for thousands of companies, and these screens belong to one. A custom application is a small, focused web app that reads the records it needs from the ServiceTitan API, adds whatever your team tracks that ServiceTitan doesn't, and shows it the way the person doing the job thinks about it.

It sits beside ServiceTitan, not inside it. Your team still books, dispatches and invoices in ServiceTitan. The app takes over the part they were doing in a spreadsheet, a whiteboard or their head. For the overall approach to these projects, see ServiceTitan API development.

Examples of custom applications

These are illustrations of the kind of tool that fits, not finished products. Each depends on the scopes your admin approves and on how your company uses ServiceTitan.

  • Estimate recovery board

    Open estimates by age, value and technician, with stale ones flagged and a follow-up status the sales team updates. HomeService WebApp is an estimate-recovery application of this kind, built on the ServiceTitan API.

  • Install coordinator board

    For example, a shop selling system replacements could see each sold install with its appointment, assigned crew and the checklist items the coordinator tracks in the app: equipment ordered, permit filed, customer confirmed.

  • Sales manager review screen

    Each comfort advisor's week in one place: estimates presented, sold and dismissed, with the ones above a dollar threshold pulled to the top for a second look.

  • Truck stock helper

    Where a company uses ServiceTitan's inventory features and grants the scope, a simple view of what each truck carries, built around how the warehouse lead restocks.

  • Membership visit planner

    Upcoming maintenance visits from memberships and recurring services, grouped by area and month so the office can plan capacity before the spring rush.

How a custom application gets built

  1. 1

    Start with the person and the decision

    Who opens this screen, at what time of day, and what do they decide from it. A board for a dispatcher at 7 a.m. and a review for the owner on Friday are different products.

  2. 2

    Map every read and write

    Each record the app needs is listed with whether it's read or written. Most internal tools only read from ServiceTitan and keep their own notes and statuses in the app's database.

  3. 3

    Design the screens before the code

    Simple wireframes the user reacts to: what's on the list, how it sorts, what a row shows on a phone. Changes here cost minutes; changes after launch cost days.

  4. 4

    Set up roles and logins

    The app has its own sign-in, often through your company's Google or Microsoft accounts, with roles deciding who sees what. Staff never enter ServiceTitan passwords into it.

  5. 5

    Build against the integration environment

    Development runs in ServiceTitan's integration environment with credentials your admin approved. ServiceTitan API authentication and setup explains that part.

  6. 6

    Launch, host and support

    The app runs on a server you own or one set up for you, with backups, logs and an alert if the ServiceTitan connection fails.

Working inside ServiceTitan vs a custom app

NeedIn ServiceTitanCustom-built
Lists and viewsBuilt-in screens, filters and reports designed for every kind of contractor.One list, sorted and grouped the way one role works, with nothing unrelated on it.
Extra trackingCustom fields and tags, within what ServiceTitan supports.Checklists, notes and statuses that live in the app and reference the ServiceTitan record by its ID.
Who can use itServiceTitan users with the right roles and licenses.Anyone you give an app login, with access limited to the screens their role needs.
Changes to the workflowConfigured by your admin within the product's options.Changed in code when your process changes, documented as it goes.

Reads, writes and where the data lives

  • Read-first by design

    Reading is safer and cheaper to build. If a tool only needs to show jobs and estimates, it gets read scopes and nothing else.

  • Writes only where they help

    Some APIs accept changes, such as estimate status or job notes, when the app has write scope. We add a write only when it removes real double entry, and every write is logged.

  • What the app keeps

    The app's own data, like checklists and follow-up notes, is yours. ServiceTitan data is kept only as long as ServiceTitan's API Terms and documentation allow, and refreshed. See how sync and storage are designed.

  • Hosting

    A small server or managed platform is enough for most internal tools. What matters is that credentials stay server-side and the app is backed up and monitored, as with any of our custom web applications.

What this looks like by trade

  • HVAC

    A replacement-sales board for comfort advisors, or a pre-season list of maintenance visits by membership and area.

  • Plumbing

    A water heater and repipe follow-up list, with permit and inspection steps tracked in the app beside the ServiceTitan job.

  • Roofing

    A production board for tile and shingle jobs, showing materials, crew and weather holds during monsoon season.

  • Electrical

    A panel upgrade tracker that follows each job from estimate through utility coordination and final inspection.

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 role that will use the app and the decision it helps them make
  • The spreadsheet, whiteboard or report it replaces, if there is one
  • Which ServiceTitan records it reads, and anything it would need to write
  • What the app should track that ServiceTitan doesn't
  • How people should sign in, and who sees which screens
  • Where you'd like it hosted

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

Describe the screen your team is missing.

Tell us who would use it and what they do today instead. We'll sketch what the app would read, what it would track, and how it would be built.

  • 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
Step 2 of 4 · The details50%

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

Custom API applications: questions we hear a lot.

Do my staff need ServiceTitan logins to use a custom app?

No. The app connects to ServiceTitan with its own approved API credentials on the server. Staff sign in to the app itself, usually with company Google or Microsoft accounts, and never type a ServiceTitan password into it.

Can a custom app change records in ServiceTitan?

Some APIs accept changes when the app has write scope, and your admin has to approve that scope. We keep writes to the ones that remove real double entry, and log each one.

Will it work on technicians' phones?

Yes, if that's who it's for. The screens are designed for the device the user actually carries, and a phone layout is planned from the wireframe stage rather than squeezed in later.

Who owns the application?

You do. The code, the app's own database and the documentation are yours. ServiceTitan data inside it stays subject to ServiceTitan's API Terms and your account's permissions.

Is a custom app the same as a dashboard?

Not quite. A dashboard mostly measures, while an internal tool helps someone do a task: work a list, update a status, coordinate a job. Many projects end up with a little of both.

Describe the screen your team is missing.

Tell us who would use it and what they do today instead. We'll sketch what the app would read, what it would track, and how it would be built.