Ir para o conteúdo

Authentication prerequisites for the ZoomInfo (Beta) connector in Jitterbit Studio

Introduction

These are the prerequisites for authenticating with the ZoomInfo (Beta) connector using 3-legged OAuth 2.0 (3LO) (Authorization Code Flow).

Note

Agent version 10.83 / 11.21 or later is required to use 3-legged OAuth 2.0 authentication.

Registering an application in the ZoomInfo Developer Portal requires an Enterprise API or Copilot package. An admin must assign a DevPortal subscription to the user before proceeding.

3-legged OAuth 2.0 (3LO)

Follow these steps to configure a 3-legged OAuth 2.0 (3LO) application in the ZoomInfo Developer Portal:

  1. Log in to the ZoomInfo Developer Portal.

  2. Click Create App.

  3. Enter an app name and upload a logo.

  4. Add one of the following URLs (depending on your organization's region) to the Sign-in Redirect URIs list:

    Region URL
    APAC https://apps.apac-southeast.jitterbit.com/design-studio/api/v1/oauth/authcode
    EMEA https://apps.emea-west.jitterbit.com/design-studio/api/v1/oauth/authcode
    NA https://apps.na-east.jitterbit.com/design-studio/api/v1/oauth/authcode

  5. Select the OAuth 2.0 scopes the application requires. The relevant scopes are:

    Scope Description
    api:data:company Search and enrich company data and corporate hierarchy
    api:data:contact Search and enrich contact data and org charts
    api:data:intent Intent signal data
    api:data:news News articles
    api:data:scoops Scoops data

  6. Click Create to register the application.

  7. After creation, click the application link to retrieve the Client ID and Client Secret for later use.

Generate a PKCE Code Verifier and Code Challenge

Generate a PKCE (Proof Key for Code Exchange) Code Verifier and Code Challenge pair. ZoomInfo requires PKCE using the SHA-256 (S256) method for authentication:

  1. Generate a Code Verifier. It is a cryptographically random, base64url-encoded string between 43 and 128 characters (no padding, no + or / characters). For example, using a terminal:

    $bytes = New-Object byte[] 32; [Security.Cryptography.RNGCryptoServiceProvider]::Create().GetBytes($bytes); [Convert]::ToBase64String($bytes).TrimEnd('=').Replace('+','-').Replace('/','_')

    openssl rand -base64 32 | tr -d '=' | tr '+/' '-_'

  2. Derive the Code Challenge from the Code Verifier by computing its SHA-256 hash, then base64url-encoding the result (no padding):

    $sha256 = [Security.Cryptography.SHA256]::Create(); $hash = $sha256.ComputeHash([Text.Encoding]::ASCII.GetBytes("<your_code_verifier>")); [Convert]::ToBase64String($hash).TrimEnd('=').Replace('+','-').Replace('/','_')

    echo -n "<your_code_verifier>" | openssl dgst -binary -sha256 | openssl base64 | tr -d '=' | tr '+/' '-_'

Retain both values for app configuration.

Configure an app registration in the Management Console

Follow these steps to configure required values for a Management Console private application app registration:

  1. Gather the following values from the ZoomInfo Developer Portal application and PKCE pair created above:

    • Client ID
    • Client secret
    • PKCE Code Verifier
    • PKCE Code Challenge

  2. In the app registration's configuration, enter the ZoomInfo OAuth 2.0 scopes required for your integration.

  3. Set the app's Client ID to the client ID from the ZoomInfo Developer Portal application.

  4. Set the app's Client Secret to the client secret from the ZoomInfo Developer Portal application.

  5. Set the app's Authentication URL to https://api.zoominfo.com/gtm/oauth/v1/authorize.

  6. Set the app's Access token URL and Refresh token URL to https://api.zoominfo.com/gtm/oauth/v1/token.

  7. Go to Advanced options. In the Authentication request tab, create these key-value pairs under Parameters:

    Key Value Send in
    response_type code Request URL
    code_challenge Your generated PKCE Code Challenge Request URL

  8. In the Token request tab, create these key-value pairs under Parameters:

    Key Value Send in
    code_verifier Your generated PKCE Code Verifier Request Body

Once the private application is registered on the App Registrations page, it is available to be selected in the OAuth application menu in the ZoomInfo (Beta) connection when using the Authorization Code Flow authentication option.