Authorization

Lokalise
Prerequisites
Before creating a Lokalise credential, you need to obtain an API token from your Lokalise account settings. The API token is required to authenticate with the Lokalise API.
To obtain your API token, follow these steps:
-
Sign in to your Lokalise account using your credentials.
-
Click on your profile icon or avatar in the top-right corner of the Lokalise interface, and select Personal settings or Account settings from the dropdown menu.
-
In your profile settings, navigate to the API tokens section. This section may be located under Security, Integrations, or directly in the main settings menu, depending on your Lokalise account configuration.
-
If you don't have an existing API token, click Create token or Generate new token to create a new API token. You may be asked to provide a name or description for the token to help identify it later (e.g., "Nexla Integration").
-
After generating the API token, copy it immediately. The API token is typically displayed only once for security reasons and may not be accessible again after you navigate away from the page.
-
Store the API token securely, as you will need it to configure your Nexla credential. The API token provides full access to your Lokalise account data, so treat it as sensitive information.
The API token is sent in the X-Api-Token header for all API requests to the Lokalise API. The API token authenticates your account and grants access to your Lokalise data, including projects, teams, files, languages, tasks, and webhooks. The API token does not expire automatically, but you can regenerate it at any time if needed. For detailed information about API token setup, authentication, and available API endpoints, refer to the Lokalise API documentation and Lokalise API authentication documentation.
Create a Lokalise Credential
- To create a new Lokalise credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Lokalise

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 provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.
API Token Authentication
Lokalise uses API Token authentication for all API requests. The API token is sent in the X-Api-Token header to authenticate API requests to the Lokalise API.
-
Enter your Lokalise API token in the API Token field. This is the API token you obtained from your Lokalise profile settings (Profile settings > API tokens). The API token is sent in the
X-Api-Tokenheader for all API requests to the Lokalise API. The API token authenticates your account and determines what data and operations you can access based on your account permissions.Keep your API token secure and do not share it publicly. The API token provides access to your Lokalise account data and should be treated as sensitive information. If your API token is compromised, you should immediately regenerate it in your Lokalise profile settings. Your Lokalise API token can be found in your Lokalise profile settings (Profile settings > API tokens) where you manage API tokens. The API token is sent in the
X-Api-Tokenheader for all API requests to the Lokalise API. The API token does not expire automatically, but you can regenerate it at any time if needed. For detailed information about obtaining and managing API tokens, API authentication, and available endpoints, see the Lokalise API documentation and Lokalise API authentication documentation.
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.