Modern field-service organizations generate enormous volumes of data: jobs created, technicians dispatched, invoices paid, customers contacted. But data alone is not insight.
At ServiceTitan, the API provides the gateway to unlock that insight. Knowing which fields matter, what they mean, and how to connect them is what separates routine operations from strategic performance.
In this article, we walk through major ServiceTitan API resources and key fields — explaining what each one does, how you can use them, and how they fit into a connected ecosystem built by a systems-oriented agency like Proven ROI.
ServiceTitan API Overview
The ServiceTitan V2 API platform supports multiple resource areas: CRM (customers, leads, bookings), Job Planning (jobs, appointments), Price book, Payroll, Inventory and more.
For each resource, you will find fields that map to operational entities (for example, a job record), transactional data (for example, invoice or payment), and metadata (for example, timestamps, external identifiers).
Understanding the structure and content of these fields allows you to integrate with other systems (CRM, marketing, analytics) and build dashboards or workflows that align with business performance rather than isolated data.
Major API Resource: CRM – Customers, Locations, Leads
Key Fields & Their Meaning
- Customer ID: Unique identifier for the bill-to customer in ServiceTitan. Used to link jobs and invoices.
- Location ID: Identifier for the job site or service address. Every job has a location record.
- Name, Address: Core fields for customer and location records — essential for mapping to external CRM systems.
- Contacts: A list of contact records under customer or location; sometimes leads to different treatments for decision-maker vs site contact.
- Custom Fields: Configurable fields you set up in ServiceTitan to capture business-specific data (for example, “Marketing Source”, “Referral Partner”).
- Do Not Mail, Do Not Service: Flags on the customer record controlling outreach or scheduling eligibility.
- External Data: Bridge fields for linking third-party systems (CRM, marketing automation) with ServiceTitan records.
How to Use These Fields Strategically
- Sync Customer ID and Location ID into your CRM to ensure job data links back to marketing origin.
- Populate Custom Fields with attribution or segment data so you can report across systems.
- Use the Do Not Mail / Do Not Service flags to prevent unwanted automation or campaigns.
- Leverage External Data fields to embed your own integration identifiers (for example your internal lead ID) so you can trace performance end-to-end across systems.
Major API Resource: Jobs and Appointments
Relevant Fields & Their Role
- Job ID: The unique identifier for the job record. Every service instance revolves around this.
- Bill-To Customer ID: Links job to the customer record. Important for attribution and customer lifetime value calculations.
- Location ID: The physical site where the work occurs, enabling geographic or service-zone analysis.
- Start, End: Scheduled start and end times for the job or appointment. Useful for technician workflow analytics.
- Technician IDs: The assigned technicians for the job. Enables efficiency, productivity and routing analysis.
- Status, Cancel Reason ID, Hold Reason ID: Fields related to job lifecycle and exceptions.
- Special Instructions, Summary: Free-form fields agencies tend to use for internal notes or segmentation triggers.
Strategic Use Cases
- Track time from job creation to completion using Start/End and Status fields to measure technician efficiency.
- Use Cancel Reason ID and Hold Reason ID to analyze service failure modes or bottlenecks.
- Link Job ID with marketing source data via your external system to determine which campaigns drive high-value jobs.
- Segment by Technician IDs and Location ID to understand performance by zone or team and optimize dispatch or routing decisions.
Major API Resource: Bookings and Leads
Important Fields to Know
- Booking ID: Identifier for an inquiry or request for service (before job creation).
- Source, Campaign ID, Booking Provider ID: Fields capturing the origin of the booking — critical for marketing attribution and ROI reporting.
- Is First-Time Client: Boolean field identifying new customers vs repeat customers — useful for acquisition cost calculations.
- Uploaded Images, External ID: Useful for API integrations that originate from web forms or external lead sources.
- Contacts: List of contact records under the booking, enabling outreach or follow-up automation.
How to Leverage These Fields
- Capture Source/Campaign ID and send it to your marketing automation or CRM as part of a unified attribution model.
- Use Booking ID as an early stage identifier in your pipeline so you can measure lead to job conversion rates.
- Apply Is First-Time-Client to segment acquisition vs retention and calculate cost per new client.
- Connect contacts from the booking into your CRM to trigger nurture workflows if the booking does not convert into a job.
Major API Resource: Pricebook, Services, Materials
Relevant Fields
- Service ID, Material ID, Category, Price, Cost: Core fields representing what you bill and what you cost.
- Discounts / Fees: Fields capturing special pricing or extra costs.
- Markup: Indicates internal margin logic.
Strategic Uses
- Map Service ID and Material ID to your CRM or analytics system to link job revenue back to marketing campaigns.
- Use Pricebook fields to analyze margin performance by service type or customer segment.
- Merge discount and markup data with job performance to identify which service types deliver the highest ROI.
Best Practices for Field Integration
- Define a Master Identifier: Use Customer ID, Job ID or Booking ID as your primary key in your integrated data warehouse or CRM to ensure matching across platforms.
- Synchronize Critical Attribution Fields: Source, Campaign ID, External ID, Booking Provider ID should flow seamlessly into your CRM so marketing gets full visibility.
- Clean Custom Fields: Ensure custom fields are consistently populated and standardized across systems to avoid segment data fragmentation.
- Schedule Delta Sync + Webhooks: Use modifiedSince parameters and webhooks to capture only changed records rather than full refreshes, improving efficiency.
- Audit Status and Lifecycle Fields: Fields like Status, Cancel Reason ID and Hold Reason ID provide insights into wrench in the gears — track them for continuous improvement.
- Map Date/Time Fields in UTC: Many API fields use UTC timestamps — convert to your local timezone if needed for reporting accuracy.
Q&A: Common Integration Questions
Q1. Can I update any field through the API?
No. Some fields are read-only (for example certain status transitions), and certain records cannot be deleted through API (for example jobs once invoiced).
Q2. How do I manage rate limits or pagination?
ServiceTitan’s API supports pagination parameters and you should design your integration to respect rate limits, use incremental (delta) syncs, and use webhooks where available.
Q3. How does integration help with marketing attribution?
By capturing Source, Campaign ID, Booking ID and Job ID you can trace a leads first touch through to closed job revenue — bridging marketing spend to operational output.
Q4. What happens if I introduce custom fields?
Custom fields expand your tracking capacity. However you must ensure your integration logic includes them consistently, and that changes to custom field configurations are managed and documented.
Q5. Does ServiceTitan support triggers when records change?
Yes — webhooks or event subscriptions enable near real-time updates so your ecosystem can react instantly rather than relying solely on scheduled pull operations.
The ServiceTitan API is more than just a technical resource. It is the backbone of connected operations, linking marketing, sales, service, and finance into one measurable flow. At Proven ROI we help businesses master the fields that matter, map them into intelligent systems, and turn data into performance.
Whether you are scaling operations, connecting marketing to jobs, or building dashboards to monitor profit by campaign, understanding these key fields is the first step toward integration that delivers measurable return.
Dive in. Map the fields. Connect the systems.
Your data knows the story, now you can tell it.
Human Strategy. Intelligent Systems. Proven ROI.
Sources
- ServiceTitan Developer Documentation
- Proven ROI Internal Integration Framework
- Proven ROI Data Architecture Methodology
- HubSpot Developer Documentation
- Salesforce Developer API Reference
- Zapier Platform Integration Guide
- Proven ROI Case Studies and Client Integrations
