Rather have us handle this? We set this up for clients every day.
See the Service
Guides / Jobber

Jobber Developer Account

Step-by-step instructions for setting up a Jobber developer account and configuring API access for integration.

Last verified: April 2026

What You’re Setting Up

Jobber provides a developer portal where we register an application and obtain credentials to connect with your Jobber account. Jobber’s API uses GraphQL (more on that below) and OAuth 2.0 for authentication. In most cases, we handle the developer setup — but you may need to authorize the connection from your Jobber account.

This process takes about 15 minutes for the initial setup, though the test environment Jobber provides has a 90-day lifespan.

Step-by-Step Setup

1. Create a Jobber Developer Account

  1. Go to developer.getjobber.com
  2. Create a developer account using your email address
  3. This is separate from your main Jobber login — the developer account is specifically for building integrations

The developer account is free and comes with a 90-day test environment pre-loaded with sample data. We use this environment to build and test the integration before connecting to your production account.

2. Create an Application

Once your developer account is active:

  1. Log into the developer portal
  2. Navigate to the section for managing your apps
  3. Create a new app with:
    • App name: Something like “AcuCoders [Your Company] Integration”
    • Redirect URI: We’ll provide this value — it’s the URL our server uses to complete the OAuth authorization flow
  4. Save the application

3. Copy Your Credentials

After creating the app:

  1. Copy the Client ID
  2. Copy the Client Secret
  3. Send both to us through the secure link we provide

4. Authorize the Connection

When we’re ready to connect to your live Jobber data:

  1. We’ll send you an authorization link
  2. Click the link and log into your production Jobber account (not the developer test account)
  3. Review the permissions and approve the connection

This grants our integration access to your live data. You can revoke access at any time from your Jobber account settings.

5. Scopes We Typically Need

We request access based on what the integration does. Common scopes include:

  • Clients — read and write client records, contact info, and properties
  • Jobs — job details, status, scheduling, and assigned team members
  • Invoices — invoice creation, line items, payment status
  • Quotes — quote details, approval status
  • Requests — new service requests and their details

We only request what’s necessary. You’ll see the full list during the authorization step.

About Jobber’s GraphQL API

Jobber uses a GraphQL API instead of the more common REST API. You don’t need to worry about the technical differences, but here’s the key thing to know:

GraphQL lets us request exactly the data we need — no more, no less. If we only need a client’s name and email, we ask for just those fields. This makes the integration more efficient and faster than APIs that return everything whether you need it or not.

From your perspective, it works the same as any other API integration. We handle the technical details.

Let's talk about your systems. Tell us what tools you're using and what's not working. We'll tell you what's possible.
Get in touch

Common Issues

Test Environment Data

The developer test environment comes with sample data that doesn’t mirror your real Jobber account. This is fine for building and testing the integration logic, but the final testing and go-live always happen against your production account.

Don’t add your real data to the test environment — it’s temporary and will be deleted.

90-Day Test Environment Expiry

Jobber’s test environment expires after 90 days. If the build takes longer than expected or we need to revisit the integration later, we may need to create a new test environment. This doesn’t affect your production account or any live integration — it only impacts our development workspace.

Authorization With the Wrong Account

Make sure you log into your production Jobber account (the one with your real clients and jobs) when clicking the authorization link. If you accidentally authorize with the test developer account, we’ll be connected to sample data instead of your real data.

Permission Levels

The Jobber user who authorizes the connection needs admin-level access. If you authorize with a limited user account, some API operations may fail. We’ll flag this if we encounter permission issues.

Next Steps

Need help with the full integration?

This guide covers the setup. If you want us to handle the integration end to end, we can do that.

See Integration Services