Skip to main content

Authorization

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

Basis DSP

Prerequisites​

Before creating a Basis DSP credential in Nexla, you need to obtain OAuth 2.0 client credentials (Client ID and Client Secret) from Basis DSP. Basis DSP uses OAuth 2.0 with client credentials flow for secure API access.

OAuth 2.0 Client Credentials Setup​

Basis DSP requires OAuth 2.0 client credentials for API access. These credentials are typically provided by Basis DSP through email or your Basis DSP account settings.

  1. Contact Basis DSP: Reach out to Basis DSP support or your account representative to request API access and OAuth 2.0 client credentials. Basis DSP will provide you with a Client ID and Client Secret via email or through your account portal.

  2. Obtain Client Credentials: Once you receive the Basis API email, you will have:

    • Client ID: A unique identifier for your OAuth application
    • Client Secret: A secret key used to authenticate your application
    • Access Scope: The scope of access granted to your application (typically STATS for statistics access)

  3. Review Access Scope: Understand the access scope provided with your credentials. The default scope is typically STATS, which provides access to statistics and reporting data. Different scopes may provide access to different API endpoints and data.

  4. Copy Credentials: Copy your Client ID and Client Secret immediately after receiving them. Keep these credentials secure, as they provide access to your Basis DSP account data.

    Basis DSP OAuth 2.0 client credentials provide programmatic access to your Basis DSP account. Keep your Client ID and Client Secret secure and do not share them publicly or commit them to version control systems. The credentials use the OAuth 2.0 client credentials flow, which exchanges the Client ID and Client Secret for an access token. For detailed information about Basis DSP API authentication, see the Basis DSP API documentation.

For additional information about Basis DSP API authentication and credential management, see the Basis DSP API documentation.

Create a Basis DSP Credential​

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

New Credential Overlay – Basis DSP

BasisDSPCred.png

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 should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

OAuth 2.0 Configuration​

  1. Enter your Basis DSP Client ID in the Client ID field. This should be the Client ID received from Basis DSP in the Basis API email. The Client ID is used together with the Client Secret to obtain an OAuth 2.0 access token.

  2. Enter your Basis DSP Client Secret in the Client Secret field. This should be the Client Secret received from Basis DSP. The Client Secret is used together with the Client ID to authenticate and obtain an OAuth 2.0 access token.

    The Client ID and Client Secret are used for OAuth 2.0 client credentials flow authentication. The credentials are exchanged for an access token using the token endpoint (https://api.sitescout.com/oauth/token). The access token is then used in the Authorization: Bearer {token} header for all API requests. Keep your Client Secret secure and do not share it publicly or commit it to version control systems. For detailed information about Basis DSP API authentication, see the Basis DSP API documentation.

  3. Enter the access scope in the Access Scope field. This should be the scope of access granted to your application (e.g., STATS for statistics access). The default value is STATS if not specified. The scope determines which API endpoints and data you can access.

    The access scope determines the level of access your application has to the Basis DSP API. The default scope is STATS, which provides access to statistics and reporting data. Different scopes may provide access to different API endpoints. Ensure the scope matches the access level granted by Basis DSP for your application.

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.