Reference · built on requestConnectorField service & CMMS

ServiceTitan

Jobs, appointments, customers, dispatch, and invoices from ServiceTitan through its V2 tenant APIs and export feeds.

Request accessPricing ↗

About

ServiceTitan is field service software for residential and commercial trades. Its V2 APIs are split by module: Job Planning and Management for jobs, appointments, and projects; CRM for customers, locations, leads, and bookings; Dispatch for assignments, arrival windows, and technician shifts; Accounting for invoices and payments; Settings for technicians and business units; plus Pricebook, Payroll, Timesheets, Memberships, Service Agreements, Forms, and Inventory. Every call is scoped to a tenant path (/tenant/{tenant}/) and carries an ST-App-Key header beside the OAuth token.

Fibric reads through the transactional endpoints and keeps history current with the export feeds. An operator proposes a reschedule, a technician assignment, a hold, or a job note, and a dispatcher approves it before anything is written.

This is a reference listing. It documents what Fibric would read from ServiceTitan and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Jobs, appointments, projects, job notes, and job status history through the Job Planning and Management API (jpm/v2)
  • Customers, contacts, locations, leads, and bookings through the CRM API (crm/v2)
  • Appointment assignments, arrival windows, technician shifts, capacity, zones, and technician tracking through the Dispatch API (dispatch/v2)
  • Invoices, invoice items, and payments through the Accounting API (accounting/v2)
  • Technicians, employees, and business units through the Settings API (settings/v2)
  • Export feeds (export/jobs, export/appointments, export/customers, export/invoices) that return hasMore and a continueFrom token for incremental pulls
  • Estimates, memberships, service agreements, technician ratings, and marketing reviews through their own v2 modules

Proposed actions

  • Target capability: propose a job change through Jobs_Update, a cancellation through Jobs_Cancel, or a note through Jobs_CreateNote
  • Target capability: propose rescheduling, holding, or confirming an appointment through the Appointments endpoints in jpm/v2
  • Target capability: propose assigning or unassigning technicians through appointment-assignments in dispatch/v2
  • Target capability: propose a new customer, location, lead, or booking through crm/v2
  • Target capability: propose an invoice update or an adjustment invoice through accounting/v2

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Confirm tomorrow's appointments

    Appointments with arrival windows are read from jpm/v2 and dispatch/v2. The operator drafts the confirmation and proposes Appointments_Confirm once the customer replies, so the board shows what is confirmed.

    With Appointment Reminder

  • Fill a gap when a job cancels

    A Jobs_Cancel or a hold frees a technician shift. The operator finds an unscheduled job in the same zone and proposes an assignment for the dispatcher to approve.

    With Field Dispatch

  • Chase unpaid invoices on a schedule

    Invoices and payments are read from accounting/v2. The operator proposes the next reminder and leaves a job note when the customer commits to a date.

    With Dunning Cadence

  • Reply to technician ratings

    Low technician ratings from Customer Interactions and reviews from Marketing Reputation are read as they arrive. The operator drafts a callback and proposes a job note for the office to approve.

    With Detractor Callback

Requirements

  • A ServiceTitan tenant whose administrator enables the app under Manage API Application Access and generates its client ID and client secret
  • An app registered in the ServiceTitan Developer Portal with the tenant ID added and the API scopes chosen, which produces the application key
  • A Developer Portal login, which a ServiceTitan administrator creates as a user in the integration or production environment
  • A separate client ID and secret for each tenant and each environment; integration-environment credentials are not accepted by the production hosts
Authentication
OAuth 2.0 client credentials against https://auth.servicetitan.io/connect/token, sent as a Bearer token together with an ST-App-Key header that carries the app's application key.

Limits

  • 600 calls per 10 seconds per application per tenant by default; reporting APIs allow 1 of the same report per minute per tenant
  • V2 webhooks are in beta and gated per app; new subscriptions to the earlier webhook version are restricted, so changes are polled through export feeds
  • ServiceTitan reviews each app registration before customer tenants can connect it
  • Export feeds return records in batches with a continueFrom token; a full history load is paced by the rate limit

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request ServiceTitan ↗

Questions and answers

Which ServiceTitan APIs does the connector call?
The V2 tenant APIs: Job Planning and Management, CRM, Dispatch, Accounting, and Settings, each under https://api.servicetitan.io/<module>/v2/tenant/{tenant}/. Other modules, such as Pricebook, Memberships, and Service Agreements, are added per deployment.
Does ServiceTitan push changes by webhook?
Not yet for new apps. ServiceTitan's portal lists V2 webhooks as a beta gated per app and restricts new subscriptions to the earlier version. The connector polls the export feeds, which return a continueFrom token so each pull resumes where the last one ended.
What does a tenant administrator have to do?
Sign into ServiceTitan, open Manage API Application Access, connect the app, and generate the client ID and secret for that tenant. Each tenant and each environment has its own pair, and the app key travels in the ST-App-Key header on every call.
Ask about ServiceTitan

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with ServiceTitan through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy