Skip to main content

Jobber API Endpoints

Reference for the Jobber GraphQL API operations and OAuth endpoints the iPaaS.com Jobber integration uses to read and write clients, products and services, invoices, payments, work requests and webhooks.

Portal Info

Jobber is a web app, with one address for every Jobber account:

https://secure.getjobber.com

Jobber does not vary this address by region or environment. A record's page in Jobber ends with the number of the record: for example, the client page https://secure.getjobber.com/clients/156768107 belongs to client number 156768107.

API Endpoints Intro

The Jobber integration uses the Jobber GraphQL API. GraphQL has one endpoint: every call is an HTTP POST to the same address, and the body names the query (a read) or mutation (a write) to run. This article lists each query and mutation the integration runs, grouped by the Jobber data type it reads or writes.

Base URL:

https://api.getjobber.com/api/graphql

Jobber publishes one API address, used for every Jobber account. The integration takes the address from the API Url subscription setting, which defaults to the address above and accepts only an https address on Jobber's own domain. Leave the setting at its default. In the sections below, [Base URL] stands for this address.

API version: every call sends Jobber's version header (X-JOBBER-GRAPHQL-VERSION) set to 2026-09-25. Jobber requires a version on every call from an app and supports each version for at least 12 months after its release.

Authentication: every call carries the access token Jobber issued when subscribers or their MiSP clicked Authenticate on the subscription. Access tokens last 60 minutes; the integration refreshes them automatically (see the Authorization Endpoint section). If Jobber still refuses the authorization after a refresh, the error appears in Dashboard / Integration Monitoring / Error Logs, and subscribers or their MiSP click Authenticate again.

Paging: Jobber returns lists in pages, using a cursor (first and after, with pageInfo.endCursor and pageInfo.hasNextPage in the answer). The integration reads every page. The page size for polls comes from the Customer Page Size, Transaction Page Size and Product Page Size subscription settings; a value above 100 acts as 100.

Rate limits: Jobber limits each app on each Jobber account in two ways, as published in its API Rate Limits page (checked 2026-11-16): 2,500 requests per 5 minutes, and a query cost budget, where each call spends points and the points are restored over time. When Jobber answers that a limit is reached, the integration stops the transfer and iPaaS.com retries it after the wait Jobber's answer allows. The subscription's API Throttle Limit, API Throttle Seconds and Concurrent Connections settings (Jobber Connections and Settings) control how fast iPaaS.com sends calls; leave them at their defaults unless your MiSP recommends otherwise.

The integration also calls iPaaS.com's own APIs (for example, to find the iPaaS.com record linked to a Jobber record). Those calls are part of the iPaaS.com platform and are not listed here.

Table of Contents

  • Account Endpoints

  • Client Endpoints

  • Product and Service Endpoints

  • Custom Field Endpoints

  • Invoice Endpoints

  • Payment Endpoints

  • Request Endpoints

  • Webhook Endpoints

  • Authorization Endpoint


Account Endpoints

Get the Account (POST)

Reads the Jobber account the subscription is authorized for. Used when iPaaS.com checks the subscription's connection to Jobber, and right after subscribers or their MiSP click Authenticate, to record which Jobber account the subscription is connected to.

[Base URL]
  • Operation: query account

  • Key fields: the account's id and name.


Client Endpoints

Get a Client by Id (POST)

Reads one client by its Jobber id. Used during TO iPaaS.com transfers (from a client webhook, a client poll, an invoice whose client is not in iPaaS.com yet, or a Manual Sync) to read the full client, and during FROM iPaaS.com updates to read the client's current emails and phones before editing them.

[Base URL]
  • Operation: query client(id)

  • Key fields: first and last name, company name, whether the client is a company, title, lead and archived flags, balance, created and updated dates, the client's Jobber web address, emails, phones, billing address, tags (up to 50), whether the client has invoices, and custom fields.

List Changed Clients (POST)

Lists the ids of clients changed since the last poll. Used by the client poll (CLIENT_POLL), which then reads each client by id. The first poll looks back the number of days in the Customer Poll Days setting (7 when blank).

[Base URL]
  • Operation: query clients, filtered by last-updated date, paged

  • Key fields: client id and updated date.

Search Clients by Email (POST)

Searches clients by email address (up to 5 results). Used during FROM iPaaS.com client creation when a collision handling method is set, to link an existing Jobber client with the same email instead of creating a duplicate.

[Base URL]
  • Operation: query clients, searching the email field

  • Key fields: the same client fields as Get a Client by Id.

Get a Client's Properties (POST)

Reads the service properties of a client (up to 20). Used during FROM iPaaS.com work request creation to pick the property whose street matches the order's service street, or the client's first property.

[Base URL]
  • Operation: query client(id), reading clientProperties

  • Key fields: property id and street.

Create a Client (POST)

Creates a client in Jobber. Used during FROM iPaaS.com transfers when adding a new customer, including a customer sent first because an order's customer is not in Jobber yet. The customer's first address with a street or city becomes both the client's billing address and a service property.

[Base URL]
  • Operation: mutation clientCreate

  • Key fields: name, company name, company flag, title, primary email, primary phone, billing address, service property address, and custom fields.

Update a Client (POST)

Updates an existing client. Used during FROM iPaaS.com transfers when updating a customer. The client's primary email and phone are replaced rather than added to.

[Base URL]
  • Operation: mutation clientEdit

  • Key fields: name, company name, company flag, title, primary email, primary phone, billing address, and custom fields.


Product and Service Endpoints

Get a Product or Service by Id (POST)

Reads one product or service by its Jobber id. Used during TO iPaaS.com transfers (from a product webhook, the product poll, an invoice line's item, or a Manual Sync).

[Base URL]
  • Operation: query productOrService(id)

  • Key fields: name, description, category (product, service or labour), unit price, unit cost, markup, taxable flag, visible flag, duration in minutes, and custom fields.

List All Products and Services (POST)

Lists the ids of every product and service. Used by the product poll (PRODUCT_OR_SERVICE_POLL), which then reads each item by id. Jobber items carry no last-changed date, so each poll sends every item.

[Base URL]
  • Operation: query products, paged

  • Key fields: item id.

Search Products and Services by Name (POST)

Searches items by name (up to 10 results). Used during FROM iPaaS.com product creation when a collision handling method is set, to link an existing Jobber item with the same name instead of creating a duplicate.

[Base URL]
  • Operation: query products, with a search term

  • Key fields: the same item fields as Get a Product or Service by Id.

Create a Product or Service (POST)

Creates a product or service in Jobber. Used during FROM iPaaS.com transfers when adding a new product.

[Base URL]
  • Operation: mutation productsAndServicesCreate

  • Key fields: name, description, category, unit price, unit cost, markup, taxable flag, duration in minutes, and custom fields.

Update a Product or Service (POST)

Updates an existing product or service. Used during FROM iPaaS.com transfers when updating a product. It is also used right after a create when the new item should be hidden in Jobber, because Jobber's create does not accept the visible flag.

[Base URL]
  • Operation: mutation productsAndServicesEdit

  • Key fields: the same fields as the create, plus the visible flag.


Custom Field Endpoints

List Custom Field Configurations (POST)

Lists the custom fields set up in the Jobber account (name, type and the records they apply to), paged 100 at a time. Used during FROM iPaaS.com client and product transfers to match each mapped custom field to a Jobber custom field by name.

[Base URL]
  • Operation: query customFieldConfigurations, paged

  • Key fields: custom field id, name, what it applies to, value type, and archived flag.

Create a Text Custom Field (POST)

Creates a text custom field in Jobber, named as the mapped custom field. Used during FROM iPaaS.com client and product transfers the first time a value arrives for a custom field Jobber does not have yet. Custom fields created for products and services are read-only in Jobber's screens.

[Base URL]
  • Operation: mutation customFieldConfigurationCreateText

  • Key fields: name, the records it applies to (clients, or products and services), and the read-only flag.


Invoice Endpoints

Get an Invoice by Id (POST)

Reads one invoice by its Jobber id. Used during TO iPaaS.com transfers (from an invoice webhook, the invoice poll or a Manual Sync). The integration sends invoices with up to 100 line items and up to 50 payments.

[Base URL]
  • Operation: query invoice(id)

  • Key fields: invoice number, status, subject, message, issued and due dates, created and updated dates, the invoice's Jobber web address, client (id, name, email), billing address, amounts (subtotal, discount, tax, total, payments total, balance, deposit, tips), discount rate and type, tax rate and its components, line items (name, description, quantity, unit price, total, taxable flag, category, date, and the linked product or service), payment ids, and custom fields.

List Changed Invoices (POST)

Lists the ids of invoices changed since the last poll. Used by the invoice poll (INVOICE_POLL), which then reads each invoice by id. The first poll looks back the number of days in the Transaction Poll Days setting (7 when blank).

[Base URL]
  • Operation: query invoices, filtered by last-updated date, paged

  • Key fields: invoice id and updated date.


Payment Endpoints

Get Payment Records by Id (POST)

Reads the payments recorded on an invoice, all in one call. Used during TO iPaaS.com invoice transfers to send each payment as a payment on the iPaaS.com transaction.

[Base URL]
  • Operation: query paymentRecord(id), once per payment in the same call

  • Key fields: amount, entry date, payment type, adjustment type, details, payment origin, and for card payments the card brand, last digits, transaction id and transaction status.


Request Endpoints

Create a Request (POST)

Creates a work request in Jobber for the order's client, with the order's lines. Used during FROM iPaaS.com transfers when adding an order. Lines are not saved to Jobber's products and services.

[Base URL]
  • Operation: mutation requestCreate

  • Key fields: client, title, service property, and line items (name, description, quantity, unit price, linked product or service, taxable flag).

Add a Note to a Request (POST)

Adds a note to a new work request. Used during FROM iPaaS.com transfers when the order's note is mapped, right after the request is created.

[Base URL]
  • Operation: mutation requestCreateNote

  • Key fields: the note text.

Update a Request (POST)

Updates an existing work request. Used during FROM iPaaS.com transfers when updating an order; only the request's title changes.

[Base URL]
  • Operation: mutation requestEdit

  • Key fields: title.


Webhook Endpoints

Create a Webhook Endpoint (POST)

Registers a webhook in the subscriber's Jobber account for one event (for example CLIENT_CREATE or INVOICE_UPDATE), pointing at this subscription's iPaaS.com webhook address. Used when subscribers or their MiSP turn on a webhook scope on the subscription. Poll scopes have no webhook.

[Base URL]
  • Operation: mutation webhookEndpointCreate

  • Key fields: the event (topic) and the iPaaS.com webhook address.

When Jobber sends an event, it carries the event name and the record's id, not the record itself; the integration then reads the record with the matching Get operation above.

Delete a Webhook Endpoint (POST)

Removes a webhook the subscription registered. Used when subscribers or their MiSP turn off a webhook scope. A webhook Jobber has already removed (for example after the app was disconnected) is treated as removed.

[Base URL]
  • Operation: mutation webhookEndpointDelete

  • Key fields: the webhook id the subscription stored when it registered the webhook.


Authorization Endpoint

Jobber uses OAuth 2.0 with the authorization code flow and PKCE (S256). The OAuth endpoints are on the same host as the API, at fixed addresses that do not depend on the API Url setting.

Authorize:

https://api.getjobber.com/api/oauth/authorize

When subscribers or their MiSP click Authenticate on the subscription, iPaaS.com opens this page with the iPaaS.com Jobber app's client id, the iPaaS.com redirect address, a state value and a PKCE code challenge. A Jobber admin logs in and allows access.

Token:

https://api.getjobber.com/api/oauth/token

This endpoint is used for:

  • Authorization code exchange: turns the code Jobber returns after access is allowed into an access token and a refresh token (grant_type=authorization_code, with the PKCE code verifier).

  • Token refresh: exchanges the refresh token for a new access token before the current one expires, or when Jobber refuses it (grant_type=refresh_token). When Jobber returns a new refresh token (Jobber's refresh token rotation), the integration stores it before making any other call.

Both requests send the iPaaS.com Jobber app's client id and client secret as form fields. Subscribers do not create a Jobber app or enter keys: iPaaS.com holds the app's credentials.

Related Documents

External References

Did this answer your question?