> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to ServiceTitan

The ServiceTitan connector lets your AI agent act in each user's ServiceTitan account. Each user signs in to ServiceTitan once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 29 tools.

**Authentication:** OAuth 2.0 Client Credentials
**Categories:** CRM & Sales, Project Management
**Tools:** 29: 19 read, 9 write, 1 destructive
**Users sign in with:** Service account
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=SERVICETITAN)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the ServiceTitan connection

   In **AgentKit > Connections**, create a ServiceTitan connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'servicetitan_appointment_assignments_list',
  toolInput: {
    app_key: '<app_key>',
    tenant_id: '<tenant_id>',
  },
  connector: 'servicetitan',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="servicetitan_appointment_assignments_list",
    tool_input={
        "app_key": "<app_key>",
        "tenant_id": "<tenant_id>",
    },
    connection_name="servicetitan",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `servicetitan_appointment_assignments_list`

List Appointment Assignments · Read-only

List technician assignments on job appointments in a ServiceTitan tenant, filtered by appointment, job, technician or appointment start date.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each assignment has id, technicianId, technicianName, appointmentId, jobId, assignedOn and status.
Use this to see who is assigned to what. Use servicetitan_appointments_list for appointment times.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which assignments to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `appointment_ids` (`string`, optional): Comma-separated appointment IDs to return assignments for. Example: 567890,567891
- `appointment_starts_before` (`string`, optional): Return assignments whose appointment starts before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `appointment_starts_on_or_after` (`string`, optional): Return assignments whose appointment starts on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `ids` (`string`, optional): Comma-separated list of assignment IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `job_id` (`integer`, optional): Return assignments for this job. Example: 456789
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, CreatedOn, ModifiedOn. Example: -ModifiedOn
- `technician_ids` (`string`, optional): Comma-separated technician IDs to return assignments for. Example: 5001,5002

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_appointments_list`

List Appointments · Read-only

List job appointments in a ServiceTitan tenant, filtered by job, customer, technician, status or start, created and modified dates.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each appointment has id, jobId, appointmentNumber, start, end, arrival window, status and customerId.
Use this to see the schedule. Use servicetitan_appointment_assignments_list for which technicians are assigned.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which appointments to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `customer_id` (`integer`, optional): Return appointments for this customer. Example: 123456
- `ids` (`string`, optional): Comma-separated list of appointment IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `job_id` (`integer`, optional): Return appointments for this job. Example: 456789
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, ModifiedOn, CreatedOn. Example: -ModifiedOn
- `starts_before` (`string`, optional): Return appointments that start before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `starts_on_or_after` (`string`, optional): Return appointments that start on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `status` (`string`, optional): Return appointments with this status: Scheduled, Dispatched, Working, Hold, Done or Canceled. Example: Scheduled. One of: `Scheduled`, `Dispatched`, `Working`, `Hold`, `Done`, `Canceled`.
- `technician_id` (`integer`, optional): Return appointments this technician is assigned to. Example: 5001

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_business_units_list`

List Business Units · Read-only

List business units in a ServiceTitan tenant, optionally filtered by name or active status.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each business unit has id, name, officialName, email, phoneNumber, address and active.
Use this to get the business_unit_id that servicetitan_job_create needs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which business units to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `ids` (`string`, optional): Comma-separated list of business unit IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `name` (`string`, optional): Return business units whose name contains this text (case-insensitive). Example: HVAC
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, Name, CreatedOn, ModifiedOn. Example: -ModifiedOn

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_campaigns_list`

List Campaigns · Read-only

List marketing campaigns in a ServiceTitan tenant, optionally filtered by name, phone number or active status.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each campaign has id, name, category, active and campaign phone numbers.
Use this to get the campaign_id that servicetitan_job_create and servicetitan_lead_create need.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which campaigns to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `campaign_phone_number` (`string`, optional): Return campaigns that use this phone number. Example: 5555550100
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `ids` (`string`, optional): Comma-separated list of campaign IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `name` (`string`, optional): Return campaigns whose name contains this text (case-insensitive). Example: Google Ads
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, Name, CreatedOn, ModifiedOn. Example: -ModifiedOn

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_customer_contacts_list`

List Customer Contacts · Read-only

List the contact methods (phone, mobile, email, fax) saved on a ServiceTitan customer.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each contact has id, type, value, memo and phoneSettings.
Use this to get a customer's phone number or email. Use servicetitan_customer_get for the customer's address and flags.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `customer_id` (`string`, required): ID of the customer. Example: 123456
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100

Example input: `{"app_key":"<app_key>","customer_id":"<customer_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_customer_get`

Get Customer · Read-only

Get one ServiceTitan customer by ID.
Returns the customer's name, type (Residential or Commercial), bill-to address, balance, flags such as doNotService, tags, custom fields and created/modified dates.
Use servicetitan_customers_list to search when you don't have the ID. Use servicetitan_customer_contacts_list for phone numbers and emails.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `customer_id` (`string`, required): ID of the customer. Get it from servicetitan_customers_list. Example: 123456
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890

Example input: `{"app_key":"<app_key>","customer_id":"<customer_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_customers_list`

List Customers · Read-only

List customers in a ServiceTitan tenant, filtered by name, address, phone, active status or created/modified dates.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each customer has id, name, type, address, balance, doNotService, active and custom fields.
Use this to find a customer ID. Use servicetitan_customer_get when you already have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which customers to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `city` (`string`, optional): Return customers in this city. Example: Austin
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `ids` (`string`, optional): Comma-separated list of customer IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `name` (`string`, optional): Return customers with this name. Example: Jane Smith
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `phone` (`string`, optional): Return customers that have a contact with this phone number. Example: 5555551234
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, ModifiedOn, CreatedOn. Example: -ModifiedOn
- `state` (`string`, optional): Return customers in this state. Example: TX
- `street` (`string`, optional): Return customers on this street. Example: 123 Main St
- `zip` (`string`, optional): Return customers with this zip or postal code. Example: 78701

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_invoices_list`

List Invoices · Read-only

List invoices in a ServiceTitan tenant, filtered by customer, job, business unit, invoice date, due date, total or status. By default all invoices are returned regardless of status.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each invoice has id, referenceNumber, invoiceDate, dueDate, subTotal, salesTax, total, balance, customer, location, businessUnit, job and syncStatus.
Use servicetitan_payments_list for payments received.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active_state` (`string`, optional): Which invoices to return by active state: ActiveOnly, InactiveOnly or All. Example: All. One of: `ActiveOnly`, `InactiveOnly`, `All`.
- `business_unit_id` (`integer`, optional): Return invoices for this business unit. Example: 789
- `customer_id` (`integer`, optional): Return invoices for this customer. Example: 123456
- `due_date_before` (`string`, optional): Return invoices due before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `due_date_on_or_after` (`string`, optional): Return invoices due on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `ids` (`string`, optional): Comma-separated list of invoice IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `invoiced_on_before` (`string`, optional): Return invoices dated before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `invoiced_on_or_after` (`string`, optional): Return invoices dated on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `job_id` (`integer`, optional): Return invoices linked to this job. Example: 456789
- `job_number` (`string`, optional): Return invoices linked to this job number. Example: 10045
- `modified_before` (`string`, optional): Return invoices modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return invoices modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `number` (`string`, optional): Return invoices with this reference number. Example: 10045
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `statuses` (`array`, optional): Transaction statuses to include: Pending, Posted or Exported. All statuses are included by default. Example: ["Posted"]
- `total_greater` (`number`, optional): Return invoices with a total greater than or equal to this amount. Example: 100
- `total_less` (`number`, optional): Return invoices with a total less than or equal to this amount. Example: 5000

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_job_cancel_reasons_list`

List Job Cancel Reasons · Read-only

List the job cancel reasons configured in a ServiceTitan tenant.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each reason has id, name and active.
Use this to get the reason_id that servicetitan_job_cancel needs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which cancel reasons to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: active and inactive reasons are both returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, ModifiedOn, CreatedOn. Example: -ModifiedOn

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_job_get`

Get Job · Read-only

Get one ServiceTitan job by ID.
Returns the job number, status, customer and location IDs, business unit, job type, priority, campaign, tags, appointment count, invoice ID, total and completion date.
Use servicetitan_jobs_list to find jobs by customer, status or date. Use servicetitan_appointments_list with job_id for its appointments.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `job_id` (`string`, required): ID of the job. Get it from servicetitan_jobs_list. Example: 456789
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890

Example input: `{"app_key":"<app_key>","job_id":"<job_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_job_notes_list`

List Job Notes · Read-only

List the notes on a ServiceTitan job.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each note has text, isPinned, createdById and createdOn.
Use servicetitan_job_note_create to add a note.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `job_id` (`string`, required): ID of the job. Example: 456789
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100

Example input: `{"app_key":"<app_key>","job_id":"<job_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_job_types_list`

List Job Types · Read-only

List the job types configured in a ServiceTitan tenant, optionally filtered by name or priority.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each job type has id, name, businessUnitIds, duration, priority, class and active.
Use this to get the job_type_id that servicetitan_job_create and servicetitan_lead_create need.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which job types to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `ids` (`string`, optional): Comma-separated list of job type IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `name` (`string`, optional): Return job types with this name. Example: AC Repair
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `priority` (`string`, optional): Return job types with this priority. Example: Normal

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_jobs_list`

List Jobs · Read-only

List jobs in a ServiceTitan tenant, filtered by status, customer, location, technician, job type, business unit or appointment, created, modified and completed dates.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each job has id, jobNumber, customerId, locationId, jobStatus, businessUnitId, jobTypeId, priority, campaignId, appointmentCount, total and completedOn.
Use this to find jobs. Use servicetitan_job_get when you already have the job ID, and servicetitan_appointments_list for appointment times.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `appointment_starts_before` (`string`, optional): Return jobs with any appointment starting before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `appointment_starts_on_or_after` (`string`, optional): Return jobs with any appointment starting on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `business_unit_id` (`integer`, optional): Return jobs in this business unit. Example: 789
- `completed_before` (`string`, optional): Return jobs completed before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `completed_on_or_after` (`string`, optional): Return jobs completed on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `customer_id` (`integer`, optional): Return jobs for this customer. Example: 123456
- `ids` (`string`, optional): Comma-separated list of job IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `job_status` (`string`, optional): Return jobs with this status: Scheduled, Dispatched, InProgress, Hold, Completed or Canceled. Example: Scheduled. One of: `Scheduled`, `Dispatched`, `InProgress`, `Hold`, `Completed`, `Canceled`.
- `job_type_id` (`integer`, optional): Return jobs of this job type. Example: 321
- `location_id` (`integer`, optional): Return jobs at this location. Example: 234567
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `number` (`string`, optional): Return the job with this job number. Example: 10045
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `priority` (`string`, optional): Return jobs with this priority: Low, Normal, High or Urgent. Example: High. One of: `Low`, `Normal`, `High`, `Urgent`.
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, ModifiedOn, CreatedOn, Priority. Example: -ModifiedOn
- `technician_id` (`integer`, optional): Return jobs where this technician is assigned to any appointment. Example: 5001

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_lead_get`

Get Lead · Read-only

Get one ServiceTitan lead by ID.
Returns the lead's status, customer and location IDs, campaign, business unit, job type, priority, summary, call reason and follow-up date.
Use servicetitan_leads_list to find leads by status or customer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `lead_id` (`string`, required): ID of the lead. Get it from servicetitan_leads_list. Example: 345678
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890

Example input: `{"app_key":"<app_key>","lead_id":"<lead_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_leads_list`

List Leads · Read-only

List leads in a ServiceTitan tenant, filtered by status, customer, phone, name or created/modified dates.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each lead has id, status, customerId, locationId, campaignId, jobTypeId, priority, summary and followUpDate.
Use this to review open leads. Use servicetitan_lead_get when you already have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `customer_id` (`integer`, optional): Return leads for this customer. Example: 123456
- `ids` (`string`, optional): Comma-separated list of lead IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `lead_customer_name` (`string`, optional): Return leads with this customer name. Example: Jane Smith
- `lead_phone` (`string`, optional): Return leads with this phone number. Example: 5555551234
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, ModifiedOn, CreatedOn. Example: -ModifiedOn
- `status` (`string`, optional): Return leads with this status: Open, Dismissed or Converted. Example: Open. One of: `Open`, `Dismissed`, `Converted`.

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_location_get`

Get Location · Read-only

Get one ServiceTitan service location by ID.
Returns the location's name, customerId, address, tax zone, active state, tags and custom fields.
Use servicetitan_locations_list to find a location by customer or address.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `location_id` (`string`, required): ID of the location. Get it from servicetitan_locations_list. Example: 234567
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890

Example input: `{"app_key":"<app_key>","location_id":"<location_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_locations_list`

List Locations · Read-only

List service locations in a ServiceTitan tenant, filtered by customer, name, address or created/modified dates.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each location has id, customerId, name, address, active and custom fields.
Use this to find the location ID a job needs. Use servicetitan_location_get when you already have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which locations to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `city` (`string`, optional): Return locations in this city. Example: Austin
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `customer_id` (`integer`, optional): Return only locations that belong to this customer. Example: 123456
- `ids` (`string`, optional): Comma-separated list of location IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `name` (`string`, optional): Return locations with this name. Example: Jane Smith - Home
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, ModifiedOn, CreatedOn. Example: -ModifiedOn
- `state` (`string`, optional): Return locations in this state. Example: TX
- `street` (`string`, optional): Return locations on this street. Example: 123 Main St
- `zip` (`string`, optional): Return locations with this zip or postal code. Example: 78701

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_payments_list`

List Payments · Read-only

List payments in a ServiceTitan tenant, filtered by customer, invoice, paid date, total or created and modified dates.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each payment has id, referenceNumber, date, type, total, unappliedAmount, customer and appliedTo invoices.
Use servicetitan_invoices_list for invoice totals and balances.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active_state` (`string`, optional): Which payments to return by active state: ActiveOnly, InactiveOnly or All (default ActiveOnly). Example: All. One of: `ActiveOnly`, `InactiveOnly`, `All`.
- `applied_to_invoice_ids` (`string`, optional): Comma-separated invoice IDs; return payments applied to them. Example: 678901,678902
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `customer_id` (`integer`, optional): Return payments from this customer. Example: 123456
- `ids` (`string`, optional): Comma-separated list of payment IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `paid_on_after` (`string`, optional): Return payments paid on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `paid_on_before` (`string`, optional): Return payments paid before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `total_greater` (`number`, optional): Return payments with a total greater than or equal to this amount. Example: 100
- `total_less` (`number`, optional): Return payments with a total less than or equal to this amount. Example: 5000

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_technicians_list`

List Technicians · Read-only

List technicians in a ServiceTitan tenant, optionally filtered by name or active status.
Returns page, pageSize, hasMore, totalCount (when requested) and a data array. Each technician has id, userId, name, businessUnitId, email, phoneNumber, team and active.
Use this to get technician IDs for servicetitan_appointment_technicians_assign and job filters.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`string`, optional): Which technicians to return by active status: True (active only), False (inactive only) or Any. ServiceTitan's default: only active records are returned by default. Example: Any. One of: `True`, `Any`, `False`.
- `created_before` (`string`, optional): Return records created before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `created_on_or_after` (`string`, optional): Return records created on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `ids` (`string`, optional): Comma-separated list of technician IDs to look up (maximum 50). Example: 101,102,103
- `include_total` (`boolean`, optional): Set to true to include the total record count in the response (totalCount). Example: true
- `modified_before` (`string`, optional): Return records modified before this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `modified_on_or_after` (`string`, optional): Return records modified on or after this date/time (ISO 8601 date-time in UTC). Example: 2026-01-01T00:00:00Z
- `name` (`string`, optional): Return technicians whose name contains this text (case-insensitive). Example: Mike
- `page` (`integer`, optional): Page number to return, starting from 1. Example: 2
- `page_size` (`integer`, optional): How many records to return per page (ServiceTitan's default is 50). Example: 100
- `sort` (`string`, optional): Sort order: +FieldName for ascending or -FieldName for descending. Available fields: Id, Name, CreatedOn, ModifiedOn. Example: -ModifiedOn

Example input: `{"app_key":"<app_key>","tenant_id":"<tenant_id>"}`

### `servicetitan_appointment_reschedule`

Reschedule Appointment · Write

Move a ServiceTitan job appointment to a new start and end time, and optionally a new arrival window.
Returns the updated appointment.
Use servicetitan_appointments_list to find the appointment ID. Use servicetitan_appointment_technicians_assign to change who is assigned.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `appointment_id` (`string`, required): ID of the appointment. Get it from servicetitan_appointments_list. Example: 567890
- `end` (`string`, required): New end date/time in UTC (ISO 8601). Example: 2026-12-02T17:00:00Z
- `start` (`string`, required): New start date/time in UTC (ISO 8601). Example: 2026-12-02T15:00:00Z
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `arrival_window_end` (`string`, optional): New arrival window end in UTC, if arrival windows are configured. Example: 2026-12-02T16:00:00Z
- `arrival_window_start` (`string`, optional): New arrival window start in UTC, if arrival windows are configured. Example: 2026-12-02T14:00:00Z

Example input: `{"app_key":"<app_key>","appointment_id":"<appointment_id>","end":"<end>","start":"<start>","tenant_id":"<tenant_id>"}`

### `servicetitan_appointment_technicians_assign`

Assign Technicians to Appointment · Write

Assign one or more technicians to a ServiceTitan job appointment.
Returns the appointment. Call servicetitan_appointment_assignments_list to see the assignments.
Get technician IDs from servicetitan_technicians_list and appointment IDs from servicetitan_appointments_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `job_appointment_id` (`integer`, required): ID of the appointment to assign technicians to. Example: 567890
- `technician_ids` (`array`, required): IDs of the technicians to assign. Example: [5001, 5002]
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890

Example input: `{"app_key":"<app_key>","job_appointment_id":567890,"technician_ids":[5001,5002],"tenant_id":"<tenant_id>"}`

### `servicetitan_customer_create`

Create Customer · Write

Create a customer in ServiceTitan with a bill-to address and at least one service location.
Returns the new customer with its id, address, locations and contacts.
Use servicetitan_customers_list first to avoid duplicates. Use servicetitan_customer_update to change an existing customer.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `address` (`object`, required): Bill-to address of the customer. Address as a JSON object with street, city, state, zip and country (all required) and optional unit, latitude and longitude. Example: {"street": "123 Main St", "unit": "Suite 4", "city": "Austin", "state": "TX", "zip": "78701", "country": "USA"}
- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `name` (`string`, required): Customer's name, as a person or business name. Example: Jane Smith
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `contacts` (`array`, optional): Customer contact methods. Contact methods as a JSON array. Each item needs a type (Phone, MobilePhone, Email or Fax) and a value, plus an optional memo. Example: [{"type": "MobilePhone", "value": "5555551234", "memo": "Owner"}, {"type": "Email", "value": "jane@example.com"}]
- `do_not_mail` (`boolean`, optional): Set to true to flag the customer as do not mail. Example: false
- `do_not_service` (`boolean`, optional): Set to true to flag the customer as do not service. Example: false
- `locations` (`array`, optional): Service locations for the customer as a JSON array. ServiceTitan requires at least one. Each location needs a name and an address object (street, city, state, zip, country), and can have contacts in the same shape as the customer contacts. If you leave this empty, the tool creates one location named after the customer at the bill-to address. Example: [{"name": "Jane Smith - Home", "address": {"street": "123 Main St", "city": "Austin", "state": "TX", "zip": "78701", "country": "USA"}}]
- `tag_type_ids` (`array`, optional): IDs of tag types to put on the customer. Example: [101, 102]
- `type` (`string`, optional): Customer type: Residential or Commercial. Example: Residential. One of: `Residential`, `Commercial`.

Example input: `{"address":{"street":"123 Main St","unit":"Suite 4","city":"Austin","state":"TX","zip":"78701","country":"USA"},"app_key":"<app_key>","name":"<name>","tenant_id":"<tenant_id>"}`

### `servicetitan_customer_note_create`

Add Customer Note · Write

Add a note to a ServiceTitan customer record, optionally pinned to the top or copied to the customer's active locations.
Returns the new note with its text, pinned state and created date.
Use servicetitan_job_note_create to note a specific job instead.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `customer_id` (`string`, required): ID of the customer. Example: 123456
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `text` (`string`, required): Text of the note. Example: Customer prefers morning appointments.
- `add_to_locations` (`boolean`, optional): Set to true to add the same note to all of the customer's active locations. Example: false
- `pin_to_top` (`boolean`, optional): Set to true to pin the note to the top of the customer's notes. Example: true

Example input: `{"app_key":"<app_key>","customer_id":"<customer_id>","tenant_id":"<tenant_id>","text":"<text>"}`

### `servicetitan_customer_update`

Update Customer · Write

Update fields on an existing ServiceTitan customer. Only the fields you send change.
Returns the updated customer.
Use servicetitan_customer_create for a new customer. To deactivate a customer, set active to false.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `customer_id` (`string`, required): ID of the customer. Get it from servicetitan_customers_list. Example: 123456
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `active` (`boolean`, optional): Set to false to deactivate the customer, or true to reactivate. Example: false
- `address` (`object`, optional): New bill-to address. Send the full address. Address as a JSON object with street, city, state, zip and country (all required) and optional unit, latitude and longitude. Example: {"street": "123 Main St", "unit": "Suite 4", "city": "Austin", "state": "TX", "zip": "78701", "country": "USA"}
- `do_not_mail` (`boolean`, optional): Flag the customer as do not mail (true) or clear the flag (false). Example: true
- `do_not_service` (`boolean`, optional): Flag the customer as do not service (true) or clear the flag (false). Example: false
- `name` (`string`, optional): New customer name. Example: Jane Smith-Lee
- `tag_type_ids` (`array`, optional): Full list of tag type IDs for the customer. This replaces the customer's tags. Example: [101, 102]
- `type` (`string`, optional): New customer type: Residential or Commercial. Example: Commercial. One of: `Residential`, `Commercial`.

Example input: `{"app_key":"<app_key>","customer_id":"<customer_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_job_create`

Create Job · Write

Book a new job in ServiceTitan for a customer location, with one or more appointments.
Returns the new job with its id, jobNumber, jobStatus and firstAppointmentId.
Use servicetitan_lead_create when the work isn't ready to schedule. Get the IDs this needs from servicetitan_customers_list, servicetitan_locations_list, servicetitan_business_units_list, servicetitan_job_types_list and servicetitan_campaigns_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `appointments` (`array`, required): Appointments for the job as a JSON array; at least one is required. Each item needs start and end (ISO 8601 UTC) and can have arrivalWindowStart, arrivalWindowEnd and technicianIds. Example: [{"start": "2026-12-01T15:00:00Z", "end": "2026-12-01T17:00:00Z", "technicianIds": [5001]}]
- `business_unit_id` (`integer`, required): ID of the business unit doing the work. Get it from servicetitan_business_units_list. Example: 789
- `campaign_id` (`integer`, required): ID of the marketing campaign the job came from. Get it from servicetitan_campaigns_list. Example: 456
- `customer_id` (`integer`, required): ID of the job's customer. Example: 123456
- `job_type_id` (`integer`, required): ID of the job type. Get it from servicetitan_job_types_list. Example: 321
- `location_id` (`integer`, required): ID of the job's service location; it must belong to the customer. Example: 234567
- `priority` (`string`, required): Job priority: Low, Normal, High or Urgent. Example: Normal. One of: `Low`, `Normal`, `High`, `Urgent`.
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `customer_po` (`string`, optional): Customer purchase order number. Example: PO-7788
- `lead_id` (`integer`, optional): ID of the lead this job comes from. Example: 345678
- `no_charge` (`boolean`, optional): Set to true for a no-charge job. Example: false
- `project_id` (`integer`, optional): ID of the project to add the job to. Example: 9001
- `sold_by_id` (`integer`, optional): ID of the technician who sold the job. Example: 5001
- `summary` (`string`, optional): Job summary describing the work; HTML is allowed. Example: Replace capacitor on outdoor AC unit.
- `tag_type_ids` (`array`, optional): IDs of tag types to put on the job. Example: [101, 102]

Example input: `{"app_key":"<app_key>","appointments":[],"business_unit_id":789,"campaign_id":456,"customer_id":123456,"job_type_id":321,"location_id":234567,"priority":"Low","tenant_id":"<tenant_id>"}`

### `servicetitan_job_note_create`

Add Job Note · Write

Add a note to a ServiceTitan job, optionally pinned to the top.
Returns the new note with its text, pinned state and created date.
Use servicetitan_customer_note_create for a note on the customer record instead.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `job_id` (`string`, required): ID of the job. Example: 456789
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `text` (`string`, required): Text of the note. Example: Gate code is 4321.
- `pin_to_top` (`boolean`, optional): Set to true to pin the note to the top of the job's notes. Example: true

Example input: `{"app_key":"<app_key>","job_id":"<job_id>","tenant_id":"<tenant_id>","text":"<text>"}`

### `servicetitan_job_update`

Update Job · Write

Update fields on an existing ServiceTitan job, such as its summary, priority, job type, business unit or customer PO. Only the fields you send change.
Returns the updated job.
Use servicetitan_appointment_reschedule to move an appointment and servicetitan_job_cancel to cancel the job.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `job_id` (`string`, required): ID of the job. Example: 456789
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `business_unit_id` (`integer`, optional): New business unit ID. Example: 789
- `campaign_id` (`integer`, optional): New campaign ID. Example: 456
- `customer_po` (`string`, optional): New customer purchase order number. Example: PO-7789
- `job_type_id` (`integer`, optional): New job type ID. Example: 321
- `no_charge` (`boolean`, optional): Set to true to make it a no-charge job, false to clear. Example: true
- `priority` (`string`, optional): New priority: Low, Normal, High or Urgent. Example: Urgent. One of: `Low`, `Normal`, `High`, `Urgent`.
- `sold_by_id` (`integer`, optional): ID of the technician who sold the job. Example: 5001
- `summary` (`string`, optional): New job summary; HTML is allowed. Example: Replace capacitor and clean coils.
- `tag_type_ids` (`array`, optional): Full list of tag type IDs for the job. This replaces the job's tags: tags you leave out are removed. Example: [101, 102]

Example input: `{"app_key":"<app_key>","job_id":"<job_id>","tenant_id":"<tenant_id>"}`

### `servicetitan_lead_create`

Create Lead · Write

Create a follow-up lead in ServiceTitan for an existing customer or for a prospect with contact details.
Returns the new lead with its id and status.
Use servicetitan_job_create instead when the work is ready to schedule. Get campaign IDs from servicetitan_campaigns_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `campaign_id` (`integer`, required): ID of the marketing campaign the lead came from. Get it from servicetitan_campaigns_list. Example: 456
- `summary` (`string`, required): Summary of what the lead needs. Example: AC not cooling, wants a quote for a new unit.
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890
- `business_unit_id` (`integer`, optional): ID of the business unit. Get it from servicetitan_business_units_list. Example: 789
- `call_reason_id` (`integer`, optional): ID of the call reason. Required when follow_up_date is empty. Example: 12
- `customer_id` (`integer`, optional): ID of an existing customer for the lead. Example: 123456
- `follow_up_date` (`string`, optional): When to follow up, as an ISO 8601 date-time in UTC. Required when call_reason_id is empty. Example: 2026-12-01T15:00:00Z
- `job_type_id` (`integer`, optional): ID of the job type the lead is for. Get it from servicetitan_job_types_list. Example: 321
- `lead_city` (`string`, optional): Prospect's city. Example: Austin
- `lead_country` (`string`, optional): Prospect's country. Example: USA
- `lead_customer_name` (`string`, optional): Prospect's name, when the lead has no customer record yet. Example: John Doe
- `lead_email` (`string`, optional): Prospect's email address. Example: john@example.com
- `lead_phone` (`string`, optional): Prospect's phone number. Example: 5555559876
- `lead_state` (`string`, optional): Prospect's state. Example: TX
- `lead_street` (`string`, optional): Prospect's street address. Example: 456 Oak Ave
- `lead_zip` (`string`, optional): Prospect's zip or postal code. Example: 78702
- `location_id` (`integer`, optional): ID of an existing location for the lead. Example: 234567
- `priority` (`string`, optional): Lead priority: Low, Normal, High or Urgent. Example: High. One of: `Low`, `Normal`, `High`, `Urgent`.
- `tag_type_ids` (`array`, optional): IDs of tag types to put on the lead. Example: [101, 102]

Example input: `{"app_key":"<app_key>","campaign_id":456,"summary":"<summary>","tenant_id":"<tenant_id>"}`

### `servicetitan_job_cancel`

Cancel Job · Destructive

Cancel a ServiceTitan job with a cancel reason and memo.
Returns an empty response on success.
Get valid reason IDs from servicetitan_job_cancel_reasons_list first. Use servicetitan_job_update to change a job without canceling it.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `app_key` (`string`, required): App Key of your ServiceTitan developer app, sent as the ST-App-Key header on every call. Find it in the ServiceTitan Developer Portal (developer.servicetitan.io) under My Apps > your app > Keys > Application Key. It belongs to the same app whose Client ID and Client Secret this connection uses. Example: ak1.abcd1234efgh5678ijkl
- `job_id` (`string`, required): ID of the job. Example: 456789
- `memo` (`string`, required): Memo explaining the cancellation. Example: Customer fixed the issue themselves.
- `reason_id` (`integer`, required): ID of the job cancel reason. Get it from servicetitan_job_cancel_reasons_list. Example: 3
- `tenant_id` (`string`, required): Your ServiceTitan tenant ID (a number). An admin finds it in ServiceTitan under Settings > Integrations > API Application Access, next to the connected app. Example: 1234567890

Example input: `{"app_key":"<app_key>","job_id":"<job_id>","memo":"<memo>","reason_id":3,"tenant_id":"<tenant_id>"}`

## Related

Other CRM & Sales connectors ([all 174](/agentkit/connectors/?category=crm-sales)):

- [Salesforce](/agentkit/connectors/salesforce/): Scalekit connector, OAuth, 74 tools
- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Close](/agentkit/connectors/close/): Scalekit connector, OAuth, 103 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
