How We're Approaching Integration Partnerships in 2025

Hey everyone — wanted to share where our heads are at with integrations this year, since I've been getting a lot of DMs and questions in the dev Slack about what's changing.

The short version: we're being more intentional. The longer version: well, keep reading.

From "build anything" to "build what matters"

Last year we shipped 14 new integrations. Some of them — QuickBooks Online, the Salesforce connector — are getting heavy use. Others... honestly, I forget they exist until someone pings me about a bug. That's not great for anyone.

So in 2025 we're moving to a partner-tier model. Three buckets:

• Tier 1: Native integrations — We build and maintain these. Deep feature parity, dedicated QA, docs that I actually review. Think QuickBooks, Salesforce, and the upcoming ServiceTitan migration tool (more on that soon).
• Tier 2: Verified partners — Built by third parties, but we've done code review, security audit, and committed to API stability. These get a badge in our marketplace and first access to new webhook events.
• Tier 3: Community integrations — Everything else. Still valid, still supported via our public API, but you're working with the standard rate limits and we can't guarantee backwards compatibility on beta endpoints.

What this means if you're building on our API

If you're maintaining an integration — or planning one — the path to Tier 2 is basically:

1. Use API v2.1 or later. v1 is entering maintenance mode and honestly, yeah, this one tripped me up too when I first looked at it. The pagination alone...
2. Implement webhook verification properly. We're starting to reject apps that don't validate signatures. (API v2.1 webhook improvements make this way easier, btw.)
3. Handle rate limits gracefully. 429 responses include a Retry-After header — use it. We've seen too many integrations that just hammer the endpoint until they get banned.

There's a full checklist in the partner portal. If you don't have access yet, email me directly.

The integrations we're actively seeking

Not gonna lie, we also have a shopping list. If you're at a company in these spaces — or you know someone — we want to talk:

• Fleet/telematics (GPS + vehicle diagnostics)
• Specialty equipment rental platforms
• Commercial HVAC supply chain management
• State-level licensing and compliance databases

The goal is fewer, deeper integrations rather than surface-level connections to everything. I'd rather have one partner that lets us sync parts inventory in real-time than five that just push basic contact records.

A note on breaking changes

With the tier system comes a real commitment: Tier 1 and Tier 2 integrations get 12 months notice on any breaking API changes. We're documenting this in a public RFC process starting next month. No more finding out about deprecated endpoints from a changelog entry buried three pages deep.

That's the gist. Happy to answer questions in the comments — especially if you're hitting edge cases with the current webhook event payloads. I know the job.updated event in particular has some... quirks.