Jobber API Guide for Contractors

One-line verdict: The most open field-service platform in this directory — a real API, real alerts, and a native lead object most platforms do not have. Openness: 5 / 5 — rated 5 because Jobber offers a documented GraphQL API with OAuth sign-in and verified webhooks open to developers, with no paid-plan gate found in its documentation.

The connection that works

Rung 1 — Direct connection. Jobber’s API is GraphQL-only, which is a technical detail your builder handles; what matters to you is how access works. The developer owns the app, and each shop authorizes it with a secure OAuth sign-in — you approve access from your own account instead of handing over a password or a master key. That is the safest pattern in this directory.

Jobber also sends verified webhooks — instant alerts when something changes. Two honest quirks: the alerts carry only an ID, so the system has to look up the full record right after (normal, just a design step), and the receiving system must answer within one second. There are usage limits, too — a request allowance per five minutes plus a query-cost budget — so well-built automations keep their questions lean instead of pulling your whole database every few minutes.

For bridge apps, Jobber has a native Zapier connection with Quote Sent and Quote Approved triggers. That is the strongest verified estimate-follow-up path in this entire directory. On Make, only community-built apps were found, so we would not rest a critical workflow on that route.

Can automate

• Speed-to-Lead on real leads — Jobber has a native lead object called Requests, which is rare and valuable. A new Request is a clean, instant trigger for a text-back or call within minutes, while the homeowner is still thinking about the job.
• Quote follow-up — Quotes are verified read/write through the API, and the Zapier Quote Sent / Quote Approved triggers give estimate follow-up a dependable second path.
• Client, job, and quote updates — Clients, Requests, Jobs, and Quotes read/write are verified in the vendor’s documentation.
• Job write-back — Work created or updated by an automation can land back in Jobber, so your board stays the source of truth.
• Invoice visibility — Invoices can be read, so an automation can see what is owed and start a polite chase from our messaging layer.

Can’t automate

• Creating invoices or payments through the API — UNVERIFIED. Invoice and payment creation is UNVERIFIED in the documentation we checked. Until it is tested live, an invoice-chasing setup on Jobber should plan on reading balances and running the follow-up messages from our side — not creating invoices inside Jobber automatically.
• Make as a primary bridge — only community apps were found, not a native vendor app.
• Unlimited polling — the rate and query-cost limits mean “check everything constantly” is not an option; triggers have to do the heavy lifting.

Hidden gate: There is no paywall gate here — the gate is a verification gap. The one money-critical action, creating an invoice or a payment through the API, is UNVERIFIED. Any builder who quotes you fully automatic invoicing on Jobber without flagging that is quoting past the evidence.

Build fit — what this platform supports well

• Speed-to-Lead — the strongest fit. Requests were practically designed for it.
• Estimate Follow-Up — strong, through both the API and the verified Zapier quote triggers.
• Missed-Call / After-Hours Capture — works, with job and booking information written back into Jobber.
• Invoice Chase / AR — partial by design: read the balance in Jobber, run the chase on our comms layer, until invoice creation is verified.
• Review Engine — like every platform here, Jobber has no verified reviews API, so the review ask runs on our system triggered by a job-completion signal.

What this means for your shop

If you run Jobber, you are in the best starting position in this directory: leads, quotes, and jobs can all move automatically, and you approve access with a sign-in instead of sharing a master key. The one place to keep expectations straight is invoicing — the follow-up chase is buildable today, but automatic invoice creation stays flagged UNVERIFIED until someone proves it on a live account.