Podium Is Missing From ServiceTitan’s Marketplace. What Contractors Need to Know

What we can verify

Key points for contractors

• Podium is not currently discoverable in ServiceTitan’s public marketplace.
• Podium still maintains a public ServiceTitan integration page with active-looking setup instructions and workflow descriptions.
• ServiceTitan now identifies Certified Apps and Customer-Built Apps as the two approved integration paths and prohibits third-party tunneling through customer app keys.
• The public record does not establish why Podium’s marketplace listing disappeared or whether every existing tenant connection is affected.
• Contractors should verify their tenant-specific status with both vendors before disconnecting, replacing, or rebuilding any workflow.

ServiceTitan’s marketplace describes itself as the place to browse ServiceTitan-approved integration and services partners. A current marketplace search does not return Podium, and a direct search for a Podium partner page does not surface a live listing.

That is different from Podium’s own public documentation. Podium continues to present ServiceTitan as a supported integration and instructs users to select Podium from ServiceTitan’s API Application Access area. The same page includes a fallback instruction: if Podium is unavailable, the customer should contact Podium support and provide a ServiceTitan tenant ID.

This creates a clear public-information mismatch. ServiceTitan’s marketplace no longer presents Podium as a discoverable partner, while Podium continues to describe the integration as connectable. Contractors may reasonably describe that as Podium being “dropped” from the marketplace, but the public evidence does not establish who initiated the change, why it happened, or whether existing installations are being discontinued.

The integration-status timeline

A marketplace removal can matter commercially and operationally without automatically meaning that an API connection has been switched off.

ServiceTitan’s certification materials separate marketplace-certified applications from customer-built applications. Its 2025 marketplace relaunch announcement also said that an existing partner unable or unwilling to complete certification could be removed from the marketplace and considered a custom integration. That policy provides important context, but it does not identify Podium’s specific circumstances.

It would be irresponsible to infer that Podium failed a security review, declined commercial terms, was replaced by another vendor, or had all access revoked without an attributable statement or tenant-level evidence. None of those explanations has been publicly confirmed in the materials reviewed for this report.

ServiceTitan has been tightening the rules around third-party software access. Its current guidance presents two approved paths.

A ServiceTitan Certified App is developed and managed by a third party, reviewed by ServiceTitan, and listed in the marketplace. A Customer-Built App is created, hosted, controlled, and maintained by the ServiceTitan customer using that customer’s own app keys.

ServiceTitan separately prohibits “tunneling,” where a third party uses a customer’s app key to access the account. The company says customers may be asked to disconnect an integration that violates that rule.

For contractors, the practical question is no longer simply whether two products can exchange data. It is whether the connection is certified, customer-built and customer-controlled, legacy, or unsupported—and who is responsible when it breaks.

ServiceTitan’s current approved integration paths

Eric Rea is Podium’s co-founder and CEO. Ara Mahdessian is ServiceTitan’s co-founder and CEO. Their companies serve overlapping home-service customers, and this integration status touches workflows that can sit directly between marketing spend, customer communication, dispatch activity, reviews, payments, and booked revenue.

TradeVulcan Dispatch did not locate a public statement from Rea, Mahdessian, Podium, or ServiceTitan explaining why Podium is absent from the current ServiceTitan marketplace. We also found no public transition date, universal shutdown notice, or official migration bulletin covering all shared customers.

That silence is important. It means contractors should not treat marketplace visibility, vendor sales messaging, or an old setup screen as a substitute for written confirmation about their own tenant.

Podium’s current integration page says the connection can monitor ServiceTitan job statuses, send appointment and dispatch updates, request reviews, import contacts, synchronize calls and conversations, and write certain payment, lead, and conversation data back to ServiceTitan.

The existence of those instructions does not confirm that every new customer can activate the same connection today. Conversely, Podium’s absence from the public marketplace does not prove that every existing connection has stopped.

The most likely contractor experience is account-specific: one tenant may have a functioning legacy connection, another may see Podium unavailable in ServiceTitan, and another may be operating through a different approved or customer-controlled path. That is an inference from the conflicting public materials—not a company-confirmed transition policy.

Workflows that should be tested before any migration

Operator checklist

• Ask Podium, in writing, whether your current ServiceTitan connection is certified, legacy, customer-built, or supported through another approved arrangement.
• Ask your ServiceTitan Customer Success Manager or Technical Support how Podium is classified in your specific tenant and whether any action or deadline applies.
• Inventory every workflow that depends on the connection, including contacts, appointments, dispatch texts, review requests, payments, leads, notes, conversations, calls, and AI booking.
• Record the current owner, credentials, phone numbers, consent language, triggers, mappings, filters, business units, postal codes, and fallback routing.
• Run controlled tests using safe records and document what enters ServiceTitan, what leaves it, what writes back, and what fails.
• Export configuration and reporting data before making changes so the business retains an operational record.
• Do not disconnect the current stack until a replacement has passed end-to-end testing and the team knows how to reverse the change.
• Require the replacement vendor to document its ServiceTitan access model, support owner, failure handling, data retention, security controls, and migration plan.

ServiceTitan’s marketplace is becoming a stronger governance layer, not merely a directory. Certification, annual recertification, commercial participation, user-experience expectations, and approved access models now shape which third-party products are presented inside the ecosystem.

The marketplace still includes products with capabilities that overlap parts of Podium’s offering. Birdeye, for example, currently appears with review, reputation, text, email, live chat, social, survey, and customer-experience capabilities. That does not establish that Birdeye replaced Podium, and contractors should not assume one vendor is a drop-in replacement for another.

The larger lesson is that a contractor’s tech stack can inherit platform risk from every external dependency. The right migration decision is not simply “Which app has the same feature list?” It is “Which app has an approved and durable access path, preserves the data we need, reproduces the workflows that make money, and gives us a tested fallback when a connection changes?”

Update status

Disclosure

Methodology

TradeVulcan Dispatch reviewed ServiceTitan’s current public marketplace, ServiceTitan’s published certification and integration-path materials, Podium’s current ServiceTitan integration page, official company leadership pages, and a current overlapping marketplace listing. We found no public company statement explaining Podium’s marketplace absence. Marketplace availability and tenant configuration can change, so readers should verify account-specific status directly with both vendors.