Authorization

Dixa
Prerequisites
To connect Nexla to Dixa, you need a Dixa API token. API tokens are generated in the Dixa admin settings and provide authenticated access to both the Dixa API (dev.dixa.io) and the Dixa Exports API (exports.dixa.io) using the same credential.
Administrator Access Required
Only Dixa administrators can generate API tokens. Ensure that you have administrator-level access to your Dixa organisation before proceeding.
Generate a Dixa API Token
-
Log in to your Dixa account at dixa.com as an administrator.
-
In the left navigation pane, click Settings, then scroll down to the Manage section in the sidebar and click Integrations.
-
On the Integrations page, click the API Tokens tab.
-
Click Add API Token to open the token creation form.
-
Enter a unique, descriptive name for the token in the Name field. A clear name (for example,
Nexla Integration) helps you identify the token's purpose later. -
Click Save changes to generate the token.
-
Click the Copy icon to copy the newly generated API token value, and store it securely—treat it with the same care as a password. The token value is shown only once and cannot be retrieved again after you navigate away from the page.
For detailed guidance on API token creation, refer to the official Dixa tutorial at docs.dixa.io/docs/tutorial-create-an-api-token.
Create a Dixa Credential
- To create a new Dixa credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Credential Name & Description
-
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 to 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
-
Enter your Dixa API token in the API Key field. This key is passed in the
Authorizationheader for every request made by Nexla to the Dixa API and the Dixa Exports API. Keep this value secure and do not share it with unauthorised parties.The same API key authenticates requests to both the Dixa API (
https://dev.dixa.io/v1) and the Dixa Exports API (https://exports.dixa.io/v1). A single credential in Nexla covers all Dixa endpoint templates.
Save the Credential
-
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.
-
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.