Skip to main content

Authorization

Follow this guide to create a new Jobber credential that will allow Nexla to authenticate to and exchange data with your Jobber account.
jobber_api_auth.png

Jobber

Prerequisites​

Nexla connects to Jobber using the OAuth 2.0 authorization code flow. To complete credential setup, you must first register an application in the Jobber Developer Center to obtain a Client ID and Client Secret.

Create a Jobber Developer Center App​

  1. Sign in to or create an account at the Jobber Developer Center.

  2. Navigate to the Apps page in the Developer Center dashboard.

  3. Click Create App (or New App) to begin creating a new application.

  4. Fill in the required application details:

    • App Name: Enter a descriptive name for your integration (e.g., "Nexla Integration").

    • Redirect URI: Enter https://app.nexla.io/oauth/callback as the redirect URI. This is the URL to which Jobber will redirect after a user authorizes your application.

  5. Save or submit the app registration form. Jobber will generate and display your application credentials:

    • Client ID: A publicly visible identifier for your application.

    • Client Secret: A confidential string used to authenticate your application with the Jobber API. Store this value securely and do not share it.

The Client Secret is displayed only once at the time of app creation. Copy it immediately and store it in a secure location such as a password manager or secrets vault. Additional details about the OAuth 2.0 flow are available in the Jobber App Authorization documentation.

  1. Note the API Version used by the Jobber GraphQL API. The default version used by the Nexla connector is 2023-08-18, which is sent in the X-JOBBER-GRAPHQL-VERSION request header. Consult the Jobber API changelog if you need to use a different version.

Create a Jobber Credential​

  • To create a new Jobber credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They can be used to provide information about the resource purpose, data freshness, and other context that helps the owner and other users efficiently understand and utilize the resource.

OAuth 2.0 Configuration​

Jobber uses the OAuth 2.0 authorization code flow (3-legged OAuth). Nexla will redirect you through the Jobber authorization page as part of the credential creation process.

  1. Enter the Client ID from your Jobber Developer Center app in the Client ID field. This value is the publicly visible identifier for your registered application.

  2. Enter the Client Secret from your Jobber Developer Center app in the Client Secret field. This value authenticates your application with the Jobber API and must be kept confidential.

    The API Version and Credential Test Query fields are pre-configured with default values (2023-08-18 and query { account { id name } } respectively) and are hidden from the standard credential form. These defaults are suitable for most integrations. Contact your Nexla administrator if you need to override these values.

  3. After entering your Client ID and Client Secret, click Authorize (or Connect) to initiate the OAuth 2.0 authorization flow. You will be redirected to the Jobber login and authorization page.

  4. Sign in to your Jobber account and click Authorize to grant Nexla access to your Jobber data.

  5. After successful authorization, you will be redirected back to Nexla, and the credential will be validated automatically using a test GraphQL query against the Jobber API.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.