Authorization

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

Pulsedive

Prerequisites

Before creating a Pulsedive credential, you need to obtain your Personal API key from your Pulsedive account. Pulsedive uses API key authentication for all API requests, with the API key sent as a query parameter (key) in the API request URL.

To obtain your Pulsedive API key, follow these steps:

1. Sign in to your Pulsedive account, or create a new account at Pulsedive.

2. Navigate to your Pulsedive dashboard or account settings in the Pulsedive interface.

3. Look for the API or API Keys section in your account settings or dashboard.

4. If you don't have an API key yet, click Create API Key or Generate API Key to create a new Personal API key.

5. Configure your API key settings:

   • Enter a name for the API key (e.g., "Nexla Integration")
   • Review and select the permissions or scopes for the key (if applicable)

6. Click Create or Generate to create the API key.

7. Copy the Personal API key immediately after it's generated, as it may not be accessible again after you navigate away from the page.

8. Store the API key securely, as you will need it to configure your Nexla credential. The API key is sensitive information and should be kept confidential.

The API key is sent as a query parameter (key) in the API request URL for all API requests to the Pulsedive API. The API key authenticates your requests and grants access to Pulsedive resources based on your account permissions. If your API key is compromised, you should immediately revoke it in your Pulsedive account settings and generate a new one. For detailed information about obtaining API keys, API authentication, and available endpoints, refer to the Pulsedive API documentation.

Create a Pulsedive Credential

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

New Credential Overlay – Pulsedive

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.

API Key Authentication

Pulsedive uses API key authentication for all API requests. The API key is sent as a query parameter (key) in the API request URL to authenticate API requests to the Pulsedive API.

2. Enter your Pulsedive Personal API key in the API Key field. This is the Personal API key you obtained from your Pulsedive account settings (API or API Keys section). The API key is sent as a query parameter (key) in the API request URL for all API requests to the Pulsedive API. The API key is sensitive information and must be kept confidential.

   Your Pulsedive Personal API key can be found in your Pulsedive account settings under the API or API Keys section. The API key is sent as a query parameter (key) in the API request URL for all API requests to the Pulsedive API.

   If your API key is compromised, you should immediately revoke it in your Pulsedive account settings and generate a new one. The API key provides access to your Pulsedive account data and should be treated as sensitive information. Keep your API key secure and do not share it publicly.

   For detailed information about obtaining API keys, API authentication, and available endpoints, see the Pulsedive API documentation.

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.