---
title: "ServiceTitan Integrations in 2026: What Certification Changed"
url: "https://fieldcamp.ai/blog/servicetitan-integrations/"
date: "2026-08-17T10:00:00+00:00"
modified: "2026-09-11T13:57:40+00:00"
type: "Article"
resource: "https://fieldcamp.ai/blog/servicetitan-integrations/"
timestamp: "2026-09-11T13:57:40+00:00"
author:
  name: "Komal Gurbani"
categories:
  - "Field Service Software"
word_count: 4214
reading_time: "22 min read"
summary: "TL;DR"
description: "ServiceTitan integrations now split into certified apps and custom integrations. What certification requires, the AI clause nobody cites, and how to audit yo..."
keywords: "servicetitan integrations, servicetitan marketplace, servicetitan api, servicetitan partners, servicetitan app marketplace, servicetitan certified apps, servicetitan custom integration, servicetitan ai, Field Service Software"
language: "en"
schema_type: "Article"
---

# ServiceTitan Integrations in 2026: What Certification Changed

_Published: August 17, 2026_  
_Author: Komal Gurbani_  

![ServiceTitan integrations split into certified apps and custom integrations](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/servicetitan-integrations-feature-1408x768-1-1024x559.png)

**TL;DR**

ServiceTitan integrations now fall into two tiers. **Certified apps** have passed a multi-stage review and stay in the App Marketplace. **Custom integrations** are everything else — unvetted, outside ServiceTitan’s support scope, and, per ServiceTitan’s own documentation, requiring The Works subscription package to build or use. As of ServiceTitan’s June 2026 update, 14 partners were certified. Certification criteria include security and performance, and also revenue share. Separately, ServiceTitan’s API Terms of Use, last updated 15 April 2026, place hard limits on partner applications that use AI. If an app in your stack isn’t certified, its status is a commercial decision between two companies you aren’t party to.

## What are ServiceTitan integrations?

ServiceTitan integrations are third-party applications that connect to the ServiceTitan platform through its API — accounting tools, phone and messaging systems, e-commerce, payroll, marketing platforms, and AI assistants. Since September 2025, ServiceTitan has run an App Certification programme that sorts these into two categories. Certified apps are listed in the ServiceTitan App Marketplace and are supported. Everything else is classified as a custom integration: not vetted by ServiceTitan, maintained entirely by the third party, not available for wide distribution, and outside ServiceTitan’s support scope. ServiceTitan states that building or using a custom integration requires The Works subscription package, which provides access to all customer APIs. For contractors, the practical consequence is that an integration’s continued existence now depends on a commercial arrangement between two vendors — not on whether the software still works. That’s a different risk from the one most operations price when they compare [field service management platforms](https://fieldcamp.ai/alternatives/servicetitan/), and it’s the one this guide is about.

Most contractors discover how their integrations work on the day one stops working.

Until then, the connection between your field service platform and your phone system, your accounting software, or your [AI answering service](https://fieldcamp.ai/ai-receptionist/) is invisible infrastructure. It syncs, it fires, nobody thinks about it. It shows up on no line item and in no risk register. And then an email arrives giving you a few weeks to replace something your CSRs use forty times a day, in a month when your dispatch board is already full.

That’s not hypothetical. In August 2026 it happened to roughly a thousand contractors at once when [ServiceTitan ended its Podium integration](https://fieldcamp.ai/blog/servicetitan-podium-integration-ending/) on about four weeks’ notice, in peak season. We covered that story in full separately. This guide is about the policy underneath it — the one that governs every other connection in your stack too.

> “I pay for 200 features I don’t use and the 3 things I actually need don’t work the way my business runs.”
>
> — Field service operator (ex-ServiceTitan)

That’s the frustration most operators can name. The one they usually can’t name is structural: the three things that actually matter are often the three that depend on somebody else’s contract.

What follows covers what changed in the ServiceTitan App Marketplace, what certification requires in ServiceTitan’s own published words, the API clause governing AI vendors that almost nobody has read, and how to audit your own stack before a notice email does it for you. It’s written for ops directors and owners running 20 to 100 technicians — the size where an integration failure costs real revenue and there’s no in-house developer to absorb it.

## What the ServiceTitan App Marketplace is now

The **ServiceTitan App Marketplace** is ServiceTitan’s directory of third-party applications that connect to its platform. That much hasn’t changed. What changed is what it takes to stay in it.

In [September 2025](https://www.servicetitan.com/blog/app-marketplace-relaunch), ServiceTitan announced App Certification, describing it as “the cornerstone of this investment.” The [first certified apps were announced in February 2026](https://www.servicetitan.com/blog/app-marketplace-certified-apps). By ServiceTitan’s [June 2026 update](https://www.servicetitan.com/blog/app-marketplace-update), the company stated it had “already certified 14 partners across accounting, payroll, point-of-sale, e-commerce, CSR, and more, with additional certifications underway.”

Fourteen. That number is worth sitting with, because the ServiceTitan App Marketplace has historically listed far more than fourteen apps. Everything not on the certified list now falls into a second category with materially different terms. If you’re mid-way through evaluating the platform itself rather than one connection, our [ServiceTitan review](https://fieldcamp.ai/reviews/servicetitan/) covers pricing and fit alongside this.

## Certified apps vs custom integrations: the split that matters

This is the single structural change contractors need to understand. ServiceTitan now sorts partner software into two tiers, and they are not two flavours of the same thing.

|  | **Certified app** | **Custom integration** |
|---|---|---|
| Listed in App Marketplace | Yes | No |
| Vetted by ServiceTitan | Yes | No |
| Covered by ServiceTitan support | Yes | No — “fall outside ServiceTitan’s support scope” |
| Available for wide distribution | Yes | No |
| Maintenance responsibility | Shared with certified partner | “Require development and maintenance from the third party” |
| Subscription requirement | Your existing plan | The Works, per ServiceTitan’s documentation |
| Commercial terms | Revenue share or connection fees | N/A — no marketplace relationship |

![ServiceTitan certified apps versus custom integrations compared across marketplace listing, support, maintenance and subscription](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/st-certified-vs-custom.png)The quoted phrases come from ServiceTitan’s own September 2025 announcement. The same post states plainly: “Partners who decline to participate or can’t meet certification standards will be removed from the marketplace and considered custom integrations.”

That sentence is the whole story in one line. Removal from the marketplace is not the end state — reclassification is. And reclassification carries a subscription implication most contractors have never been walked through.

Worth noting the contrast: any platform’s connector list is a claim, and the honest thing is to publish it where customers can check. Ours sits on the [integrations page](https://fieldcamp.ai/integrations/) with the [full connections documentation](https://docs.fieldcamp.ai/integrations/apps-and-integrations-all-fieldcamp-connections) behind it, for exactly the reason this section describes.

The constraint behind every item below

What you do not control in your own stack

 1. Custom fields mean a custom integrationConfiguring your own data becomes a subscription decision.2. Non-certified connectors sit outside supportIf the connection breaks, it is between you and the other vendor.3. Your AI layer is permissioned by somebody else's agreementYour AI layer sits under a contract you did not sign.4. Answering your own questions needs a connectorReporting you cannot reshape pushes you to a BI tool.5. A connector ending is not your decisionPodium is the worked example, and nobody got notice.
The pattern: **every workaround for a customisation limit becomes an integration**, and every integration is a dependency on somebody else's agreement.

## What ServiceTitan certification actually requires

ServiceTitan publishes its criteria. Here they are in the company’s own words, from the [June 2026 App Marketplace update](https://www.servicetitan.com/blog/app-marketplace-update):

![ServiceTitan's five certification criteria — security, performance, predictability, data transparency and revenue share](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/st-certification-requires.png)- **Security** — “Apps must be secure. They cannot unintentionally or nefariously siphon off sensitive data including (but not limited to): end-customer data, payment details, employee records, business financials, etc.”
- **Performance** — “Apps must be performant. They cannot generate excessive or unnecessary load on our infrastructure.”
- **Predictability** — “An app’s scope must be clear and reasonably defined.”
- **Data transparency** — “If partners are accessing data through the ServiceTitan API, they must also write back data to ServiceTitan.”
- **Revenue share** — “Partners must share in these costs through reasonable economic arrangements that are comparable to other industries.”

Four of those five are ordinary platform hygiene. Any serious software company would want them, and a marketplace that certified nothing would eventually fail the contractors trusting it. If your accounting connector is quietly hammering the API or holding payment details it shouldn’t, you want somebody checking.

The fifth is a commercial term sitting in a list of safety ones. ServiceTitan’s [App Marketplace Program Guide](https://www.servicetitan.com/legal/app-marketplace-program-guide) spells it out further: revenue share is “a percentage of partner net revenue derived from its application or a specified minimum fee, whichever is greater,” and “partners must maintain current payment status to preserve program benefits and certified status.”

Certified status is contingent on paying. That’s not a criticism — running a certification programme costs money and it has to come from somewhere. But it means that when a contractor is told an app “didn’t meet Marketplace standards,” that phrase covers both a failed security review and a failed negotiation, and from outside there’s no way to tell which. If that changes how you read the platform’s total cost, [ServiceTitan alternatives](https://fieldcamp.ai/alternatives/servicetitan/) is the wider comparison, and for mid-market shortlists specifically [Jobber vs ServiceTitan](https://fieldcamp.ai/jobber-vs-servicetitan/) and [Housecall Pro vs ServiceTitan](https://fieldcamp.ai/housecall-pro-vs-servicetitan/) cover the two most common ones.

One thing worth checking today

#### ServiceTitan certified 14 apps in June. Is yours one?

That is ServiceTitan's own figure from its June 2026 Marketplace update, with more certifications said to be in progress. Certification decides who supports the connection when it breaks, and the published criteria include revenue share alongside security. Tell us which connector you cannot afford to lose.



## The AI clause nobody is citing

There’s a third possibility, and it’s in writing.

ServiceTitan’s [API Terms of Use](https://www.servicetitan.com/legal/api-terms), last updated 15 April 2026, place specific restrictions on partner applications that use artificial intelligence. This is the least-discussed document in the entire ServiceTitan partner conversation, and for anyone running an AI vendor alongside ServiceTitan it’s the most consequential.

Among the prohibited uses, a partner may not:

> permit any bots, robotic process automation (RPA), AI (whether agentic or otherwise), or similar automated technology (“AI System”) to independently determine which API endpoints to access, what Content to request or modify, or what actions to take through the APIs.

The terms then bound what an AI System may do:

> Any API calls made by or through an AI System must be limited to predefined operations within your Application’s Certified Scope and must not allow the AI System to autonomously expand, modify, or deviate from such predefined operations.

Disclosure is mandatory and approval is discretionary:

> You must disclose to ServiceTitan whether your Application incorporates or relies upon any AI System at the time of registration and promptly upon any subsequent integration of an AI System.

> ServiceTitan reserves the right to impose additional conditions, restrictions, or Certification Requirements on any Application that incorporates an AI System, including requiring human authorization for write operations, if ServiceTitan elects to permit such use of an AI System at all.

Using an AI System with the APIs without that disclosure and approval “shall constitute a material breach of these Terms.” Separately, partners may not “use the APIs to collect data for creating training datasets for AI purposes.”

![ServiceTitan's four AI integration restrictions from its API Terms of Use dated 15 April 2026](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/st-ai-clause.png)**Certified Scope** is the operative term. ServiceTitan defines it as the “defined functionality, API scopes, API endpoints, and/or data fields” attached to an application’s certification, and states that an app “shall at no time exceed such Certified Scope.”

Read the discretionary clause once more: *“if ServiceTitan elects to permit such use of an AI System at all.”*

An agentic product’s defining behaviour is deciding what to do next. A clause requiring every API call to stay inside predefined operations, with write operations potentially gated behind human authorisation and permission reserved entirely at ServiceTitan’s discretion, is a ceiling on what any AI-first vendor can build on top of ServiceTitan. It was published four months before the partner news that made contractors start asking these questions.

This is not an accusation. ServiceTitan has legitimate reasons to want AI traffic bounded — an autonomous agent roaming an API it doesn’t understand is a genuine security and load problem, and the security and performance criteria above exist for good reason. The point is narrower and it matters to your planning: when you’re told an integration “didn’t meet Marketplace standards,” there are now at least three distinct things that sentence can mean, and only one of them is about software quality.

| What “didn’t meet standards” could mean | Is it about the software? |
|---|---|
| Failed security or performance review | Yes |
| Declined or failed to agree revenue share | No — commercial |
| Could not operate inside AI Certified Scope limits | Partly — architectural |

If you’re evaluating **AI assistants for ServiceTitan integration**, that third row is the question to ask the vendor directly, in writing, before you sign. It’s also worth understanding how an AI layer connects to your system of record in the first place — our [documentation on connecting the AI Dispatcher](https://docs.fieldcamp.ai/ai-dispatcher/connecting-fieldcamp-to-dispatcher) shows the shape of that plumbing, and the [AI Dispatcher](https://fieldcamp.ai/ai-dispatcher/) page explains why we built it to sit alongside an existing platform rather than replace it.

## The worked example: what happened with Podium

In August 2026, ServiceTitan ended its integration with Podium — a nine-year partnership covering roughly a thousand shared customers — on approximately four weeks’ notice, in peak season. Podium was subsequently delisted from both companies’ directories.

![The ServiceTitan Podium integration ending: nine-year partnership, 1,000 shared customers, four weeks' notice](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/st-podium-example.png)The full account is in our separate write-up of [the ServiceTitan Podium integration ending](https://fieldcamp.ai/blog/servicetitan-podium-integration-ending/), including what breaks, the four realistic options, and the subscription detail buried in the announcement. If you’re evaluating replacements, we’ve also published a breakdown of [Podium alternatives for contractors](https://fieldcamp.ai/alternatives/podium/) and a straight [Podium review](https://fieldcamp.ai/reviews/podium/).

The reason it belongs in a guide about integrations generally, rather than as a one-off news item, is the mechanism. Nothing broke. The software still worked on the morning of the announcement and on the morning after it. What changed was a commercial relationship between two companies, and roughly a thousand businesses absorbed the entire cost of that change without having been party to it, without having seen its terms, and without any ability to observe it deteriorating.

That mechanism is not specific to Podium, and it is not specific to ServiceTitan. It’s how platform marketplaces work. Which is exactly why it belongs on your risk list rather than in your news feed.

## The ServiceTitan integrations contractors actually ask about

Certification policy is the structural story. Day to day, most operators are asking narrower questions. Here’s where the common ones sit.

| Integration category | Typical tools | Notes under the current programme |
|---|---|---|
| Accounting | QuickBooks Online, QuickBooks Desktop, Sage Intacct, NetSuite | Accounting is explicitly named among the 14 certified categories |
| Payroll | Payroll and time platforms | Named among certified categories |
| Point of sale / e-commerce | Consumer-facing purchase flows | Named among certified categories |
| CSR and communications | Phone, messaging, webchat, answering services | Named among certified categories; also the most contested area |
| Automation middleware | Zapier and similar connectors | Middleware sits closer to the custom-integration definition — confirm before relying on it |
| AI assistants | AI CSRs, voice agents, review and follow-up bots | Subject to the AI System clauses above |
| Customer and homeowner portals | Customer-facing status and booking portals | Confirm certification status individually |

Two practical notes. First, **ServiceTitan API documentation** is publicly available, so a technically capable partner can always build against it — but “the API allows it” and “your subscription permits it, supported” are now different statements. If you want a sense of what a two-way sync actually requires before you scope one, our [API reference](https://docs.fieldcamp.ai/api-reference) and [webhook documentation](https://docs.fieldcamp.ai/api-reference/webhooks) show the event plumbing involved. Second, category presence on the certified list does not mean your specific vendor is certified. Fourteen partners across six-plus categories means most named tools in any given category are not on that list.

The category most operators underestimate is the customer record itself. When a sync breaks, the drift starts on day one and nobody notices for weeks — which is why we keep the [customer record](https://fieldcamp.ai/crm/) and the job on the same object rather than syncing them between systems.

## How to audit your ServiceTitan integrations before a notice email does

This takes about ninety minutes and it’s the highest-value hour of admin you’ll do this quarter.

![Seven-step audit for ServiceTitan integrations covering certification status, subscription and AI disclosure questions](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/st-audit-steps.png)**1. List every connection, not every app.** Open ServiceTitan and write down every third-party system that reads from or writes to it. Include the ones nobody talks about — the accounting sync, the payroll export, the review request bot, the call recording tool. Aim for completeness over precision.

**2. Mark what each one actually does for revenue.** Next to each, write the business outcome it produces. “On-my-way texts.” “Invoice sync.” “After-hours booking.” If you can’t name an outcome, you’ve found a subscription to cancel regardless of certification status.

**3. Check certification status individually.** Don’t infer it from the category, and don’t infer it from the vendor’s marketing page. Ask ServiceTitan directly which of your connections are certified apps and which are custom integrations.

**4. Ask the subscription question in writing.** For anything that comes back as a custom integration, ask: does keeping this connection require a move to The Works, and what would that change on our invoice? This is the single most expensive detail in the entire policy and it does not appear in any announcement email.

**5. Ask the AI question in writing.** For any vendor using AI — and in 2026 that’s most CSR and communications tools — ask whether their AI functionality is disclosed and approved under ServiceTitan’s API terms, and whether it operates inside a Certified Scope.

**6. Rank by replacement cost, not by monthly fee.** A $200/month tool holding your phone numbers and message history is a bigger exposure than a $2,000/month tool you could swap in an afternoon. Number porting, CSR retraining, rebuilt automations and **A2P 10DLC re-registration** are the real costs, and none of them appear on the invoice. That last one catches people out — our [A2P 10DLC and toll-free verification guide](https://docs.fieldcamp.ai/integrations/a2p-10dlc-and-toll-free-verification) explains what carriers actually ask for, and it applies whichever platform you land on.

**7. Write down what you’d do if each one ended in four weeks.** One line each. That document is your actual continuity plan, and it takes twenty minutes.

Then put these five questions to your CSM by email, because verbal answers from a customer success manager are given in good faith and are not durable: which of our integrations are certified and which are custom; does each custom one require The Works and what’s the invoice impact; what notice period applies if a certified app’s status changes; are our AI vendors disclosed and approved under the API terms; and if an integration is discontinued mid-contract, what accommodation exists for customers who bought the connected product because of it. That last one rarely gets a satisfying answer. Ask anyway — the answer tells you how the relationship behaves under stress, which is the only time it matters.

## The cost nobody prices: integration risk

Here’s the thing worth taking away, whatever platform you’re on.

When you buy field service software, you price the licence. When you buy a connected tool, you price that licence too. What almost nobody prices is the connection between them — which is not a feature you bought, but a treaty between two companies whose commercial interests were aligned on the day you signed and may not be next year.

That risk is highest exactly where the two companies are closest to competing. A phone-and-messaging vendor sitting on your customer conversations, an AI CSR answering your calls, a portal owning your homeowner relationship — these are the connections most useful to you and most strategically uncomfortable for a platform that also sells communications, AI and portals. Integration risk concentrates where value concentrates.

![Integration risk concentrates where a connected vendor competes with the platform on communications, AI and portals](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/st-integration-risk.png)> “The software handles invoicing. But which tech goes where — that is still manual.”
>
> — Field service ops lead

That quote is about dispatch, but it describes the same shape of problem. The parts of your operation that matter most are the parts most likely to be stitched together across vendors — and stitching is where things tear.

You can conclude that ServiceTitan is entirely within its rights here, because it is, and still conclude that depending on an integration you don’t control is a risk worth pricing. Most operations have never priced it, because until the email arrives it costs nothing.

## Where this leaves your architecture

There are two honest ways to reduce integration risk, and only one of them gets discussed.

The discussed one is redundancy: pick certified vendors, ask the questions above, keep a documented fallback for each connection. That’s sound and you should do it regardless.

The undiscussed one is scope: the connections that can’t be revoked are the ones that don’t exist, because the capability is native to the platform you’re already running. If customer messaging, booking and the customer record live in the same product as jobs and dispatch, there’s no certification to maintain and no third party who can be removed from the arrangement.

That’s the model FieldCamp is built on, and we’d rather state the bias than pretend this section is neutral. We flipped the model — instead of shipping a fixed platform and asking operations to adapt to it, [the data model is customisable](https://fieldcamp.ai/customizable-data-model/) to how a business actually runs, with communication built in rather than bolted on. Practically, that means an [AI receptionist](https://fieldcamp.ai/ai-receptionist/) answering the calls your CSRs can’t get to, [online booking](https://fieldcamp.ai/online-booking/) on your own site, and messages landing in a shared inbox against the job — the [inbox documentation](https://docs.fieldcamp.ai/inbox/inbox-overview) covers how that works. Automations are built in the same place, through the [workflow builder](https://fieldcamp.ai/workflow-builder/), so a broken connector can’t silently stop them firing.

And the honest limits, because a guide about vendor trust shouldn’t hand-wave its own: FieldCamp does not do automated review generation — no auto-fired review invitations on job completion, no review aggregation or response. If reputation management is the main job you’re hiring a tool for, that stays a separate purchase. FieldCamp also has no offline mode. And we run integrations of our own, which means everything above applies to us too. If you run [HVAC](https://fieldcamp.ai/hvac-software/) or [plumbing](https://fieldcamp.ai/plumbing-software/) operations, those pages carry the trade-specific detail.

Ready to find out which connections you can actually lose?

If you’re auditing your stack after a partner change, we’ll walk through your setup with you — including where staying exactly where you are is the right call this season. No migration pitch if migration isn’t the answer.

[Book a Demo](https://calendly.com/jeel-fieldcamp/30min)*FieldCamp is AI-native [field service management software](https://fieldcamp.ai/) with customer communication built in — two-way texting, webchat, calls and a shared team inbox in the same system as jobs and dispatch. We compete with ServiceTitan, which is why we’ve tried to make this guide useful whether or not you ever talk to us. [See how pricing works](https://fieldcamp.ai/pricing/).*

## Frequently asked questions

**How many ServiceTitan integrations are certified?**

As of ServiceTitan’s June 2026 App Marketplace update, the company stated it had certified 14 partners across accounting, payroll, point-of-sale, e-commerce, CSR “and more,” with additional certifications underway. That number changes as the programme progresses, so confirm current status with ServiceTitan rather than relying on any published figure, including this one.

**What is a ServiceTitan custom integration?**

A custom integration is any connection to ServiceTitan that isn’t a certified app. Per ServiceTitan’s own documentation, custom integrations “aren’t vetted by ServiceTitan, require development and maintenance from the third party, aren’t available for wide distribution, and fall outside ServiceTitan’s support scope.” ServiceTitan also states that building or using one requires The Works subscription package, which provides access to all customer APIs.

**Does a non-certified integration require The Works subscription?**

ServiceTitan’s September 2025 App Marketplace post states that “to build or use a custom integration, customers need ‘The Works’ subscription package.” Since partners who decline or fail certification “will be removed from the marketplace and considered custom integrations,” the two statements read together imply a subscription requirement. Because this is the most expensive detail in the policy, get your specific situation confirmed by your CSM in writing rather than relying on inference.

**How do I get data from the ServiceTitan API?**

ServiceTitan publishes API documentation and a developer portal, and technically capable teams build against it directly. But the API Terms of Use govern what you may do with that access, including restrictions on AI systems, least-privilege scope requirements, and a rule that an application must never exceed its Certified Scope. Access and permission are separate questions — confirm both before you scope any build.

**How do I find my API key in ServiceTitan?**

API credentials are issued through ServiceTitan’s developer portal rather than the main application settings, and access depends on your subscription package — ServiceTitan states that using customer APIs for a custom integration requires The Works. If you can’t locate credentials, the subscription tier is the first thing to check with your CSM, not the interface.

**What are ServiceTitan’s rules for AI integrations?**

ServiceTitan’s API Terms of Use, last updated 15 April 2026, prohibit letting an AI system independently determine which endpoints to access or what actions to take. API calls made through an AI system must stay inside predefined operations within the application’s Certified Scope. Any AI use must be disclosed at registration, undisclosed use is treated as a material breach, and ServiceTitan reserves the right to impose extra conditions “if ServiceTitan elects to permit such use of an AI System at all.”

**Why did ServiceTitan end its Podium integration?**

ServiceTitan’s public statement was that the integration no longer met its Marketplace standards, and that it “tried to bring this partner into our certified program and opted not to move forward with their own certification” — a sentence that can be read as either party having declined. Podium’s CEO said his team was blindsided and had been trying to get a meeting for months. Both accounts are public and they don’t reconcile. Our [full write-up of the ServiceTitan Podium integration ending](https://fieldcamp.ai/blog/servicetitan-podium-integration-ending/) has the sourcing.

**How do I check whether my ServiceTitan integration is certified?**

Ask ServiceTitan directly, by email, and ask about your specific vendor rather than its category. Vendor marketing pages and marketplace listings can lag behind status changes, and category presence on the certified list does not mean every tool in that category is certified. Get the answer in writing so it’s durable if the status later changes.

**Does QuickBooks integrate with ServiceTitan?**

Accounting is one of the categories ServiceTitan names among its certified partners, and QuickBooks integration is among the most-searched ServiceTitan connections. As with any integration under the current programme, confirm the certification status of the specific connector you’re using, since accounting syncs are the ones operations notice last and miss most.

**What happens to my data if an integration ends?**

The integration ending is not the same as the connected product ending. Your data generally stays with whichever vendor holds it — phone numbers, message history and review profiles live with the communications provider, not with the connection. What stops is the sync and any automation keyed to it. Export from both systems while both accounts are fully active, before you make any decision.


---

_View the original post at: [https://fieldcamp.ai/blog/servicetitan-integrations/](https://fieldcamp.ai/blog/servicetitan-integrations/)_  
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1.1_  
_Generated: 2026-09-11 13:57:40 UTC_