Split.io

Split.io (now part of Harness Feature Management & Experimentation) is a feature flagging and experimentation platform that lets teams roll out features progressively, target them to defined segments and traffic types, and measure their impact. Its Admin API exposes account resources such as workspaces, environments, feature flags, segments, and traffic types for programmatic management.

Power end-to-end data operations for your Split.io API with Nexla. Our bi-directional Split.io connector is purpose-built for Split.io, 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 Split.io or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Split.io 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 a Split.io credential, you need an Admin API key for your Split.io (Harness FME) account. The Admin API key authenticates all requests to the Admin API and is sent as a Bearer token in the Authorization header.

To create an Admin API key, follow these steps:

1. Sign in to your Split.io account with an administrator user.

2. Open Admin settings, then select API keys.

3. Click the action button and select Create API key.

4. Select Admin as the API key type. Admin keys are the key type accepted by the Admin API endpoints used by this connector.

5. Enter a descriptive name for the key (for example, "Nexla Integration"). Optionally restrict the key to the specific projects (workspaces) and environments it should have access to.

6. Create the key and copy its value immediately, as it may not be retrievable again after you leave the page.

Store the Admin API key securely, as it grants access to your Split.io resources based on the roles and restrictions you configured. Treat it as sensitive information, and revoke and regenerate it if it is ever exposed. Never place Admin or server-side keys in client-side JavaScript or mobile SDKs. For complete details, see the Split.io Admin API Authentication reference and the API keys guide.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Split.io Admin API key (Bearer token).

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 Split.io Admin API key in the API Key field. This is the Admin API key you obtained in Prerequisites. Nexla sends it as a Bearer token in the Authorization header for all API requests to the Split.io Admin API.

   The Admin API key grants access to your Split.io account resources based on the roles and project/environment restrictions configured when the key was created. If the key is compromised, revoke it in your Split.io Admin settings and generate a new one.

4. 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 Split.io connector tile, then select the credential that will be used to connect to Split.io, and click Next; or, create a new Split.io 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 Split.io 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.

[Rest API] List Users

Retrieve users. Use this template to ingest the users in your Split.io account for reporting, auditing, or synchronization with other systems.

• This endpoint returns the users accessible to your Admin API key. No additional parameters are required.

[Rest API] List Groups

Retrieve groups. Use this template to ingest the groups defined in your Split.io account.

• This endpoint returns the groups accessible to your Admin API key. No additional parameters are required.

[Rest API] List Change Requests

Retrieve change requests. Use this template to ingest the change requests submitted for approval in your Split.io account.

• This endpoint returns the change requests accessible to your Admin API key. No additional parameters are required.

[Rest API] List Workspaces

Retrieve workspaces. Use this template to ingest the workspaces (projects) in your Split.io account. The workspace ID returned here is required to configure several other Split.io source and destination endpoints.

• This endpoint returns the workspaces accessible to your Admin API key. No additional parameters are required.

[Rest API] List Flag Sets

Retrieve flag sets. Use this template to ingest the flag sets defined within a specific workspace.

• Enter the ID of the workspace to list flag sets for in the Workspace ID field. This value can be obtained from the List Workspaces endpoint.

[Rest API] List Segments

Retrieve segments. Use this template to ingest the segments defined within a specific workspace. Results are paginated, and Nexla automatically fetches subsequent pages.

• Enter the ID of the workspace to list segments for in the Workspace ID field. This value can be obtained from the List Workspaces endpoint.

[Rest API] List Segments Keys

Retrieve the keys belonging to a segment within a specific environment. Use this template to ingest the individual keys assigned to a segment.

• Enter the ID of the environment in the Environment ID field. This value can be obtained from the List Environments endpoint.
• Enter the name of the segment to list keys for in the Segment Name field. This value can be obtained from the List Segments endpoint.

[Rest API] List Rollout Statuses

Retrieve rollout statuses. Use this template to ingest the rollout statuses defined within a specific workspace.

• Enter the ID of the workspace to list rollout statuses for in the Workspace ID field. This value can be obtained from the List Workspaces endpoint.

[Rest API] List Environments

Retrieve environments. Use this template to ingest the environments defined within a specific workspace. Environment IDs are required to configure segment key operations.

• Enter the ID of the workspace to list environments for in the Workspace ID field. This value can be obtained from the List Workspaces endpoint.

[Rest API] List Traffic Types

Retrieve traffic types. Use this template to ingest the traffic types defined within a specific workspace.

• Enter the ID of the workspace to list traffic types for in the Workspace ID field. This value can be obtained from the List Workspaces endpoint.

[Rest API] List Feature Flags

Retrieve feature flags. Use this template to ingest the feature flags defined within a specific workspace for reporting, auditing, or synchronization.

• Enter the ID of the workspace to list feature flags for in the Workspace ID field. This value can be obtained from the List Workspaces endpoint.

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

Split.io data sources can also be manually configured to ingest data from any valid Split.io 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 Split.io 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 Split.io destination, and select the Send to Destination option from the menu. Select the Split.io connector from the list of available destination connectors, then select the credential that will be used to connect to Split.io, and click Next; or, create a new Split.io 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 Split.io 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.

[Rest API] Create Workspace

Create a new workspace (project) in your Split.io account. Use this template to provision workspaces from records in a Nexset.

• Each record from your Nexset is sent as a JSON request body to create a new workspace. The record should contain the workspace properties expected by the Split.io Admin API.

[Rest API] Create Environment

Create a new FME environment within a given workspace. Use this template to provision environments from records in a Nexset.

• Each record from your Nexset is sent as a JSON request body to create a new environment. The record should include the target workspace and the environment properties expected by the Split.io Admin API.

[Rest API] Create Feature Flag

Create a feature flag in a workspace for a given traffic type. Use this template to create feature flags from records in a Nexset.

• Each record from your Nexset is sent as a JSON request body to create a new feature flag. The record should include the target workspace and traffic type, along with the feature flag properties expected by the Split.io Admin API.

[Rest API] Create Segment

Create a segment in a workspace for a given traffic type. Use this template to create segments from records in a Nexset.

• Each record from your Nexset is sent as a JSON request body to create a new segment. The record should include the target workspace and traffic type, along with the segment properties expected by the Split.io Admin API.

[Rest API] Update Segment Keys

Replace the full key list for a segment in a given environment, supplied as a JSON array of keys. Use this template to synchronize segment membership from a Nexset.

• Each record from your Nexset is sent as a JSON request body to replace the segment's key list. Because this operation replaces the entire key list, ensure the payload contains the complete set of keys that should belong to the segment.

This endpoint replaces the full key list for the segment rather than appending to it. Any keys not included in the request will be removed from the segment in the target environment.

Manual configuration

Split.io destinations can also be manually configured to send data to any valid Split.io 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.

Split.io Admin API endpoints expect JSON payloads. For operations that target a specific workspace, environment, traffic type, or segment, include those identifiers in the request as required by the corresponding Split.io Admin API endpoint.

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 Split.io endpoint, open the destination resource menu, and select Activate.

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