Authorization

GoLogin
Prerequisites
To connect Nexla to GoLogin, you will need a GoLogin account and a personal API token. GoLogin offers a free trial as well as paid plans; the API is available on all plan tiers, though rate limits differ between free and paid plans (300 requests/minute on free/trial plans, 1,200 requests/minute on paid plans).
Generate a GoLogin API Token
GoLogin authenticates all API requests using a Bearer token. You can generate your personal API token directly from the GoLogin web application.
-
Sign in to your GoLogin account at app.gologin.com.
-
Click your profile avatar or username in the upper-right corner to open the account menu, and select Settings.
-
In the left navigation panel, select API (also accessible by navigating directly to
https://app.gologin.com/#/personalArea/TokenApi). -
Click the New Token button to generate a new personal API token.
-
Copy the generated token and store it in a secure location. The token will be used to authenticate all API requests made by Nexla on your behalf.
GoLogin API tokens provide full programmatic access to your account, including the ability to create, read, update, and delete browser profiles and proxies. Store your token securely and avoid sharing it. If a token is compromised, return to the API settings page to revoke it and generate a new one.
Create a GoLogin Credential
- To create a new GoLogin 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 Token
- Enter the GoLogin personal API token you generated in the Prerequisites section above in the Token field. Nexla will include this token as a Bearer credential in the
Authorizationheader of every API request sent tohttps://api.gologin.com.
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.