GoLogin is a cloud-based browser automation and multi-accounting platform that enables teams to create, manage, and run isolated browser profiles with unique fingerprints. Each profile simulates a distinct browser identity—including operating system, hardware specs, fonts, WebGL renderer, and geolocation—making it ideal for web scraping, automated testing, social media management, affiliate marketing, and ad verification workflows. GoLogin's REST API provides programmatic access to all profile and proxy management capabilities, allowing external tools and data pipelines to retrieve profile data, manage cookies, and orchestrate browser sessions at scale.
Power end-to-end data operations for your GoLogin API with Nexla. Our bi-directional GoLogin connector is purpose-built for GoLogin, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to GoLogin or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your GoLogin workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
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).
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.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
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 Authorization header of every API request sent to https://api.gologin.com.
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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the GoLogin connector tile, then select the credential that will be used to connect to the GoLogin account, and click Next; or, create a new GoLogin credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common GoLogin endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
List Profiles
Returns a list of all browser profiles associated with the account. Use this endpoint to audit your profile inventory or build downstream automations that reference profile metadata.
Response data is extracted from $.profiles[*], treating each profile object as a separate record.
This endpoint returns up to 30 profiles per page by default. Use lookup-based macros with a page iteration pattern if you need to ingest more than one page of results.
Get Browser History
Retrieves the browsing history from a browser profile. Use this endpoint to audit activity logs or analyze browsing patterns for a specific GoLogin profile.
Response data is extracted from $.history[*], treating each history entry as a separate record.
A valid profile ID must be provided as a query parameter or path component. Profile IDs can be retrieved using the List Profiles or Get All Profiles endpoint.
Get Browser Cookies
Retrieves the cookies stored in a browser profile. Use this endpoint to export cookie data for archiving, compliance review, or cross-environment synchronization.
Response data is extracted from $.cookies[*], treating each cookie as a separate record.
Cookie data may be sensitive. Ensure downstream systems and data flows are appropriately secured before ingesting cookie records into Nexla.
List Folders
Returns a list of all folders used to organize browser profiles. Use this endpoint to synchronize folder structures with external systems or build folder-aware profile management workflows.
Response data is extracted from $.folders[*], treating each folder as a separate record.
Folder IDs returned by this endpoint can be used as input for the Get All Profiles endpoint to filter profiles by folder.
List Tags
Returns a list of all tags available for organizing profiles. Use this endpoint to retrieve the tag taxonomy for use in filtering, reporting, or automating profile classification workflows.
Response data is extracted from $.tags[*], treating each tag as a separate record.
Tag IDs returned by this endpoint can be referenced in the Get All Profiles endpoint to filter profiles by tag.
Get User Info
Retrieves the current user account information. Use this endpoint to confirm account identity, verify subscription details, or pull account metadata for reporting purposes.
Sends a GET request to https://api.gologin.com/user and returns the authenticated user's account details as a single object.
Response data is extracted from $ (the root object), returning a single record with all user fields.
This endpoint returns a single record. No pagination is required.
Get User Metadata
Retrieves metadata associated with the user account. Use this endpoint to extract supplementary account-level attributes not included in the core user info response.
Response data is extracted from $ (the root object), returning a single metadata record.
This endpoint returns a single record. No pagination is required.
Get User Balance
Retrieves the account balance for the current user. Use this endpoint to monitor credit usage or track subscription consumption in financial reporting workflows.
Response data is extracted from $ (the root object), returning a single record.
This endpoint returns a single record. No pagination is required.
List Timezones
Returns a list of available timezones that can be assigned to browser profiles. Use this endpoint to retrieve the full timezone reference for use in profile creation or update workflows.
Response data is extracted from $.timezones[*], treating each timezone entry as a separate record.
This is a reference/lookup endpoint. The returned timezone identifiers can be used as input values when configuring profile creation destinations.
Get All Profiles
Retrieves a paginated list of all browser profiles with optional filtering and sorting. Use this endpoint when you need to ingest profiles with specific search criteria, folder filters, or sort orders applied.
Sends a GET request to https://api.gologin.com/browser/v2 with optional query parameters for search, folder, sort field, sort order, and tag filtering.
Response data is extracted from $.profiles[*], treating each profile object as a separate record.
Configure the following parameters: Search Query — a text string to filter profiles by name or other attributes. Folder Filter — a folder ID to restrict results to profiles within a specific folder. Sort Field — the field by which to sort results. Sort Order — ascending or descending sort direction. Tag Filter — a tag ID to restrict results to profiles with a specific tag.
All filter parameters are optional. Leaving them blank returns all profiles in the account. Use the List Folders and List Tags endpoints to retrieve valid folder and tag IDs for use as filter values.
Get Profile by ID
Retrieves detailed information about a specific browser profile by its ID. Use this endpoint when you need the full configuration record for a single profile, including fingerprint, proxy, and navigator settings.
Response data is extracted from $ (the root object), returning a single profile record.
Configure the following parameter: Id — the unique identifier of the GoLogin browser profile to retrieve.
Profile IDs can be obtained from the List Profiles or Get All Profiles endpoint. Use lookup-based macros to iterate over a list of profile IDs and retrieve detailed records for each.
Retrieve or Generate a Browser Fingerprint
Retrieves or generates a browser fingerprint for use in profile creation or analysis. Use this endpoint to obtain fingerprint data that can be applied to new or existing browser profiles.
Response data is extracted from $ (the root object), returning a single fingerprint record.
Fingerprint records returned by this endpoint can be used as input for profile creation or update destination endpoints.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
GoLogin sources can also be manually configured to ingest data from any valid GoLogin API endpoint not covered by the pre-built templates, including chained API calls or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The GoLogin REST API base URL is https://api.gologin.com. Common endpoints include https://api.gologin.com/browser/v2 (a paginated list of all browser profiles across workspaces), https://api.gologin.com/browser/{'{profileId}'} (a specific profile by ID), https://api.gologin.com/workspaces/{'{workspaceId}'}/profiles (all profiles in a workspace), and https://api.gologin.com/proxy (saved proxy configurations). Profile list endpoints are paginated using the page query parameter (e.g., https://api.gologin.com/browser/v2?page=1), returning up to 30 profiles per page by default.
Set the Path to Data to $.profiles[*] for the profiles list endpoint, or $ for single-object endpoints such as Get Profile by ID, Get User Info, or Get User Balance. GoLogin responses typically include pagination metadata (total, page, totalPages) outside the profiles array — set the metadata path (e.g., $.totalPages or $.total) to preserve this information alongside each record. The Authorization header is added automatically from your GoLogin credential and does not need to be entered manually.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new GoLogin data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the GoLogin destination, and select the Send to Destination option from the menu. Select the GoLogin connector from the list of available destination connectors, then select the credential that will be used to connect to the GoLogin account, and click Next; or, create a new GoLogin credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common GoLogin endpoints. Select the endpoint to which this destination will send data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your destination for this endpoint.
Add Member to Workspace
Invites one or more members to a workspace with specified roles and permissions. Use this endpoint to automate team onboarding or synchronize workspace membership from an external directory.
Sends a POST request to the GoLogin workspace members endpoint with the invitation payload in the request body.
Configure the following parameter: Workspace Id — the unique identifier of the GoLogin workspace to which members will be added.
The workspace ID can be found in the GoLogin web application under workspace settings, or retrieved via the GoLogin API.
Remove Member from Workspace
Removes a member from a workspace, revoking all their access and permissions. Use this endpoint to automate offboarding or synchronize workspace membership removals from an external HR or identity system.
Sends a DELETE request to the GoLogin workspace member endpoint for the specified member.
Configure the following parameters: Workspace Id — the unique identifier of the workspace. Member Id — the unique identifier of the member to remove.
This operation is irreversible — the member will lose all access to the workspace immediately. Re-invitation is required to restore access.
Create Workspace
Creates a new workspace with the specified configuration. Use this endpoint to programmatically provision GoLogin workspaces as part of a customer onboarding or environment setup workflow.
Sends a POST request to the GoLogin workspaces endpoint with the new workspace configuration in the request body.
Returns the created workspace object, including the newly assigned workspace ID.
Enable the Response Webhook option to capture the new workspace ID returned after creation for use in downstream flows.
Create Dev Token
Creates a new developer API token for programmatic access to the GoLogin API. Use this endpoint to automate token provisioning as part of a developer or integration setup workflow.
Sends a POST request to the GoLogin developer token endpoint and returns the newly created token.
The created token is returned in the API response and should be captured via the Response Webhook option if it needs to be used downstream.
Store generated API tokens securely. Tokens grant full API access to the associated GoLogin account and should not be exposed in logs or downstream systems without appropriate access controls.
Create a Standard Browser Profile with Full Parameter Set
Creates a standard browser profile with the full set of configurable parameters. Use this endpoint to bulk-provision browser profiles with custom fingerprint, proxy, and navigator settings sourced from a Nexset.
Returns the created profile object including the newly assigned profile ID.
Use the Retrieve or Generate a Browser Fingerprint source endpoint to generate fingerprint values that can be included in the profile creation payload.
Full Update of a Browser Profile
Performs a full replacement update of a browser profile, including fingerprint, proxy, navigator settings, notes, and other attributes. Use this endpoint to synchronize complete profile configurations from an external source of truth into GoLogin.
Configure the following parameter: Update Browser By Id Id — the unique identifier of the browser profile to update.
This is a full replacement (PUT) operation — all profile fields must be included in the payload. Use the Get Profile by ID source endpoint to retrieve the current profile state before performing updates.
Upload / Replace Cookies for a Browser Profile
Uploads or replaces the cookies stored in a specific browser profile. Use this endpoint to restore saved session cookies or programmatically inject cookies into GoLogin profiles.
Sends a POST request to the GoLogin browser cookies endpoint with the cookie payload for the specified profile.
Configure the following parameter: Create Browser By Id Cookies Id — the unique identifier of the browser profile whose cookies will be replaced.
This operation replaces all existing cookies for the profile. Use the Get Browser Cookies source endpoint to retrieve the current cookie set before performing updates if a backup is needed.
Create a New Profile Folder
Creates a new profile folder for organizing browser profiles. Use this endpoint to programmatically provision folder structures as part of a workspace setup or profile management workflow.
Returns the created folder object including the newly assigned folder ID.
Enable the Response Webhook option to capture the new folder ID for use in subsequent profile assignment flows.
Create a New Tag
Creates a new tag for organizing and classifying browser profiles. Use this endpoint to programmatically set up a tag taxonomy before bulk-assigning tags to profiles.
Sends a POST request to the GoLogin tags endpoint with the tag name and configuration in the request body.
Returns the created tag object including the newly assigned tag ID.
Enable the Response Webhook option to capture the new tag ID for use in subsequent profile tagging flows.
Bulk Delete Multiple Browser Profiles
Deletes multiple browser profiles in a single API call. Use this endpoint to programmatically clean up stale or decommissioned profiles in bulk.
Sends a DELETE request to the GoLogin browser endpoint with an array of profile IDs in the request body.
Use the Record Batching option to group profile IDs into appropriately sized deletion payloads.
Profile deletion is permanent and cannot be undone. Verify the list of profile IDs before executing bulk deletion flows.
Delete a Browser Profile by ID
Deletes a single browser profile by its unique ID. Use this endpoint to remove individual profiles as part of an automated lifecycle management workflow.
Configure the following parameter: Delete Browser By Id Id — the unique identifier of the browser profile to delete.
Profile deletion is permanent and cannot be undone. Use lookup-based macros to iterate over a list of IDs and delete profiles one at a time.
Move a Browser Profile into a Folder
Moves a browser profile into a specified folder. Use this endpoint to reorganize profiles programmatically or automate folder assignment as part of a profile management workflow.
Sends a POST request to the GoLogin browser folder assignment endpoint for the specified profile.
Configure the following parameter: Create Browser By Id Folder Id — the unique identifier of the browser profile to move.
Folder IDs can be retrieved using the List Folders source endpoint. Use lookup-based macros to dynamically assign profiles to folders based on data from an upstream Nexset.
Stop a Running Cloud Browser Session
Stops a running cloud browser session for a profile. Use this endpoint to programmatically terminate active sessions as part of a session management or resource cleanup workflow.
Sends a DELETE request to the GoLogin cloud browser web session endpoint for the specified profile.
Configure the following parameter: Delete Browser By Id Web Id — the unique identifier of the profile whose cloud session should be stopped.
Stopping a cloud browser session terminates the active browsing session immediately. Ensure that any required session data has been saved before invoking this endpoint.
GoLogin destinations can also be manually configured to send data to any valid GoLogin API endpoint. This is useful for creating or updating browser profiles, managing proxy assignments, importing profile configurations, or synchronizing profile metadata from external systems into GoLogin. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
GoLogin's REST API accepts and returns JSON — select JSON as the content format. The GoLogin REST API base URL is https://api.gologin.com. Common destination endpoints include https://api.gologin.com/browser (create a new profile with POST), https://api.gologin.com/browser/{'{profileId}'} (fully replace a profile with PUT, or partially update it with PATCH), and https://api.gologin.com/proxy (create or update a saved proxy configuration). For update and upsert operations, include the GoLogin profile ID at the end of the URL — the profile ID can be found in the GoLogin web application under each profile's settings, or retrieved via the GET /browser/v2 endpoint. The Authorization header is added automatically from your GoLogin credential and does not need to be entered manually.
GoLogin enforces API rate limits of 300 requests per minute on free/trial plans and 1,200 requests per minute on paid plans. If you are processing large volumes of records, consider enabling record batching to reduce the total number of API calls and avoid rate limit errors.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured GoLogin endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to GoLogin until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
