Unleash

Unleash is a feature management and experimentation platform for controlling feature flags and A/B tests across applications. Its Admin API provides programmatic access to feature flags, projects, users, groups, roles, and API tokens, letting teams automate feature rollout and access management. Nexla connects to the Unleash Admin API to move this data in and out of your other systems.

Power end-to-end data operations for your Unleash API with Nexla. Our bi-directional Unleash connector is purpose-built for Unleash, 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 Unleash or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Unleash 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

Prerequisites

Before creating an Unleash credential, you need the base URL of your Unleash instance and an API token that authorizes calls to the Unleash Admin API. Nexla sends this token as a Bearer token in the Authorization header on every request.

To obtain your Unleash credentials, follow these steps:

1. Sign in to your Unleash instance with an account that has permission to manage the resources you plan to access.

2. Determine your Admin API base URL. This is the root URL of your Unleash instance, for example a value like https://api.unleash.example.com. Nexla appends the Admin API paths (such as /api/admin/...) to this base URL.

3. Create an API token to authenticate your requests. Unleash supports several token types for the Admin API:

   • Personal access token (PAT) — created from Profile > View profile settings > Personal API tokens. A PAT reflects the permissions of the user who created it and is useful for testing or scoped automation.
   • Service account token — created for a dedicated service account under Admin > Service accounts, recommended for long-lived integrations that should not be tied to an individual user.

4. Grant the token the roles and permissions required for your use case. Read-only operations (such as listing features, projects, or groups) require view permissions, while write operations (such as creating projects or feature flags) require the corresponding management permissions.

5. Copy the token value immediately after it is created, as Unleash returns the secret only once. Store it securely, as you will need it to configure your Nexla credential.

If a token is compromised, revoke it in Unleash and issue a new one. For detailed information about tokens, permissions, and available endpoints, see the Unleash API documentation.

Authenticate

Credentials required

Authenticate using Unleash API key passed as Bearer token in Authorization header.

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests
Base URL	Yes	No	Unleash API base URL (e.g., https://api.unleash.example.com)

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Unleash API token in the API Key Value field. Nexla sends this value as a Bearer token in the Authorization header on every request, so it must be kept confidential.

4. Enter your Unleash instance root URL in the Base URL field, for example a value like https://api.unleash.example.com. Nexla appends the Admin API paths to this base URL.

   If your API token is compromised, revoke it in Unleash and generate a new one. The token grants access to your Unleash resources based on its assigned permissions and should be treated as sensitive information.

   For detailed information about tokens, permissions, and available endpoints, see the Unleash API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Unleash connector tile, then select the credential that will be used to connect to the Unleash instance, and click Next; or, create a new Unleash credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Unleash 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.

List Features

Returns a list of all feature flags available in the Unleash instance.

Use this template to ingest every feature flag across your Unleash instance for reporting, auditing, or synchronization with other systems. For details on the response structure, see the Unleash API documentation.

List all projects

Returns a list of all projects, optionally filtered by archived status.

Use this template to retrieve the projects defined in your Unleash instance. For details on the response structure and available filters, see the Unleash API documentation.

List Licensed Users

Retrieves data for all licensed users in the Unleash instance.

Use this template to ingest licensed user data for access reviews or license reporting. For details on the response structure, see the Unleash API documentation.

Login

Authenticate a user with username and password credentials.

This endpoint authenticates a user with username and password credentials and returns the resulting session information. For details on the request and response structure, see the Unleash API documentation.

List Groups

Retrieve a list of all groups in the Unleash instance.

Use this template to ingest the user groups defined in your Unleash instance for access management and reporting. For details on the response structure, see the Unleash API documentation.

Get a list of roles

Retrieves all available roles in the Unleash instance.

Use this template to retrieve the roles configured in your Unleash instance. For details on the response structure, see the Unleash API documentation.

Search features

Searches and filters features with support for multiple criteria including query, project, state, and custom sorting.

Use this template to ingest a filtered subset of feature flags using search criteria such as query text, project, and state. For details on the supported parameters and response structure, see the Unleash API documentation.

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.

Manual configuration

Unleash data sources can also be manually configured to ingest data from any valid Unleash Admin API endpoint, including endpoints not covered by the pre-built templates, 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.

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

Use as a destination

Click the + icon on the Nexset that will be sent to the Unleash destination, and select the Send to Destination option from the menu. Select the Unleash connector from the list of available destination connectors, then select the credential that will be used to connect to the Unleash instance, and click Next; or, create a new Unleash credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Unleash endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create project

Creates a new project with the specified configuration.

Each record from your Nexset is sent as a request to create a new project with the specified configuration. Ensure your data includes the fields required by Unleash for project creation. For details on the request body format, see the Unleash API documentation.

Update project

Updates configuration settings for an existing project.

Each record from your Nexset is sent as a request to update the configuration settings of an existing project. Ensure your data identifies the target project and includes the fields to update. For details on the request body format, see the Unleash API documentation.

Set users and groups to roles in project

Assigns users and groups to roles within a specific project.

Each record from your Nexset is sent as a request to assign users and groups to roles within a specific project. Ensure your data identifies the project, users, groups, and target roles. For details on the request body format, see the Unleash API documentation.

Set roles for user in project

Assigns one or more roles to a user within a specific project.

Each record from your Nexset is sent as a request to assign one or more roles to a user within a specific project. Ensure your data identifies the project, user, and target roles. For details on the request body format, see the Unleash API documentation.

Remove project access for user

Removes all role assignments for a user from a specific project.

Each record from your Nexset is sent as a request to remove all role assignments for a user from a specific project. Ensure your data identifies the project and the user. For details on the request format, see the Unleash API documentation.

Set roles for group in project

Assigns one or more roles to a group within a specific project.

Each record from your Nexset is sent as a request to assign one or more roles to a group within a specific project. Ensure your data identifies the project, group, and target roles. For details on the request body format, see the Unleash API documentation.

Remove project access for group

Removes all role assignments for a group from a specific project.

Each record from your Nexset is sent as a request to remove all role assignments for a group from a specific project. Ensure your data identifies the project and the group. For details on the request format, see the Unleash API documentation.

Create Group

Create a new user group with specified settings and role assignments.

Each record from your Nexset is sent as a request to create a new user group with the specified settings and role assignments. Ensure your data includes the fields required by Unleash for group creation. For details on the request body format, see the Unleash API documentation.

Create a service account token

Creates a new API token for a service account with optional description and expiration date.

Each record from your Nexset is sent as a request to create a new API token for a service account, with an optional description and expiration date. Ensure your data identifies the service account and includes any required token settings. For details on the request body format, see the Unleash API documentation.

Update License

Sets a new Unleash instance license using a token.

Each record from your Nexset is sent as a request to set a new Unleash instance license using a token. Ensure your data includes a valid license token. For details on the request format, see the Unleash API documentation.

Create API token

Creates a new API token for authentication and programmatic access to Unleash.

Each record from your Nexset is sent as a request to create a new API token for authentication and programmatic access to Unleash. Ensure your data includes the token settings required by Unleash. For details on the request body format, see the Unleash API documentation.

Disable a feature flag

Disables a feature flag in a specific environment.

Each record from your Nexset is sent as a request to disable a feature flag in a specific environment. Ensure your data identifies the feature flag, project, and environment. For details on the request format, see the Unleash API documentation.

Create Feature Flag

Creates a new feature flag in the specified project.

Each record from your Nexset is sent as a request to create a new feature flag in the specified project. Ensure your data identifies the project and includes the fields required by Unleash for feature flag creation. For details on the request body format, see the Unleash API documentation.

Update Feature Flag

Updates properties of an existing feature flag in the project.

Each record from your Nexset is sent as a request to update properties of an existing feature flag in the project. Ensure your data identifies the project and feature flag and includes the fields to update. For details on the request body format, see the Unleash API documentation.

Manual configuration

Unleash destinations can also be manually configured to send data to any valid Unleash Admin API endpoint. 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.

Unleash Admin API endpoints typically expect JSON format for write operations. For update operations, include the identifier of the object to be updated in the endpoint path.

Save & activate

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 send the data to the configured Unleash endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Unleash endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.