Which Home Service CRMs Actually Have Working APIs (2026 Field Report)

Short answer, as of August 2026: Markate integrations work today through its premium Zapier app — that's the path running in our production. Jobber has a public GraphQL developer API with a Technology Partner track and an App Marketplace; our integration is in active development. Housecall Pro has a REST API with OAuth 2.0 and an integrations directory; also in development on our side. ServiceTitan and FieldPulse are at the partner-intake stage for us — we've submitted, we haven't built, so we won't pretend to have a report. Details on each below.

How we know, and what this page is

We build an AI phone receptionist that turns callers into CRM leads, which means we integrate against these platforms for a living. This page reports what we've actually built against — auth models, integration paths, and behaviors we've verified in code. Where we haven't built yet, we say exactly that instead of paraphrasing someone's docs. We'll update this page as our integrations progress; the last-updated date above is real.

One thing this page is not: a review of any vendor's partner program or support. We're reporting what the APIs do.

Markate: does it have a working API?

The working path is Markate's premium Zapier app, and it works well — it's live in our production today. New callers become CRM leads through it reliably.

Worth knowing before you build: in our testing, the same credentials that power the Zapier app did not authenticate against direct REST calls. Whatever the reason, the practical answer for an integrator today is that Zapier is the supported, working path — plan your architecture around it rather than around direct API calls.

And to be clear, that's a legitimate path, not a lesser one. Zapier-based integrations are sometimes dismissed as duct tape; in production, a stable Zapier app beats a direct API you can't authenticate against every single time.

Jobber: does it have a working API?

Yes — a public GraphQL developer API, with a formal Technology Partner track and App Marketplace. Our integration is in active development.

Three concrete things an integrator should know, all from Jobber's developer documentation:

• It's GraphQL, not REST. Every request POSTs to a single endpoint (api.getjobber.com/api/graphql) with an OAuth 2.0 bearer token, and a X-JOBBER-GRAPHQL-VERSION header is required on each call.
• Rate limiting is query-cost based, not request-count based. Jobber uses a leaky-bucket point system per app/account pair — an expensive query spends more of your budget than a cheap one, and exceeding it returns a 429. If you're used to "N requests per minute" REST quotas, budget differently: one deeply-nested query can cost what dozens of small ones do.
• Webhooks are thin on purpose. A webhook delivers the topic, the account ID, and the item ID — not the object itself. Your handler queries back for the details. That's an extra round trip to design for, and it also means a missed webhook is recoverable by re-querying.

One more requirement worth planning for early: apps published in the App Marketplace must handle the APP_DISCONNECT webhook — the "a customer just disconnected your app" signal — cleanly.

Housecall Pro: does it have a working API?

Yes — a REST API with OAuth 2.0, and an integrations directory. Our integration is in active development. We'll expand this section with verified integration behaviors as our build progresses — same rule as everywhere on this page: we only write what we've run.

ServiceTitan and FieldPulse: what's the status?

We've submitted partner intake with both and haven't yet built against either API, so we have no firsthand report — and no secondhand one either. When we've built, we'll write it up here.

What does this mean if you're choosing a CRM?

• An API existing is not the same as an integration existing. Every platform above "has an API" in a press-release sense. What matters to you is whether the tool you're buying has a built, running integration with your CRM — ask your vendor which of these statuses applies, in exactly these terms: live in production, in development, or not started.
• Zapier is a real answer. If a vendor connects to your CRM through Zapier and it runs reliably, that's a working integration. The failure mode to avoid isn't Zapier — it's "we integrate with everything" marketing that turns out to mean a webhook and a prayer.
• If you're on Markate, integration is a today thing. If you're on Jobber or Housecall Pro, ask for timelines, not just intentions — ours is "in active development," and any honest vendor should be equally specific with you.

This is the field report behind the integration claims on our features page — the two say the same thing on purpose. If you want to see what the integrated flow does for a trade business day-to-day, the HVAC and plumbing pages walk through it.

Ready to stop missing calls?

See your AI receptionist in a 20-minute demo. Live in 48 hours.