Skip to main content

Data Source

The GoLogin connector enables you to ingest browser profile data, proxy configurations, and session metadata from your GoLogin account into Nexla data flows. This is particularly useful for applications that need to audit profile inventories, monitor proxy assignments, or synchronize GoLogin profile data with downstream analytics or data warehouse systems. Follow the instructions below to create a new data flow that ingests data from a GoLogin source in Nexla.
go_login_api.png

GoLogin

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the GoLogin connector tile from the list of available 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.

  3. In Nexla, GoLogin data sources can be created using pre-built endpoint templates, which expedite source setup for common GoLogin endpoints. Each template is designed specifically for the corresponding GoLogin endpoint, making data source setup easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    GoLogin sources can also be configured manually, allowing you to ingest data from GoLogin endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common GoLogin endpoints. Each template is designed specifically for the corresponding GoLogin endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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.

    • Sends a GET request to https://api.gologin.com/browser/v2 and returns a paginated list of browser profiles.
    • 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.

    • Sends a GET request to https://api.gologin.com/browser/history and returns history entries for a 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.

    • Sends a GET request to https://api.gologin.com/browser/cookies and returns the stored cookies for a profile.
    • 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.

    • Sends a GET request to https://api.gologin.com/folders and returns all profile folders in the account.
    • 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.

    • Sends a GET request to https://api.gologin.com/tags/all and returns all available tags.
    • 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.

    • Sends a GET request to https://api.gologin.com/user/metadata and returns user metadata as a single object.
    • 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.

    • Sends a GET request to https://api.gologin.com/user/balance and returns the current account balance as a single object.
    • 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.

    • Sends a GET request to https://api.gologin.com/timezone and returns the list of supported timezones.
    • 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.

    • Sends a GET request to https://api.gologin.com/browser/{'{id}'} and returns the full profile object as a single record.
    • 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.

    • Sends a GET request to https://api.gologin.com/fingerprint and returns a fingerprint configuration object as a single record.
    • 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.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

GoLogin sources can also be configured manually, allowing you to ingest data from GoLogin endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.

First, select the method that will be used for calls to the GoLogin API from the Method pulldown menu. The most common method for GoLogin data retrieval is:

  • GET: For retrieving browser profiles, proxies, workspace data, and account information.
  • POST: For creating new profiles or triggering profile actions.

API Endpoint URL​

  1. Enter the URL of the GoLogin API endpoint from which this source will fetch data in the Set API URL field. The GoLogin REST API base URL is https://api.gologin.com. Common endpoints include:

    • https://api.gologin.com/browser/v2 — Retrieve a paginated list of all browser profiles across workspaces.
    • https://api.gologin.com/browser/{profileId} — Retrieve data for a specific browser profile by its ID.
    • https://api.gologin.com/workspaces/{workspaceId}/profiles — Retrieve all profiles belonging to a specific workspace.
    • https://api.gologin.com/proxy — Retrieve saved proxy configurations.

    The GoLogin API returns paginated results for profile list endpoints. Use the page query parameter (e.g., https://api.gologin.com/browser/v2?page=1) to navigate through pages of results. Each page contains up to 30 profiles by default.

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Date/time macros are useful when filtering GoLogin profiles by creation or last-activity date, for example, when using a GoLogin API endpoint that supports date-based query parameters.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime
    • {now-1} – The datetime one time unit before the current datetime
    • {now+1} – The datetime one time unit after the current datetime
    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)​

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are useful when you need to iterate over a list of GoLogin profile IDs or workspace IDs retrieved from another Nexla source, constructing per-profile API calls dynamically.

  1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

  2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data​

Optional

If only a subset of the data returned by the GoLogin API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response.

For example, the GoLogin GET /browser/v2 endpoint returns a JSON object with a top-level profiles array containing the actual profile records alongside pagination metadata. By specifying the path to the profiles array, Nexla treats each element as a separate record.

Path to Data is important for GoLogin API responses, which typically wrap the records of interest in a named array (e.g., profiles, proxies). Without specifying the correct path, Nexla will treat the entire response object as a single record rather than expanding individual items.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For the profiles list endpoint (GET /browser/v2), enter $.profiles[*] to extract each profile as a separate record.

    • For the workspace profiles endpoint (GET /workspaces/{workspaceId}/profiles), enter the JSON path pointing to the profiles array in the response.

    Path to Data Example:

    If the GoLogin API response includes a top-level array named profiles containing the relevant data, the path to the response would be entered as $.profiles[*].

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the GoLogin API endpoint. Suggested data paths generated based on the content and format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. GoLogin API responses typically include pagination metadata (such as total, page, and totalPages) outside the profiles array. You can preserve this information by specifying its path.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field using JSON path notation (e.g., $.totalPages or $.total for GoLogin pagination fields).

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers and corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers may be required for specific GoLogin API operations.

    You do not need to include the Authorization header here, as Nexla automatically populates it using the Bearer token stored in the GoLogin credential. Common headers like Authorization are handled automatically based on your credential configuration.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched and displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, 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.