Skip to main content
Technical Preview

Overview

Client-mode REST API connector for ServiceTitan field service: create jobs from connected-equipment faults, patch, note and cancel them, attach installed equipment, add appointments and assign technicians, track technicians, register and update installed equipment, and read locations and lookup lists, with OAuth 2.0 client credentials plus the ST-App-Key header. This is one of the templates in the ServiceTitan REST API app (servicetitan). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No ServiceTitan tenant, app key or client credentials on the factory box (no SERVICETITAN_* variables); only static, mock, negative-control and fake-credential public probes ran.

Auth

OAuth 2.0 client credentials: GetToken posts grant_type=client_credentials&client_id&client_secret (form) to https://auth.servicetitan.io/connect/token; tokens last 900 s, no refresh token. API events: Authorization: <access_token> (raw, as in the portal’s first-call sample) + ST-App-Key: <app key> from payload; tenant id in the path. Every event also sends User-Agent: Coreflux-Broker. Auth headers used by the template: Authorization: {value.json.access_token}, ST-App-Key: {value.json.app_key}.

Template parameters

BASE_ADDRESS default: https://api.servicetitan.io.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call ListJobs by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026