ServiceTitan

ServiceTitan is a cloud field service management platform built for residential and commercial trades like HVAC, plumbing, electrical, and roofing. It provides an end-to-end operations suite — job booking, scheduling and dispatching, technician management, CRM, estimates and invoicing, and reporting. Its V2 REST API integrates field service data with external systems across your stack.

Power end-to-end data operations for your ServiceTitan API with Nexla. Our bi-directional ServiceTitan connector is purpose-built for ServiceTitan, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to ServiceTitan or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ServiceTitan workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

ServiceTitan uses the OAuth 2.0 Client Credentials Grant flow (two-legged, machine-to-machine authentication) for all API access. To connect Nexla to ServiceTitan, you need a Client ID, Client Secret, Application Key (App Key), and your Tenant ID. These are obtained through the ServiceTitan Developer Portal and your ServiceTitan account settings.

Access the ServiceTitan Developer Portal

The ServiceTitan Developer Portal is where you register your integration application and manage API credentials. You must have a ServiceTitan account to log in.

1. Navigate to https://developer.servicetitan.io/ and click Login to My Apps.

2. Sign in using the Production Environment option if you are connecting to your live ServiceTitan account, or the Integration Environment for testing and development purposes.

Create an Application and Obtain Your App Key

The App Key is a unique identifier tied to your integration application in the ServiceTitan Developer Portal. It is required as an HTTP request header (ST-App-Key) on every API call to identify which developer application is making the request.

1. After logging in to the Developer Portal, navigate to the My Apps tab.

2. Click Create App and provide a descriptive name and description for your integration application (for example, "Nexla Integration").

3. Add your ServiceTitan Tenant ID to the app and select the API scopes your integration requires. For use with Nexla, the relevant scopes include Job Planning, CRM, Dispatch, Pricebook, Sales, Equipment Systems, and Settings, corresponding to the endpoint categories available in the Nexla connector.

4. Save the application. Your Application Key (App Key) will be generated and displayed in the Keys > Application Key section of the app details page. Copy it and store it securely — you will enter this value in Nexla as the Application Key field.

Obtain Your Client ID and Client Secret

The Client ID and Client Secret are used together to request an OAuth 2.0 access token from the ServiceTitan authorization server at https://auth.servicetitan.io/connect/token.

1. Log in to your ServiceTitan account (not the Developer Portal) and navigate to Settings using the toolbar at the top of the screen.

2. In the settings side panel, search for Integrations and select API Application Access.

3. In the Manage API Application Access section, click Connect New App.

4. A pop-up will display the available applications registered to your account. Locate the application you created in the Developer Portal and click to select it.

5. Review the access request and the listed API scopes, then click Allow Access to authorize the integration.

6. Once access is granted, navigate to Application Details in the API Application Access section. Your Client ID is displayed there — copy it.

7. Copy your Client Secret from the same Application Details section. Store both credentials securely, as the Client Secret grants API access to your ServiceTitan data.

Important

The Client ID and Client Secret are environment-specific. Credentials generated in the Production Environment cannot be used to authenticate against the Integration (sandbox) Environment. Ensure you generate credentials in the correct environment for your use case.

Find Your Tenant ID

The Tenant ID is a numeric identifier that uniquely identifies your ServiceTitan organization. It is included in every API endpoint URL as a path parameter.

1. Log in to the ServiceTitan Developer Portal and navigate to the My Apps tab.

2. Your Tenant ID is listed in your application details. It is also available in your ServiceTitan account settings. Contact your ServiceTitan administrator if you need assistance locating it.

Additional details about obtaining and managing ServiceTitan API credentials are available in the ServiceTitan Developer Portal FAQ: App Key, Client ID & Secret.

Authenticate

Credentials required

Server-to-server OAuth2 authentication for ServiceTitan API integration.

Field	Required	Secret	Description
Client ID	Yes	No	OAuth2 Client ID from ServiceTitan developer portal
Client Secret	Yes	Yes	OAuth2 Client Secret from ServiceTitan developer portal
Access Token URL	Yes	No	OAuth2 token endpoint
Tenant ID	Yes	No	Your ServiceTitan organization Tenant ID
Application Key	Yes	Yes	ST-App-Key from ServiceTitan developer portal

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay, and enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

   ServiceTitan uses the OAuth 2.0 Client Credentials Grant (two-legged) flow for machine-to-machine authentication. Nexla handles token retrieval and renewal automatically — access tokens expire after 15 minutes and Nexla will request a new one using the credentials below without interrupting your data flows.

2. Enter your OAuth 2.0 Client ID in the Client ID field. This value is obtained from the Application Details section of API Application Access in your ServiceTitan account settings, as described in Prerequisites.

3. Enter your OAuth 2.0 Client Secret in the Client Secret field. This is the corresponding secret associated with your Client ID. This value is treated as a password and will be stored securely by Nexla.

4. Enter the OAuth 2.0 token endpoint URL in the Access Token URL field. The default value is https://auth.servicetitan.io/connect/token. This is the standard ServiceTitan authorization server endpoint and should not need to be changed.

5. Enter your ServiceTitan organization's Tenant ID in the Tenant ID field. This numeric identifier is included in all ServiceTitan API endpoint URLs to route requests to the correct organization. See Find Your Tenant ID in Prerequisites for instructions on locating this value.

6. Enter your Application Key in the Application Key field. This is the ST-App-Key value generated in the ServiceTitan Developer Portal when you created your integration application. It is sent as an HTTP request header on every API call and identifies which developer application is making the request.

   The Application Key is distinct from the Client ID. The App Key identifies your integration application in the Developer Portal, while the Client ID and Client Secret authenticate your specific organization's authorized access to the API.

7. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

The ServiceTitan connector enables you to ingest operational field service data — including jobs, appointments, customers, locations, technicians, estimates, pricebook items, and dispatch information — directly into Nexla. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the ServiceTitan connector tile, then select the credential that will be used to connect to the ServiceTitan instance, and click Next; or, create a new ServiceTitan credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common ServiceTitan API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

List Jobs

Retrieves all jobs from your ServiceTitan account with filtering and pagination support. Use this endpoint to ingest bulk job records for reporting, analytics, or synchronization with external systems. Jobs in ServiceTitan represent the core unit of work — each job tracks the customer, location, assigned technicians, job type, status, and associated appointments.

• This endpoint automatically paginates through all available jobs, fetching up to 50 records per page. No additional pagination configuration is required.

• Optionally, filter the jobs returned using the following date-based parameters to limit the data to a specific time range:

  • Modified On or After: Enter a date and time in ISO 8601 format (e.g., 2024-01-01T00:00:00Z) to retrieve only jobs that were modified on or after this datetime. This filter is particularly useful for incremental data loads, where you want to capture only new or updated jobs since the last run.
  • Modified Before: Enter a date and time in ISO 8601 format to retrieve only jobs modified before this datetime. Use this in combination with the Modified On or After parameter to define a precise modification date range.
  • Completed On or After: Enter a date and time in ISO 8601 format to retrieve only jobs that were completed on or after this datetime. Use this filter when your analysis focuses on completed work within a specific timeframe.

All three filter parameters are optional. When no filters are specified, all accessible jobs are returned. For large ServiceTitan tenants with many jobs, applying date filters is recommended to reduce data volume and improve performance. Refer to the ServiceTitan Job Planning API documentation for additional details on available query parameters.

Get Job Details

Retrieves full details for a single, specific job by its ServiceTitan Job ID. Use this endpoint when you need comprehensive information about one particular job, such as when building a job detail view, verifying job data, or triggering downstream actions based on a specific job's state.

• Enter the ServiceTitan Job ID in the required Job ID field:

  • Job ID (required): The unique numeric identifier of the job to retrieve. Job IDs can be obtained from the results of the List Jobs endpoint or from the ServiceTitan application's job detail URL.

This endpoint returns a single job record rather than a paginated list. It is best suited for targeted lookups. To retrieve records for multiple jobs, use the List Jobs endpoint instead.

List Appointments

Retrieves all appointments from your ServiceTitan account with filtering support. In ServiceTitan, an appointment represents the scheduled instance of a job — it specifies who is going out (the technician) and when. Every job has at least one appointment, created automatically at the time of booking. Use this endpoint to ingest appointment schedules for capacity planning, dispatch analysis, or integration with calendar systems.

• This endpoint automatically paginates through all available appointments, fetching up to 50 records per page.

• Optionally, filter the appointments returned using the following date-based parameters:

  • Starts On or After: Enter a date and time in ISO 8601 format to retrieve only appointments scheduled to start on or after this datetime.
  • Starts Before: Enter a date and time in ISO 8601 format to retrieve only appointments scheduled to start before this datetime. Use this in combination with Starts On or After to define a date range for appointment retrieval.

Both filter parameters are optional. Refer to the ServiceTitan Job Planning API documentation for full details on the appointment data model.

Get Appointment

Retrieves full details for a single appointment by its ServiceTitan Appointment ID. Use this endpoint when you need to look up all details for one specific appointment, such as the assigned technician, scheduled time, and associated job.

• Enter the appointment identifier in the required Appointment ID field:

  • Appointment ID (required): The unique numeric identifier of the appointment to retrieve. Appointment IDs can be obtained from the results of the List Appointments endpoint.

List Appointment Assignments

Retrieves technician-to-appointment assignment records from ServiceTitan. Use this endpoint to analyze technician workload distribution, track dispatch decisions, or audit assignment history across your field operations.

• This endpoint automatically paginates through all available assignment records, fetching up to 50 records per page.

• Optionally, filter assignments by the associated job using the following parameter:

  • Job ID: Enter a ServiceTitan Job ID to retrieve only the technician assignments related to that specific job.

The Job ID filter parameter is optional. When not specified, all accessible assignment records are returned. Refer to the ServiceTitan Dispatch API documentation for more information.

List Technicians

Retrieves all technician records in your ServiceTitan organization. Use this endpoint to synchronize your technician roster with external systems, build workforce analytics reports, or enrich job and appointment data with technician profile information.

• This endpoint automatically paginates through all technician records, fetching up to 50 records per page. No additional configuration parameters are required.

Technician data is managed in the ServiceTitan Settings module. Refer to the ServiceTitan Settings API documentation for details on the technician data model.

Get Technician

Retrieves full profile details for a single technician by their ServiceTitan Technician ID. Use this endpoint to look up a specific technician's information, including their skills, certifications, and contact details.

• Enter the technician identifier in the required Technician ID field:

  • Technician ID (required): The unique numeric identifier of the technician to retrieve. Technician IDs can be obtained from the results of the List Technicians endpoint.

List Business Units

Retrieves all business units (divisions) configured in your ServiceTitan organization. Business units in ServiceTitan are used to segment operations by trade, geography, or business line. Use this endpoint to ingest business unit reference data for enriching job and financial reporting.

• This endpoint automatically paginates through all business unit records, fetching up to 50 records per page. No additional configuration parameters are required.

List Job Types

Retrieves all job types configured in your ServiceTitan account. Job types categorize work orders by the nature of the service (for example, Installation, Maintenance, Repair). Use this endpoint to ingest job type reference data for use in analytics, filtering, or integration with external work order systems.

• This endpoint automatically paginates through all job type records, fetching up to 50 records per page. No additional configuration parameters are required.

List Customers

Retrieves all customer records from your ServiceTitan CRM with filtering support. In ServiceTitan, every job has a customer responsible for payment. Customer records contain contact information, service history, membership status, and more. Use this endpoint to synchronize your customer database with external CRM or marketing platforms, or to build customer analytics reports.

• This endpoint automatically paginates through all customer records, fetching up to 50 records per page.

• Optionally, filter the customers returned using the following date-based parameter:

  • Modified On or After: Enter a date and time in ISO 8601 format (e.g., 2024-01-01T00:00:00Z) to retrieve only customer records that were modified on or after this datetime. This is useful for incremental synchronization of customer data.

Refer to the ServiceTitan CRM API documentation for full details on the customer data model and available filter parameters.

Get Customer

Retrieves full details for a single customer by their ServiceTitan Customer ID. Use this endpoint for targeted customer lookups, such as when enriching a specific record or verifying customer data before processing.

• Enter the customer identifier in the required Customer ID field:

  • Customer ID (required): The unique numeric identifier of the customer to retrieve. Customer IDs can be obtained from the results of the List Customers endpoint.

List Locations

Retrieves all service location records from your ServiceTitan CRM. In ServiceTitan, a location is the physical address where a job is performed — each customer can have multiple service locations. Use this endpoint to ingest location data for geographic analysis, service territory management, or synchronization with external systems.

• This endpoint automatically paginates through all location records, fetching up to 50 records per page.

• Optionally, filter locations by their associated customer using the following parameter:

  • Customer ID: Enter a ServiceTitan Customer ID to retrieve only the service locations associated with that specific customer.

Get Location

Retrieves full details for a single service location by its ServiceTitan Location ID. Use this endpoint when you need complete address and metadata for one specific service location.

• Enter the location identifier in the required Location ID field:

  • Location ID (required): The unique numeric identifier of the service location to retrieve. Location IDs can be obtained from the results of the List Locations endpoint.

List Estimates

Retrieves all estimates (quotes) from your ServiceTitan account. Estimates in ServiceTitan are proposals presented to customers that outline the proposed services, materials, and pricing. Use this endpoint to analyze sales conversion rates, track outstanding proposals, or synchronize estimate data with quoting or ERP systems.

• This endpoint automatically paginates through all estimate records, fetching up to 50 records per page.

• Optionally, filter estimates by the associated job using the following parameter:

  • Job ID: Enter a ServiceTitan Job ID to retrieve only the estimates associated with that specific job.

Refer to the ServiceTitan Sales API documentation for details on the estimate data model.

Get Estimate

Retrieves full details for a single estimate by its ServiceTitan Estimate ID. Use this endpoint to retrieve all line items, pricing, and status information for a specific estimate.

• Enter the estimate identifier in the required Estimate ID field:

  • Estimate ID (required): The unique numeric identifier of the estimate to retrieve. Estimate IDs can be obtained from the results of the List Estimates endpoint.

List Installed Equipment

Retrieves all installed equipment records at customer locations. In ServiceTitan, installed equipment tracks the HVAC units, appliances, and other equipment installed at each customer location — including make, model, serial number, and installation date. Use this endpoint to build equipment maintenance schedules, warranty tracking systems, or asset management integrations.

• This endpoint automatically paginates through all installed equipment records, fetching up to 50 records per page.

• Optionally, filter installed equipment by the associated service location using the following parameter:

  • Location ID: Enter a ServiceTitan Location ID to retrieve only the equipment installed at that specific service location.

Refer to the ServiceTitan Equipment Systems API documentation for details on the installed equipment data model.

List Pricebook Services

Retrieves all service items from your ServiceTitan pricebook. The pricebook in ServiceTitan defines the standardized services, materials, and equipment that technicians can add to invoices and estimates. Use this endpoint to synchronize pricebook service definitions with external pricing or ERP systems.

• This endpoint automatically paginates through all pricebook service records, fetching up to 50 records per page. No additional configuration parameters are required.

Refer to the ServiceTitan Pricebook API documentation for details on the pricebook data model.

List Pricebook Materials

Retrieves all material items from your ServiceTitan pricebook. Materials represent the physical parts, components, and supplies that technicians use and bill for on service calls. Use this endpoint to synchronize pricebook material data with inventory management or procurement systems.

• This endpoint automatically paginates through all pricebook material records, fetching up to 50 records per page. No additional configuration parameters are required.

List Pricebook Equipment

Retrieves all equipment items from your ServiceTitan pricebook. Pricebook equipment items represent the systems and units (such as HVAC systems or water heaters) that can be sold and installed. Use this endpoint to synchronize pricebook equipment catalog data with external sales or inventory systems.

• This endpoint automatically paginates through all pricebook equipment records, fetching up to 50 records per page. No additional configuration parameters are required.

List Non-Job Events

Retrieves non-job events from the ServiceTitan dispatch board, such as time off, training sessions, meetings, and other technician schedule blocks that do not correspond to a customer job. Use this endpoint to analyze technician availability, build capacity planning reports, or integrate with HR systems for time and attendance tracking.

• This endpoint automatically paginates through all non-job event records, fetching up to 50 records per page.

• Optionally, filter non-job events by the assigned technician using the following parameter:

  • Technician ID: Enter a ServiceTitan Technician ID to retrieve only the non-job events associated with that specific technician.

Refer to the ServiceTitan Dispatch API documentation for more information on non-job event types and the data model.

List Technician Shifts

Retrieves technician shift schedules and availability windows from ServiceTitan. Shifts define the working hours and availability of each technician for scheduling purposes. Use this endpoint to analyze workforce scheduling patterns, build staffing reports, or integrate technician availability data with external workforce management systems.

• This endpoint automatically paginates through all technician shift records, fetching up to 50 records per page.

• Optionally, filter shifts by start date using the following parameter:

  • Starts On or After: Enter a date and time in ISO 8601 format to retrieve only shifts that start on or after this datetime.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

ServiceTitan data sources can also be manually configured to ingest data from any valid ServiceTitan V2 API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

All ServiceTitan V2 API endpoints follow the pattern https://api.servicetitan.io/{'{namespace}'}/v2/tenant/{'{tenantId}'}/{'{resource}'}. Your Tenant ID is automatically provided by your saved ServiceTitan credential for template-based sources; substitute it manually when configuring a source by hand. Most list endpoints return records under $.data[*], with pagination metadata (such as page.totalCount and page.hasMore) available at $.page. ServiceTitan also requires the ST-App-Key header on every request — Nexla adds this automatically using the Application Key stored in your ServiceTitan credential.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new ServiceTitan data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the ServiceTitan destination, and select the Send to Destination option from the menu. Select the ServiceTitan connector from the list of available destination connectors, then select the credential that will be used to connect to the ServiceTitan organization, and click Next; or, create a new ServiceTitan credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common ServiceTitan write endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Job

Creates a new job record in ServiceTitan. Use this endpoint to programmatically book service jobs from external systems such as a CRM, customer portal, or lead management platform. The data in your Nexset will be sent as the JSON body of a POST request to the ServiceTitan Job Planning API.

• Ensure that your Nexset data is structured as a JSON object containing the required ServiceTitan job fields before configuring this destination. At minimum, a job typically requires a customer ID, location ID, job type ID, and at least one appointment.
• No additional template parameters are required beyond selecting this endpoint. The full contents of each Nexset record will be sent as the JSON request body to the ServiceTitan jobs endpoint.

Refer to the ServiceTitan Job Planning API documentation for the complete list of required and optional fields for job creation, including field names, data types, and validation requirements.

Update Job

Updates an existing job in ServiceTitan by its Job ID using a PATCH request. Use this endpoint to push status changes, reschedule jobs, or update job details from external systems back into ServiceTitan.

• Enter the ServiceTitan Job ID of the record to be updated in the required Job ID field:

  • Job ID (required): The unique numeric identifier of the job to update. This value will be appended to the API endpoint URL as a path parameter. You can reference a field in your Nexset that contains the Job ID by using a Nexla field reference.
• The fields included in each Nexset record will be sent as the PATCH request body. Only the fields you include will be updated — fields not present in the payload will remain unchanged in ServiceTitan.

The Update Job endpoint uses a PATCH method, which means only the fields included in the request body will be modified. This is useful for partial updates, such as changing only the job status or priority without affecting other job fields. Refer to the ServiceTitan Job Planning API documentation for updateable field details.

Create Appointment

Creates a new appointment for a job in ServiceTitan. Appointments represent the scheduled service visit — specifying the date, time window, and assigned technician(s). Use this endpoint to schedule service appointments from external scheduling or booking systems.

• Ensure that your Nexset data includes the required appointment fields. At minimum, an appointment requires a job ID, start date/time, and end date/time.
• No additional template parameters are required beyond selecting this endpoint. The full contents of each Nexset record will be sent as the JSON request body to the ServiceTitan appointments endpoint.

Refer to the ServiceTitan Job Planning API documentation for the complete list of required and optional fields for appointment creation.

Update Appointment

Updates an existing appointment in ServiceTitan by its Appointment ID using a PATCH request. Use this endpoint to reschedule appointments, update time windows, or modify appointment details from external systems.

• Enter the ServiceTitan Appointment ID of the record to be updated in the required Appointment ID field:

  • Appointment ID (required): The unique numeric identifier of the appointment to update. This value will be appended to the API endpoint URL as a path parameter.
• Only the fields included in each Nexset record will be updated — fields not present in the payload will remain unchanged in ServiceTitan.

Assign Technician

Assigns or reassigns a technician to an appointment in ServiceTitan. Use this endpoint to automate dispatch decisions, push technician assignments from an external workforce management system, or synchronize assignment changes from a scheduling optimizer.

• Ensure that your Nexset data includes the appointment ID and the technician ID to be assigned. The payload should conform to the ServiceTitan appointment-assignments API request format.
• No additional template parameters are required beyond selecting this endpoint. The full contents of each Nexset record will be sent as the JSON request body to the ServiceTitan appointment-assignments endpoint.

Refer to the ServiceTitan Dispatch API documentation for the required fields and request format for technician assignment.

Create Customer

Creates a new customer record in the ServiceTitan CRM. Use this endpoint to add customers from external sources such as a lead management system, customer import file, or e-commerce platform directly into ServiceTitan.

• Ensure that your Nexset data includes the required customer fields. At minimum, a customer record typically requires a name and contact information.
• No additional template parameters are required beyond selecting this endpoint. The full contents of each Nexset record will be sent as the JSON request body.

Refer to the ServiceTitan CRM API documentation for the complete list of required and optional fields for customer creation, including address fields, contact details, and custom fields.

Update Customer

Updates an existing customer record in ServiceTitan by their Customer ID using a PATCH request. Use this endpoint to synchronize customer data changes from external CRM systems, update contact information, or apply bulk customer record corrections.

• Enter the ServiceTitan Customer ID of the record to be updated in the required Customer ID field:

  • Customer ID (required): The unique numeric identifier of the customer to update. This value will be appended to the API endpoint URL as a path parameter.
• Only the fields included in each Nexset record will be updated — fields not present in the payload will remain unchanged in ServiceTitan.

Create Location

Creates a new service location in the ServiceTitan CRM, associated with a customer. Use this endpoint to add service addresses for customers from external property management systems, address databases, or customer onboarding workflows.

• Ensure that your Nexset data includes the required location fields. At minimum, a location record typically requires a customer ID and a service address (street, city, state, zip code).
• No additional template parameters are required beyond selecting this endpoint. The full contents of each Nexset record will be sent as the JSON request body.

Refer to the ServiceTitan CRM API documentation for the complete list of required and optional fields for location creation.

Create Non-Job Event

Creates a non-job event for a technician in ServiceTitan, such as time off, training, a meeting, or another schedule block that is not associated with a customer job. Use this endpoint to push schedule blocks from external HR systems, time-off management tools, or workforce planning applications into the ServiceTitan dispatch board.

• Ensure that your Nexset data includes the required non-job event fields. At minimum, a non-job event typically requires a technician ID, event type, start datetime, and end datetime.
• No additional template parameters are required beyond selecting this endpoint. The full contents of each Nexset record will be sent as the JSON request body.

Refer to the ServiceTitan Dispatch API documentation for the required fields, supported event types, and request format for non-job event creation.

Manual configuration

ServiceTitan destinations can also be manually configured to send data to any valid ServiceTitan V2 API endpoint, including PATCH/PUT update operations and endpoints not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

ServiceTitan API endpoint URLs include your Tenant ID as a path component (for example, https://api.servicetitan.io/crm/v2/tenant/{'{tenantId}'}/customers). For update (PATCH) operations, include the numeric ID of the object to be updated at the end of the URL. ServiceTitan's V2 API accepts JSON for all write operations. The ST-App-Key and Authorization headers are added automatically by Nexla using your saved credential — you do not need to include them manually.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to ServiceTitan, open the destination resource menu, and select Activate.

The Nexset data will not be sent to ServiceTitan until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.