What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jobber/Jobber API
Jobber API

The Jobber API: What a Real Build Involves

Jobber's API is GraphQL, reached through an OAuth app you create in Jobber's Developer Center. It covers clients, properties, quotes, jobs, visits and invoices, with webhooks for changes. Here's what you need to know before the first query, and the part most people get wrong: whether Jobber has to approve your app.

The Jobber API in four lines

One GraphQL endpoint: requests POST to https://api.getjobber.com/api/graphql, and one query can pull a client with their jobs and invoices together.

OAuth app: create it in the Developer Center, choose its scopes there, and have the Jobber account owner connect it.

Version header: every request sends X-JOBBER-GRAPHQL-VERSION with a dated API version. Pin one and plan to move up before it's retired.

Review only for the Marketplace: an app that stays in Draft for your own company doesn't need review, as long as it connects to no more than five paying Jobber accounts.

A private Jobber integration or a Marketplace app

Stays in Draft

Built for one company

  • Connects your own Jobber account, or a handful of related ones, to your other systems.
  • No review meeting, no listing, no gallery images.
  • API access is blocked if a Draft app connects to more than five paying accounts.
Goes through review

Listed for every Jobber customer

  • Request Review from Manage Apps, with two-factor authentication turned on first.
  • Jobber's App Review team meets you to check the user flow and the listing.
  • Has to handle disconnects cleanly, since customers can remove it at any time.

If the goal is your own business running better, stay in Draft. Review is for software you plan to sell to other Jobber users.

Settle these before writing a Jobber query

Each one changes the design, and each one is cheaper to answer on paper than in code.

  • What has to happen the moment something changes in Jobber, and what can wait until tonight?

    Real-time work runs off webhooks. Everything else can be a scheduled pass, which is simpler and easier to rerun.

  • Do records from before the integration need to come across?

    Webhooks only fire for new changes. Two years of past jobs or invoices means a separate backfill that pages through the API within its cost limits.

  • When Jobber and the other system disagree, which one wins?

    Without a rule, a two-way sync overwrites good data with stale data. Decide it per field: phone numbers from Jobber, credit terms from accounting.

  • Whose Jobber login connects the app?

    The connection runs under that account. If it belongs to someone who leaves, the integration stops when their access does.

  • Who moves the API version forward?

    Versions are dated and supported for a limited time. Someone has to test the next one before the pinned one ages out.

  • Where will you test?

    Jobber developer tester accounts expire after 90 days, so long projects need an extension or a new account.

Jobber webhook details that break first builds

Expecting the record in the payload

How you'll know: Your handler looks for the invoice total and finds only IDs.

Fix: Jobber's webhook tells you the topic, the account and the item ID. Your code queries the API for the rest, which means the handler needs a valid token too.

Skipping the signature check

How you'll know: Anyone who finds the URL could post fake events to it.

Fix: Check the X-Jobber-Hmac-SHA256 header against an HMAC of the raw body, keyed with your app's client secret, before doing anything else.

Processing the same event twice

How you'll know: A crew gets two notifications, or a contract goes out twice for one approved quote.

Fix: Treat every delivery as possibly repeated. Record the topic, item ID and time of each event you've handled and ignore repeats.

Doing the slow work before answering

How you'll know: Events go missing on busy days.

Fix: Answer the webhook straight away and do the follow-up work from a queue. Then run a nightly pass that catches anything that slipped.

One giant nested query

How you'll know: Requests start failing for cost even though you're making very few of them.

Fix: Jobber limits by query cost as well as by request count. Ask for fewer fields per page, paginate, and spread large backfills out.

Where Zapier and the QuickBooks sync hand over to the API

Jobber's official Zapier integration is good at one trigger and one action: a new client adds a spreadsheet row, a paid invoice posts to Slack. It starts failing when steps depend on each other, when a condition decides what happens next, or when existing records need to come across from before the zap was turned on.

The native QuickBooks Online sync moves clients and invoices. It doesn't know about a commission rule, a franchise where each location books to its own company file, or an approved quote that should send a contract through a separate e-sign tool and ask for a deposit.

Those are the builds n-frames does on the GraphQL API: quote approvals that start the next three steps, bulk updates that write a route planner's schedule back to every affected job in one pass, and syncs that carry the rules your business actually uses.

Let's talk

Ready to stop patching Jobber with Zaps?

n-frames designs the integration, builds it on Jobber's GraphQL API with signed webhooks and a nightly catch-up, and keeps it working when Jobber releases a new API version. It stays a private app in your account, so there's no Marketplace review to wait for.

Retire the fragile zaps →

Questions people ask

Does Jobber have an API?

Yes, a documented GraphQL API covering clients, quotes, jobs, invoices and more, with webhooks for changes. It's meant for building custom apps and integrations on top of Jobber.

Is the Jobber API REST or GraphQL?

GraphQL. There's one endpoint, and each request names exactly which fields it wants, including related records, instead of calling a separate REST URL per object.

Does Jobber integrate with Zapier, and when is that enough?

Yes, Jobber has an official Zapier integration. It's enough for single-step automations. Chains of dependent steps, conditions or backfills of existing records are better built directly on the API.

Does Jobber have a native QuickBooks integration?

Yes, it syncs clients and invoices with QuickBooks Online. Commission rules, multi-entity setups and anything that should happen outside the books are left for custom work on top of it.

Do you need a developer account to build against the Jobber API?

Yes. You sign up for Jobber's Developer Center, create an app there and set its scopes. For your own company's integration that's the whole process. Jobber's App Review only applies if you want the app listed in the Marketplace.

Does Jobber have to approve a custom integration?

Not if it stays a Draft app for your own use and connects to five or fewer paying Jobber accounts. Above that, or for a public listing, you request a review and meet Jobber's App Review team.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.