Statsig

Statsig is a feature management and experimentation platform that lets teams ship feature gates, run A/B experiments, manage dynamic configs, and analyze product metrics. Its Console API exposes these resources over REST, enabling programmatic access to gates, experiments, dynamic configs, segments, metrics, and audit logs. Nexla connects to the Statsig Console API to ingest these resources into Nexsets and to create or update configuration objects in Statsig.

Power end-to-end data operations for your Statsig API with Nexla. Our bi-directional Statsig connector is purpose-built for Statsig, 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 Statsig or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Statsig 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 Statsig credential, you need a Statsig Console API key. Statsig authenticates every Console API request with this key, sent in the STATSIG-API-KEY request header. The Console API is served from https://statsigapi.net.

To obtain a Console API key, follow these steps:

1. Sign in to your Statsig account at console.statsig.com.

2. Open Project Settings and navigate to the API Keys (Keys & Environments) section.

3. Create a new Console API Key, or copy an existing one. Console API keys are project-scoped, so make sure you are in the project whose data you want to work with.

4. Copy the key value and store it securely. You will paste it into your Nexla credential.

The Console API key grants access to the resources in your Statsig project according to the key's permissions, so treat it as sensitive information. If a key is compromised, revoke it in Project Settings and generate a new one. For details on authentication, available resources, and request formats, see the Statsig Console API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key.

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 Statsig Console API key in the API Key field. This is the Console API key you obtained in Prerequisites. Nexla sends this key in the STATSIG-API-KEY header on every request to the Statsig Console API.

   Console API keys are project-scoped and grant access to the resources in the associated Statsig project. If the key is compromised, revoke it in your Statsig Project Settings and generate a new one.

   For detailed information about authentication and available resources, see the Statsig Console API documentation.

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 Statsig connector tile, then select the credential that will be used to connect to Statsig, and click Next; or, create a new Statsig 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 Statsig 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 the list of users in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Events Metrics

Retrieve the event-based metrics defined in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Metrics

Retrieve the metrics available in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Metrics Values

Retrieve computed values for the metrics in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Audit Logs

Retrieve audit log entries recording changes made in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Autotunes

Retrieve the autotune experiments configured in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Dynamic Configs

Retrieve the dynamic configs defined in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Dynamic Configs Versions

Retrieve the version history for the dynamic configs in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Dynamic Configs Rules

Retrieve the targeting rules defined on the dynamic configs in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Events

Retrieve the events tracked in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Experiments

Retrieve the experiments configured in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Gates

Retrieve the feature gates defined in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Gates Rules

Retrieve the targeting rules defined on the feature gates in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Holdouts

Retrieve the holdouts configured in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Ingestion Status

Retrieve the current ingestion status for your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Ingestion Runs

Retrieve the ingestion runs recorded for your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Layers

Retrieve the layers defined in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Segments

Retrieve the user segments defined in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Segments Ids

Retrieve the member IDs belonging to the user segments in your Statsig project.

For details on the response structure and available fields, see the Statsig Console API documentation.

[Rest API] List Tags

Retrieve the tags defined in your Statsig project.

For details on the response structure and available fields, see the Statsig Console 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

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

Create a new feature gate in your Statsig project from records in a Nexset.

• Each record from your Nexset is sent as a separate request to create a new feature gate. The request body should contain the gate definition in the format required by the Statsig Console API.

For details on the request body and required fields, see the Statsig Console API documentation.

[Rest API] Update Gate

Update an existing feature gate in your Statsig project, identified by its ID, using records from a Nexset.

• Each record from your Nexset is sent as a separate request to update the corresponding feature gate. Include the ID of the gate to update along with the fields to change in the request body.

For details on the request body and required fields, see the Statsig Console API documentation.

[Rest API] Create Experiment

Create a new experiment in your Statsig project from records in a Nexset.

• Each record from your Nexset is sent as a separate request to create a new experiment. The request body should contain the experiment definition in the format required by the Statsig Console API.

For details on the request body and required fields, see the Statsig Console API documentation.

[Rest API] Create Dynamic Config

Create a new dynamic config in your Statsig project from records in a Nexset.

• Each record from your Nexset is sent as a separate request to create a new dynamic config. The request body should contain the dynamic config definition in the format required by the Statsig Console API.

For details on the request body and required fields, see the Statsig Console API documentation.

[Rest API] Create Segment

Create a new user segment in your Statsig project from records in a Nexset.

• Each record from your Nexset is sent as a separate request to create a new user segment. The request body should contain the segment definition in the format required by the Statsig Console API.

For details on the request body and required fields, see the Statsig Console API documentation.

Manual configuration

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

Statsig Console API endpoints expect JSON request bodies. For update operations, include the ID of the object to be updated as required by the 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 Statsig endpoint, open the destination resource menu, and select Activate.

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