How We're Approaching Integration Partnerships in 2025

RE: How We're Approaching Integration Partnerships in 2025

Omar Hassan — Sat, 07 Mar 2026 08:44:00 GMT

From a governance perspective, the 12-month deprecation commitment is welcome. However, it is worth noting that the phrase "breaking API changes" requires precise definition. Does this include:

Removal of fields from response payloads (i.e., additive-only guarantees)?
Changes to enum value sets (e.g., job.status gaining new states)?
Modifications to webhook delivery ordering or retry semantics?

The RFC should reference specific sections of the RFC 7807 problem details specification if you're adopting standard error formats, which would assist in automated client adaptation.

RE: How We're Approaching Integration Partnerships in 2025

Carlos Vega — Fri, 06 Mar 2026 09:15:00 GMT

Can you share the current rate limit headers? Last I checked X-RateLimit-Remaining wasn't consistently returned on 200s.

RE: How We're Approaching Integration Partnerships in 2025

Devon Marsh — Thu, 05 Mar 2026 14:22:00 GMT

Heads up — the partner portal link in step 3 404s if you're not already logged into the dev sandbox. Worth noting since I just sent three people there and they all got confused.

Also, any rough timeline on the ServiceTitan migration tool? Have a client sitting on a stalled project waiting for a path off their old setup.