The Statsig connector lets your AI agent act in each user's Statsig account. Each user connects their own Statsig API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 96 tools.
- Tools
- 96
- What they doRead · write · destructive
- 53 · 35 · 853 read35 write8 destructive
- Users sign in with
- API key
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Statsig connection
In AgentKit > Connections, create a Statsig connection. The name you give it is the
connection_nameyour code passes. See Configure connections.Authorize a user and make your first call
quickstart.mts import { ScalekitClient } from '@scalekit-sdk/node'import 'dotenv/config'import { createInterface } from 'node:readline/promises'const scalekit = new ScalekitClient(process.env.SCALEKIT_ENVIRONMENT_URL,process.env.SCALEKIT_CLIENT_ID,process.env.SCALEKIT_CLIENT_SECRET,)const actions = scalekit.actionsconst connector = 'statsig'const identifier = 'user_123'// Generate an authorization link for the userconst { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })console.log('Authorize Statsig:', link)const rl = createInterface({ input: process.stdin, output: process.stdout })await rl.question('Press Enter after authorizing...')rl.close()// Make your first callconst result = await actions.executeTool({connector,identifier,toolName: 'statsig_audit_overrides',toolInput: {},})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_dotenv()scalekit_client = ScalekitClient(env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),client_id=os.getenv("SCALEKIT_CLIENT_ID"),client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),)actions = scalekit_client.actionsconnection_name = "statsig"identifier = "user_123"# Generate an authorization link for the userlink_response = actions.get_authorization_link(connection_name=connection_name,identifier=identifier,)print("Authorize Statsig:", link_response.link)input("Press Enter after authorizing...")# Make your first callresult = actions.execute_tool(tool_input={},tool_name="statsig_audit_overrides",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user opens the link once and enters their Statsig credentials there. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_toolstatsig_audit_overridesList the gates, experiments and layers that have overrides, optionally narrowed to one unit ID.Read-onlyAudit Overrides
List the gates, experiments and layers that have overrides, optionally narrowed to one unit ID. Returns each entity with overrides and the overridden IDs and groups. Use statsig_audit_overrides to find every override affecting a user. Use statsig_get_gate_overrides or statsig_get_experiment_overrides for one entity.
Inputs
id_typestring- Unit ID type that unit_id refers to, such as userID or stableID. Example: userID.
unit_idstring- Unit ID to audit. When set, only entities that override this ID are returned. Example: user_123.
statsig_get_alertGet one topline metric alert by ID.Read-onlyGet Topline Alert
Get one topline metric alert by ID. Returns the alert's name, metric, condition, thresholds, schedule, subscribers and mute status. Use statsig_get_alert for one known alert. Use statsig_list_alerts to find alert IDs.
Inputs
alert_idstringrequired- ID of the topline alert, as returned by statsig_list_alerts. Example: 6Yt2cVb8kq1LmNoPqRsTuv.
statsig_get_dashboardGet one dashboard by ID.Read-onlyGet Dashboard
Get one dashboard by ID. Returns the dashboard's name, description and widget definitions. Use statsig_get_dashboard for one known dashboard. Use statsig_list_dashboards to find dashboard IDs.
Inputs
dashboard_idstringrequired- ID of the dashboard, as returned by statsig_list_dashboards. Example: 3kLmN8pQrS2tUvWxYz1AbC.
statsig_get_dynamic_configGet one dynamic config by ID.Read-onlyGet Dynamic Config
Get one dynamic config by ID. Returns the config's name, description, isEnabled, defaultValue, rules with return values, schema, tags and owner. Use statsig_get_dynamic_config for one known config. Use statsig_list_dynamic_configs to find config IDs.
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
statsig_get_eventList recently logged events for one event name.Read-onlyGet Recent Events by Name
List recently logged events for one event name. Covers a limited rolling window, not full history. Returns recent records for that event with value, metadata, user and timestamp, plus pagination info. Use statsig_get_event to inspect one event's payloads. Use statsig_list_events for all events.
Inputs
event_namestringrequired- Name of the logged event. Example: add_to_cart.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_get_experimentGet one experiment by ID.Read-onlyGet Experiment
Get one experiment by ID. Returns the experiment's full setup: name, hypothesis, status, groups with parameter values, allocation, layer, targeting gate, metrics, statistical settings and dates. Use statsig_get_experiment for one known experiment. Use statsig_get_experiment_pulse_results for its metric results.
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
statsig_get_experiment_cumulative_exposuresGet cumulative exposure counts for an experiment's groups over time.Read-onlyGet Experiment Cumulative Exposures
Get cumulative exposure counts for an experiment's groups over time. Returns daily cumulative exposure counts per group. Use statsig_get_experiment_cumulative_exposures to check enrollment balance. Use statsig_get_experiment_pulse_results for metric impact.
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
statsig_get_experiment_overridesGet the overrides that force users, gates or segments into specific groups of an experiment.Read-onlyGet Experiment Overrides
Get the overrides that force users, gates or segments into specific groups of an experiment. Returns the gate and segment overrides and the user ID overrides with their target groups. Use statsig_get_experiment_overrides to see forced assignments. Use statsig_update_experiment_overrides to add them.
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
statsig_get_experiment_pulse_resultsGet Pulse metric results comparing a test group with a control group (beta endpoint).Read-onlyGet Experiment Pulse Results
Get Pulse metric results comparing a test group with a control group (beta endpoint). Returns per-metric lifts, confidence intervals and statistical significance for the two groups. Use statsig_get_experiment_pulse_results to read an experiment's outcome. Use statsig_get_experiment_cumulative_exposures for exposure counts.
Inputs
control_group_idstringrequired- ID of the control group, from the experiment's groups. Example: Control.
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
test_group_idstringrequired- ID of the test group to compare, from the experiment's groups. Example: Test.
confidencestring- Confidence interval percentage between 0 and 100. Example: 95.
cupedstring- Whether to apply CUPED variance reduction. Allowed values: true, false. Example: true.
datestring- Date of the results to read, in YYYY-MM-DD format. Defaults to the latest. Example: 2026-10-01.
statsig_get_gateGet one feature gate by ID.Read-onlyGet Feature Gate
Get one feature gate by ID. Returns the gate's full definition: name, description, isEnabled, status, idType, rules with conditions and pass percentages, tags, target apps and owner. Use statsig_get_gate for one known gate. Use statsig_list_gates to find gate IDs.
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse
statsig_get_gate_checksCheck whether a feature gate has been evaluated in production recently.Read-onlyGet Feature Gate Check Activity
Check whether a feature gate has been evaluated in production recently. Returns has_production_checks_in_last_7_days. Use statsig_get_gate_checks before archiving or deleting a gate to confirm it is no longer checked in code.
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
statsig_get_gate_overridesGet the user and custom ID overrides set on a feature gate.Read-onlyGet Feature Gate Overrides
Get the user and custom ID overrides set on a feature gate. Returns passingUserIDs, failingUserIDs, passingCustomIDs, failingCustomIDs and per-environment overrides. Use statsig_get_gate_overrides to see who is forced to pass or fail. Use statsig_add_gate_overrides to add IDs.
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
statsig_get_gate_rule_pulse_resultsGet Pulse metric lift results for one rule of a feature gate.Read-onlyGet Feature Gate Rule Pulse Results
Get Pulse metric lift results for one rule of a feature gate. Returns the metric impact of passing versus failing the rule, with confidence intervals. Use statsig_get_gate_rule_pulse_results to measure a rollout's impact. Use statsig_get_experiment_pulse_results for experiments.
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
rule_idstringrequired- ID of the rule, as returned by the rules list for this entity. Example: 4XnxkZmGpqbV9lnT3ACJQo.
confidencestring- Confidence interval percentage between 0 and 100. Example: 95.
cupedstring- Whether to apply CUPED variance reduction. Allowed values: true, false. Example: true.
statsig_get_holdoutGet one holdout by ID.Read-onlyGet Holdout
Get one holdout by ID. Returns the holdout's name, description, isEnabled, passPercentage, isGlobal, and the gates, experiments and layers it applies to. Use statsig_get_holdout for one known holdout. Use statsig_list_holdouts to find holdout IDs.
Inputs
holdout_idstringrequired- ID of the holdout, as returned by statsig_list_holdouts. Example: global_holdout_q4.
statsig_get_layerGet one layer by ID.Read-onlyGet Layer
Get one layer by ID. Returns the layer's name, description, idType, parameters with default values, target apps and experiments. Use statsig_get_layer for one known layer. Use statsig_list_layer_experiments to list the experiments in it.
Inputs
layer_idstringrequired- ID of the layer, as returned by statsig_list_layers. Example: checkout_layer.
statsig_get_metricGet one metric's definition by ID.Read-onlyGet Metric Definition
Get one metric's definition by ID. Returns the metric's name, type, description, directionality, events or component metrics it is computed from, unit types and tags. Use statsig_get_metric for how a metric is defined. Use statsig_get_metric_value for its value on a date.
Inputs
metric_idstringrequired- ID of the metric in the form <metric name>::<metric type>, as returned by statsig_list_metrics. Example: add_to_cart::event_count.
statsig_get_metric_valueGet the value of one metric on one date.Read-onlyGet Metric Value
Get the value of one metric on one date. Returns the metric's value records for that date. Use statsig_get_metric_value for one metric. Use statsig_list_metric_values for every metric on a date.
Inputs
datestringrequired- Date to read, in YYYY-MM-DD format. Example: 2026-10-01.
metric_idstringrequired- ID of the metric in the form <metric name>::<metric type>, as returned by statsig_list_metrics. Example: add_to_cart::event_count.
statsig_get_param_storeGet one param store by name.Read-onlyGet Param Store
Get one param store by name. Returns the store's description and each parameter with its type and the gate, config, experiment or static value it reads from. Use statsig_get_param_store for one known store. Use statsig_list_param_stores to find store names.
Inputs
param_store_namestringrequired- Name of the param store, as returned by statsig_list_param_stores. Example: mobile_app_params.
statsig_get_projectGet information about the Statsig project the API key belongs to.Read-onlyGet Project
Get information about the Statsig project the API key belongs to. Returns the project's id, name and settings summary. Use statsig_get_project to confirm which project the connection targets. Use statsig_list_environments for its environments.
Inputs
This tool takes no inputs.
statsig_get_release_pipelineGet one release pipeline by ID.Read-onlyGet Release Pipeline
Get one release pipeline by ID. Returns the pipeline's name, description and phases with their environments, approvals and wait times. Use statsig_get_release_pipeline for one known pipeline. Use statsig_list_release_pipelines to find pipeline IDs.
Inputs
release_pipeline_idstringrequired- ID of the release pipeline, as returned by statsig_list_release_pipelines. Example: 7AbCdEfGhIjKlMnOpQrStU.
statsig_get_segmentGet one segment by ID.Read-onlyGet Segment
Get one segment by ID. Returns the segment's name, description, type, idType, rules (for rule-based segments), ID count (for ID lists) and tags. Use statsig_get_segment for one known segment. Use statsig_list_segment_ids to read the IDs in an ID-list segment.
Inputs
segment_idstringrequired- ID of the segment, as returned by statsig_list_segments. Example: beta_testers.
statsig_get_userGet one project member by email address.Read-onlyGet User by Email
Get one project member by email address. Returns the user's email, name and role. Use statsig_get_user to look up one member. Use statsig_list_users to browse all members.
Inputs
emailstringrequired- Email address of the Statsig console user. Example: jane@example.com.
statsig_list_alertsList topline metric alerts in the Statsig project.Read-onlyList Topline Alerts
List topline metric alerts in the Statsig project. Returns each alert's id, name, metric, condition, thresholds and mute status, plus pagination info. Use statsig_list_alerts to browse alerts. Use statsig_get_alert for one alert's configuration.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_audit_logsList audit log entries for changes made in the Statsig project, optionally filtered by entity, action or date range.Read-onlyList Audit Logs
List audit log entries for changes made in the Statsig project, optionally filtered by entity, action or date range. Returns each entry's id, entity name, action type, change log, date, time and the user who made the change, plus pagination info. Use statsig_list_audit_logs for project-wide change history. Use statsig_list_gate_versions or statsig_list_experiment_versions for one entity.
Inputs
action_typestring- Only return entries with this action type. Example: gate_update.
end_datestring- Only return entries on or before this date (YYYY-MM-DD). Defaults to today. Example: 2026-09-30.
entity_idstring- Only return entries for this entity ID (a gate, config, experiment or other entity). Example: new_checkout_flow.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
sort_keystring- Field to sort by. Allowed values: id, name, changeLog, actionType, date, time, updatedBy, updatedByUserID. Example: date.one of
idnamechangeLogactionTypedatetimeupdatedByupdatedByUserID sort_orderstring- Sort direction. Allowed values: asc, desc. Example: desc.one of
ascdesc start_datestring- Only return entries on or after this date (YYYY-MM-DD). Defaults to 90 days before end_date. Example: 2026-09-01.
statsig_list_dashboardsList dashboards in the Statsig project, optionally filtered by a partial name match.Read-onlyList Dashboards
List dashboards in the Statsig project, optionally filtered by a partial name match. Returns each dashboard's id, name, description and owner, plus pagination info. Use statsig_list_dashboards to find dashboards. Use statsig_get_dashboard for one dashboard's widgets.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
searchstring- Partial dashboard name to match. Example: Checkout.
statsig_list_dynamic_config_rulesList the targeting rules of a dynamic config.Read-onlyList Dynamic Config Rules
List the targeting rules of a dynamic config. Returns each rule's id, name, passPercentage, conditions and returnValue. Use statsig_list_dynamic_config_rules to get rule IDs before statsig_update_dynamic_config_rule or statsig_delete_dynamic_config_rule.
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
statsig_list_dynamic_config_versionsList the saved versions of a dynamic config, optionally limited to a date range.Read-onlyList Dynamic Config Versions
List the saved versions of a dynamic config, optionally limited to a date range. Returns each version's number, modification time, modifier and the config definition at that version. Use statsig_list_dynamic_config_versions to see how a config changed over time.
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
end_datestring- Only include items on or before this date (inclusive), in YYYY-MM-DD format. Example: 2026-09-30.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
start_datestring- Only include items on or after this date, in YYYY-MM-DD format. Example: 2026-09-01.
statsig_list_dynamic_configsList dynamic configs in the Statsig project, with optional filters for type, staleness, team, target app, tag and creator.Read-onlyList Dynamic Configs
List dynamic configs in the Statsig project, with optional filters for type, staleness, team, target app, tag and creator. Returns each config's id, name, description, isEnabled, default value, rules summary and tags, plus pagination info. Use statsig_list_dynamic_configs to browse configs. Use statsig_get_dynamic_config to read one config's rules and values.
Inputs
creator_idstring- Only return entities created by the user with this Statsig user ID. Example: 5rfuqoxLIYTscuSaaCOlB8.
creator_namestring- Only return entities created by the user with this name. Example: Jane Doe.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
release_pipeline_idstring- Only return configs using this release pipeline ID. Example: 7AbCdEfGhIjKlMnOpQrStU.
tagstring- Only return configs with this tag name. Example: pricing.
target_app_idstring- Only return configs scoped to this target app ID. Example: web_app.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
typestring- Only return configs of this lifecycle type. STALE configs are flagged by Statsig's nightly stale detection. Allowed values: TEMPORARY, PERMANENT, STALE. Example: PERMANENT.one of
TEMPORARYPERMANENTSTALE type_reasonstring- Only return configs with this stale classification reason. Allowed values: NONE, STALE_PROBABLY_DEAD_CHECK, STALE_NO_RULES, STALE_PROBABLY_FORGOTTEN, STALE_PROBABLY_LAUNCHED, STALE_PROBABLY_UNLAUNCHED.one of
NONESTALE_PROBABLY_DEAD_CHECKSTALE_NO_RULESSTALE_PROBABLY_FORGOTTENSTALE_PROBABLY_LAUNCHEDSTALE_PROBABLY_UNLAUNCHED
statsig_list_environmentsList the environments defined in the Statsig project.Read-onlyList Environments
List the environments defined in the Statsig project. Returns each environment's name, id, production flag and review requirements. Use statsig_list_environments to find environment names for rules and overrides.
Inputs
This tool takes no inputs.
statsig_list_event_metricsList the metrics computed from an event name.Read-onlyList Metrics for Event
List the metrics computed from an event name. Returns each metric's id, name, type and definition, plus pagination info. Use statsig_list_event_metrics to see which metrics an event feeds. Use statsig_list_metrics to search all metrics.
Inputs
event_namestringrequired- Name of the logged event. Example: add_to_cart.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_eventsList recently logged events across all event names.Read-onlyList Recent Events
List recently logged events across all event names. Covers a limited rolling window, not full history. Returns recent event records with event name, value, metadata, user and timestamp, plus pagination info. Use statsig_list_events to see what is being logged. Use statsig_get_event for one event name.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_experiment_versionsList the saved versions of an experiment, optionally limited to a date range.Read-onlyList Experiment Versions
List the saved versions of an experiment, optionally limited to a date range. Returns each version's number, modification time, modifier and the experiment definition at that version. Use statsig_list_experiment_versions to see how an experiment's setup changed.
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
end_datestring- Only include items on or before this date (inclusive), in YYYY-MM-DD format. Example: 2026-09-30.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
start_datestring- Only include items on or after this date, in YYYY-MM-DD format. Example: 2026-09-01.
statsig_list_experimentsList experiments in the Statsig project, with optional filters for status, layer, unit type, team, creation date, type and tag.Read-onlyList Experiments
List experiments in the Statsig project, with optional filters for status, layer, unit type, team, creation date, type and tag. Returns each experiment's id, name, description, status, hypothesis, groups, allocation, layer and metrics, plus pagination info. Use statsig_list_experiments to browse or filter experiments. Use statsig_get_experiment for one experiment's full setup.
Inputs
created_end_datestring- Only return experiments created on or before this date (YYYY-MM-DD). Example: 2026-09-30.
created_start_datestring- Only return experiments created on or after this date (YYYY-MM-DD). Example: 2026-09-01.
creator_idstring- Only return entities created by the user with this Statsig user ID. Example: 5rfuqoxLIYTscuSaaCOlB8.
creator_namestring- Only return entities created by the user with this name. Example: Jane Doe.
experiment_typestring- Only return experiments of this type. Allowed values: BASE, GEO, SWITCHBACK, PROMPT, SIDECAR, GRID_SEARCH. Example: BASE.one of
BASEGEOSWITCHBACKPROMPTSIDECARGRID_SEARCH fieldsstring- Comma-separated top-level fields to return, to trim the response. id is always included. Example: id,name,status,groups.
id_typestring- Only return experiments randomized on this unit ID type. Example: userID.
idsstring- Comma-separated experiment IDs to fetch in one request (max 100). Example: checkout_button_color_test,onboarding_copy_test.
layer_idstring- Only return experiments in this layer ID. Example: checkout_layer.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
staleboolean- Set true to return only stale experiments. Example: true.
statusstring- Only return experiments with this status. Allowed values: active, setup, decision_made, abandoned, archived, experiment_stopped, assignment_stopped. Example: active.one of
activesetupdecision_madeabandonedarchivedexperiment_stoppedassignment_stopped tagstring- Only return experiments with this tag name. Example: checkout.
target_app_idstring- Only return experiments scoped to this target app ID. Example: web_app.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
statsig_list_gate_rulesList the targeting rules of a feature gate.Read-onlyList Feature Gate Rules
List the targeting rules of a feature gate. Returns each rule's id, name, passPercentage, conditions and environments. Use statsig_list_gate_rules to get rule IDs before statsig_update_gate_rule or statsig_delete_gate_rule.
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
statsig_list_gate_versionsList the saved versions of a feature gate, newest first, optionally limited to a date range.Read-onlyList Feature Gate Versions
List the saved versions of a feature gate, newest first, optionally limited to a date range. Returns each version's number, modification time, modifier and the gate definition at that version. Use statsig_list_gate_versions to see how a gate changed. Use statsig_list_audit_logs for project-wide change history.
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
end_datestring- Only include items on or before this date (inclusive), in YYYY-MM-DD format. Example: 2026-09-30.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
start_datestring- Only include items on or after this date, in YYYY-MM-DD format. Example: 2026-09-01.
statsig_list_gatesList feature gates in the Statsig project, with optional filters for type, staleness, team, target app, tag and creator.Read-onlyList Feature Gates
List feature gates in the Statsig project, with optional filters for type, staleness, team, target app, tag and creator. Returns each gate's id, name, description, status, type, rules summary, tags and owner, plus pagination info. Use statsig_list_gates to browse or filter gates. Use statsig_get_gate to read one gate's full definition and rules.
Inputs
creator_idstring- Only return entities created by the user with this Statsig user ID. Example: 5rfuqoxLIYTscuSaaCOlB8.
creator_namestring- Only return entities created by the user with this name. Example: Jane Doe.
id_typestring- Only return gates that evaluate on this unit ID type. Example: userID.
include_archivedstring- Set to "true" to include archived gates. Allowed values: true, false. Example: true.one of
truefalse limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
tagstring- Only return gates with this tag name. Example: checkout.
target_app_idstring- Only return gates scoped to this target app ID. Example: web_app.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
typestring- Only return gates of this lifecycle type. STALE gates are flagged by Statsig's nightly stale detection. Allowed values: TEMPORARY, PERMANENT, STALE, TEMPLATE. Example: TEMPORARY.one of
TEMPORARYPERMANENTSTALETEMPLATE type_reasonstring- Only return gates with this stale classification reason. Allowed values: NONE, STALE_PROBABLY_LAUNCHED, STALE_PROBABLY_UNLAUNCHED, STALE_PROBABLY_FORGOTTEN, STALE_NO_RULES, STALE_PROBABLY_DEAD_CHECK, STALE_EMPTY_CHECKS, STALE_ALL_TRUE, STALE_ALL_FALSE.one of
NONESTALE_PROBABLY_LAUNCHEDSTALE_PROBABLY_UNLAUNCHEDSTALE_PROBABLY_FORGOTTENSTALE_NO_RULESSTALE_PROBABLY_DEAD_CHECKSTALE_EMPTY_CHECKSSTALE_ALL_TRUESTALE_ALL_FALSE
statsig_list_holdoutsList holdouts (groups of users kept out of new features to measure cumulative impact).Read-onlyList Holdouts
List holdouts (groups of users kept out of new features to measure cumulative impact). Returns each holdout's id, name, description, passPercentage, attached gates, experiments and layers, plus pagination info. Use statsig_list_holdouts to browse holdouts. Use statsig_get_holdout for one holdout.
Inputs
creator_idstring- Only return entities created by the user with this Statsig user ID. Example: 5rfuqoxLIYTscuSaaCOlB8.
creator_namestring- Only return entities created by the user with this name. Example: Jane Doe.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
tagstring- Only return holdouts with this tag name. Example: q4.
statsig_list_layer_experimentsList the experiments that belong to a layer.Read-onlyList Layer Experiments
List the experiments that belong to a layer. Returns each experiment's id, name, status, allocation and groups, plus pagination info. Use statsig_list_layer_experiments to see what shares a layer. Use statsig_list_experiments to search all experiments.
Inputs
layer_idstringrequired- ID of the layer, as returned by statsig_list_layers. Example: checkout_layer.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_layersList layers in the Statsig project.Read-onlyList Layers
List layers in the Statsig project. Returns each layer's id, name, description, idType, parameters and experiments, plus pagination info. Use statsig_list_layers to browse layers. Use statsig_get_layer for one layer's parameters.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_metric_experimentsList the experiments that use a given metric.Read-onlyList Experiments Using Metric
List the experiments that use a given metric. Returns each experiment's id, name, status and setup, plus pagination info. Use statsig_list_metric_experiments to see where a metric is measured. Use statsig_list_experiments to search all experiments.
Inputs
metric_idstringrequired- ID of the metric in the form <metric name>::<metric type>, as returned by statsig_list_metrics. Example: add_to_cart::event_count.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statusstring- Only return experiments with this status. Allowed values: active, setup, decision_made, abandoned, archived, experiment_stopped, assignment_stopped. Example: active.one of
activesetupdecision_madeabandonedarchivedexperiment_stoppedassignment_stopped
statsig_list_metric_sourcesList metric sources (warehouse tables or queries that metrics are computed from).Read-onlyList Metric Sources
List metric sources (warehouse tables or queries that metrics are computed from). Returns each source's name, description, SQL or table, ID type mappings and owner, plus pagination info. Use statsig_list_metric_sources to see where metric data comes from. Use statsig_list_metrics for the metrics themselves.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_metric_valuesList metric values for one date, optionally filtered to a metric name or type.Read-onlyList Metric Values
List metric values for one date, optionally filtered to a metric name or type. Returns each metric's name, type and value for the date, plus pagination info. Use statsig_list_metric_values for a daily snapshot of many metrics. Use statsig_get_metric_value for one known metric.
Inputs
datestringrequired- Date to read, in YYYY-MM-DD format. Example: 2026-10-01.
limitinteger- Number of results to return per page. Example: 20.
metric_namestring- Only return values for this metric name. Example: add_to_cart.
metric_typestring- Only return values for this metric type. Example: event_count.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_metricsList metric definitions in the Statsig project, optionally filtered by tag or search text.Read-onlyList Metrics
List metric definitions in the Statsig project, optionally filtered by tag or search text. Returns each metric's id (name::type), name, type, description, directionality, unit types, tags and verification status, plus pagination info. Use statsig_list_metrics to find metric IDs and names. Use statsig_get_metric for one metric's definition, or statsig_list_metric_values for daily values.
Inputs
filtersstring- Plain search text to match metrics against. Example: checkout.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
show_hidden_metricsstring- Set to "true" to include hidden metrics. Allowed values: true, false. Example: false.one of
truefalse tagstring- Only return metrics with this tag ID (see statsig_list_tags). Example: revenue.
statsig_list_param_storesList param stores, which group parameters whose values come from gates, configs, experiments or static values.Read-onlyList Param Stores
List param stores, which group parameters whose values come from gates, configs, experiments or static values. Returns each param store's name, description and parameters, plus pagination info. Use statsig_list_param_stores to browse param stores. Use statsig_get_param_store for one store's parameters.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_release_pipeline_triggersList release pipeline runs (triggers), optionally filtered by pipeline, gate, dynamic config, status or creation date.Read-onlyList Release Pipeline Triggers
List release pipeline runs (triggers), optionally filtered by pipeline, gate, dynamic config, status or creation date. Returns each trigger's id, pipeline, entity, status, current phase and timestamps, plus pagination info. Use statsig_list_release_pipeline_triggers to track rollouts in progress. Use statsig_list_release_pipelines for pipeline definitions.
Inputs
dynamic_config_idstring- Only return triggers for this dynamic config ID. Example: pricing_page_config.
end_datestring- Only return triggers created on or before this date (YYYY-MM-DD, UTC). Example: 2026-09-30.
gate_idstring- Only return triggers for this feature gate ID. Example: new_checkout_flow.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
release_pipeline_idstring- Only return triggers of this release pipeline ID. Example: 7AbCdEfGhIjKlMnOpQrStU.
start_datestring- Only return triggers created on or after this date (YYYY-MM-DD, UTC). Example: 2026-09-01.
statusstring- Only return triggers with this status. Allowed values: IN_PROGRESS, PAUSED, ABORTED, COMPLETED. Example: IN_PROGRESS.one of
IN_PROGRESSPAUSEDABORTEDCOMPLETED
statsig_list_release_pipelinesList release pipelines, which roll gate and config changes through environments in phases.Read-onlyList Release Pipelines
List release pipelines, which roll gate and config changes through environments in phases. Returns each pipeline's id, name, description and phases, plus pagination info. Use statsig_list_release_pipelines to browse pipelines. Use statsig_list_release_pipeline_triggers to see runs in progress.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_segment_idsList the IDs in an ID-list segment.Read-onlyList Segment IDs
List the IDs in an ID-list segment. Statsig rate-limits this endpoint. Returns the list name, ID count and a page of IDs, plus pagination info. Use statsig_list_segment_ids to read members of an ID-list segment. Use statsig_get_segment for the segment's settings.
Inputs
segment_idstringrequired- ID of the segment, as returned by statsig_list_segments. Example: beta_testers.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_segmentsList segments (reusable user groups) in the Statsig project.Read-onlyList Segments
List segments (reusable user groups) in the Statsig project. Returns each segment's id, name, description, type, idType, rules or ID count, and tags, plus pagination info. Use statsig_list_segments to browse segments. Use statsig_get_segment for one segment's rules.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_target_appsList target apps, which scope which SDK keys can evaluate a gate, config or experiment.Read-onlyList Target Apps
List target apps, which scope which SDK keys can evaluate a gate, config or experiment. Returns each target app's id, name, description and attached entities, plus pagination info. Use statsig_list_target_apps to find names for the target_apps fields.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_teamsList teams in the Statsig project (Enterprise).Read-onlyList Teams
List teams in the Statsig project (Enterprise). Returns each team's id, name, description, members and admins, plus pagination info. Use statsig_list_teams to find team IDs for the team_id filters and fields.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_unit_id_typesList the unit ID types (such as userID, stableID and custom IDs) defined in the project.Read-onlyList Unit ID Types
List the unit ID types (such as userID, stableID and custom IDs) defined in the project. Returns each unit type's name and description, plus pagination info. Use statsig_list_unit_id_types to find valid values for id_type fields.
Inputs
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_list_usersList members of the Statsig project.Read-onlyList Users
List members of the Statsig project. Returns each user's email, first and last name and role, plus pagination info. Use statsig_list_users to browse members. Use statsig_get_user to look up one member by email.
Inputs
include_stale_membersboolean- Set true to also return stale membership records. Defaults to false (current members only). Example: false.
limitinteger- Number of results to return per page. Example: 20.
pageinteger- Page number to return, starting at 1. Use with limit to page through results. Example: 2.
statsig_abandon_experimentAbandon an experiment, stopping it without shipping any group.WriteAbandon Experiment
Abandon an experiment, stopping it without shipping any group. Returns a confirmation message. Use statsig_abandon_experiment to stop a failed or invalid test. Use statsig_ship_experiment to launch a winning group.
- Idempotent
Inputs
decision_reasonstringrequired- Reason for abandoning, recorded on the experiment. Example: Logging bug invalidated the results.
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
statsig_add_gate_overridesAdd IDs that are forced to pass or fail a feature gate, regardless of its rules.WriteAdd Feature Gate Overrides
Add IDs that are forced to pass or fail a feature gate, regardless of its rules. Existing overrides are kept. Returns the gate's full override lists after the change. Use statsig_add_gate_overrides to force specific users in or out. Use statsig_get_gate_overrides to read current overrides.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
environment_overridesarray- Alternative to the ID lists: per-environment overrides as a JSON array. Each entry names an environment (or null for all), a unitID type, and passingIDs and failingIDs arrays. Example: [{"environment": "staging", "unitID": "userID", "passingIDs": ["user_123"], "failingIDs": []}]
failing_custom_idsarray- Custom unit IDs forced to fail the gate, as a JSON array. Example: ["company_99"].
failing_user_idsarray- User IDs forced to fail the gate, as a JSON array. Send together with passing_user_ids (use [] for none). Example: ["user_456"].
passing_custom_idsarray- Custom unit IDs forced to pass the gate, as a JSON array. Example: ["company_42"].
passing_user_idsarray- User IDs forced to pass the gate, as a JSON array. Send together with failing_user_ids (use [] for none). Example: ["user_123"].
statsig_add_gate_ruleAdd one targeting rule to a feature gate, keeping its existing rules.WriteAdd Feature Gate Rule
Add one targeting rule to a feature gate, keeping its existing rules. Returns the updated gate definition with all rules. Use statsig_add_gate_rule to append a rule. Use statsig_update_gate_rule to change an existing rule.
Inputs
conditionsarrayrequired- Conditions a user must meet, as a JSON array. Each condition has a type (for example public, user_id, email, country, custom_field, passes_gate) and, for most types, an operator (any, none, str_contains_any, gt, version_gt, and so on) and a targetValue. Use [{"type": "public"}] to match everyone. Example: [{"type": "country", "operator": "any", "targetValue": ["US", "CA"]}]
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
namestringrequired- Name of the new rule. Example: Internal users.
pass_percentagenumberrequired- Percentage (0-100) of users matching the conditions who pass the gate. Example: 100.
environmentsarray- Environments this rule applies in, as a JSON array of environment names. Omit to apply in all environments. Example: ["production"].
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse
statsig_add_segment_idsAdd IDs to an ID-list segment.WriteAdd IDs to Segment
Add IDs to an ID-list segment. Statsig rate-limits this endpoint (about 12 requests per 10 seconds). Returns a confirmation message. Use statsig_add_segment_ids to grow an ID list. Use statsig_remove_segment_ids to take IDs out.
- Idempotent
Inputs
idsarrayrequired- IDs to add, as a JSON array of strings. Example: ["user_123", "user_456"].
segment_idstringrequired- ID of the segment, as returned by statsig_list_segments. Example: beta_testers.
statsig_archive_dynamic_configArchive a dynamic config, retiring it while keeping its history.WriteArchive Dynamic Config
Archive a dynamic config, retiring it while keeping its history. Returns the archived dynamic config. Use statsig_archive_dynamic_config to retire a config. Use statsig_delete_dynamic_config to remove it permanently.
- Idempotent
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
archive_reasonstring- Reason for archiving, shown in the audit history. Example: Feature fully launched and code removed.
force_archiveboolean- Set true to archive even when other entities still reference this one. Example: false.
statsig_archive_experimentArchive an experiment, retiring it while keeping its results.WriteArchive Experiment
Archive an experiment, retiring it while keeping its results. Returns a confirmation message. Use statsig_archive_experiment to retire a finished experiment. Use statsig_delete_experiment to remove it permanently.
- Idempotent
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
archive_reasonstring- Reason for archiving the experiment. Example: Decision shipped and code cleaned up.
statsig_archive_gateArchive a feature gate, retiring it while keeping its history.WriteArchive Feature Gate
Archive a feature gate, retiring it while keeping its history. Returns the archived gate definition. Use statsig_archive_gate to retire a gate. Use statsig_unarchive_gate to restore it, or statsig_delete_gate to remove it permanently.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
archive_reasonstring- Reason for archiving, shown in the audit history. Example: Feature fully launched and code removed.
force_archiveboolean- Set true to archive even when other entities still reference this one. Example: false.
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse
statsig_archive_segmentArchive a segment, retiring it while keeping its history.WriteArchive Segment
Archive a segment, retiring it while keeping its history. Returns the archived segment. Use statsig_archive_segment to retire a segment. Use statsig_delete_segment to remove it permanently.
- Idempotent
Inputs
segment_idstringrequired- ID of the segment, as returned by statsig_list_segments. Example: beta_testers.
statsig_conclude_experimentStop an experiment's assignment and analysis while deferring the ship decision.WriteConclude Experiment and Defer Decision
Stop an experiment's assignment and analysis while deferring the ship decision. Returns a confirmation message. Use statsig_conclude_experiment to end data collection now and decide later. Use statsig_ship_experiment when a group is ready to ship.
- Idempotent
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
stop_reasonstring- Optional reason for concluding the experiment. Example: Reached planned duration; reviewing results with the team.
statsig_create_dynamic_configCreate a new dynamic config that serves JSON values to users, optionally with targeting rules.WriteCreate Dynamic Config
Create a new dynamic config that serves JSON values to users, optionally with targeting rules. Returns the created dynamic config, including its generated id. Use statsig_create_dynamic_config for a new config. Use statsig_update_dynamic_config to change an existing one.
Inputs
namestringrequired- Display name of the dynamic config. Statsig derives the ID from it in snake_case. Example: Pricing Page Config.
default_valueobject- JSON object served when no rule matches. Example: {"currency": "USD", "show_banner": false}.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
id_typestring- Unit ID type the entity evaluates on, such as userID, stableID, or a custom unit ID type from statsig_list_unit_id_types. Example: userID.
is_enabledboolean- Whether the config is enabled. A disabled config serves its default value to everyone. Example: true.
rulesarray- Targeting rules as a JSON array. Each rule needs a name, a conditions array (same shape as gate conditions) and a returnValue JSON object served to users who match. passPercentage (0-100) is optional. Example: [{"name": "EU users", "passPercentage": 100, "conditions": [{"type": "country", "operator": "any", "targetValue": ["DE", "FR"]}], "returnValue": {"currency": "EUR"}}]
schemastring- Optional JSON Schema (Draft 2020-12), as a string, that every return value must satisfy. Example: {"type": "object", "properties": {"currency": {"type": "string"}}}.
tagsarray- Tag names to attach, as a JSON array of strings. Tags must already exist (see statsig_list_tags). Example: ["checkout", "web"].
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
teamstring- Name of the owning team (Enterprise only). Example: Growth.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
statsig_create_experimentCreate a new experiment in setup status, with groups, metrics and statistical settings.WriteCreate Experiment
Create a new experiment in setup status, with groups, metrics and statistical settings. Returns the created experiment, including its generated id and groups. Use statsig_create_experiment to set up a test, then statsig_start_experiment to begin it. Use statsig_update_experiment to change an existing one.
Inputs
namestringrequired- Display name of the experiment. Statsig derives the ID from it in snake_case. Example: Checkout Button Color Test.
allocationnumber- Percentage (0-100) of the layer's traffic allocated to this experiment. Example: 100.
analytics_typestring- Statistical analysis mode. Allowed values: frequentist, bayesian, sprt. Example: frequentist.one of
frequentistbayesiansprt bonferroni_correctionboolean- Whether to apply a Bonferroni correction per variant. Example: false.
control_group_idstring- ID of the group to treat as control. Defaults to the first group. Example: Control.
default_confidence_intervalstring- Default confidence interval for results. Allowed values: 80, 90, 95, 98, 99. Example: 95.one of
8090959899 descriptionstring- Summary of what the experiment tests. Example: Tests a green checkout button against the current blue one.
durationinteger- Planned length of the experiment in days. Example: 14.
groupsarray- Test groups as a JSON array. Each group needs a name, a size (percentage; sizes add up to 100) and parameterValues, a JSON object of the parameter values that group serves. Example: [{"name": "Control", "size": 50, "parameterValues": {"button_color": "blue"}}, {"name": "Test", "size": 50, "parameterValues": {"button_color": "green"}}]
hypothesisstring- Statement the experiment tests. Example: A green button increases checkout completion.
id_typestring- Unit ID type users are randomized on, such as userID or stableID. Example: userID.
layer_idstring- Layer to place the experiment in, so it shares traffic with other experiments in that layer. Example: checkout_layer.
primary_metric_tagsarray- Metric tag names whose metrics are treated as primary, as a JSON array. Example: ["revenue"].
primary_metricsarray- Main metrics used to judge the hypothesis, as a JSON array of objects with the metric name and type (from statsig_list_metrics). Example: [{"name": "purchase", "type": "event_count"}]
secondary_metric_tagsarray- Metric tag names whose metrics are treated as secondary, as a JSON array. Example: ["engagement"].
secondary_metricsarray- Additional metrics to monitor, as a JSON array of objects with name and type. Example: [{"name": "add_to_cart", "type": "event_count"}]
sequential_testingboolean- Whether to apply sequential testing so results can be read early. Example: true.
tagsarray- Tag names to attach, as a JSON array of strings. Tags must already exist (see statsig_list_tags). Example: ["checkout", "web"].
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
targeting_gate_idstring- ID of a feature gate users must pass to enter the experiment. Example: new_checkout_flow.
teamstring- Name of the owning team (Enterprise only). Example: Growth.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
statsig_create_gateCreate a new feature gate, optionally with targeting rules.WriteCreate Feature Gate
Create a new feature gate, optionally with targeting rules. Returns the created gate, including its generated id, rules and status. Use statsig_create_gate for a new gate. Use statsig_update_gate to change an existing gate, or statsig_add_gate_rule to add one rule.
Inputs
namestringrequired- Display name of the gate. Statsig derives the gate ID from it in snake_case. Example: New Checkout Flow.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
id_typestring- Unit ID type the entity evaluates on, such as userID, stableID, or a custom unit ID type from statsig_list_unit_id_types. Example: userID.
is_enabledboolean- Whether the gate is enabled. A disabled gate returns false for everyone. Example: true.
rulesarray- Targeting rules, evaluated in order, as a JSON array. Each rule needs a name, a passPercentage (0-100), and a conditions array. Each condition has a type (for example public, user_id, email, country, custom_field, passes_gate, environment_tier), and most types also take an operator (any, none, str_contains_any, gt, lt, version_gt, and so on) and a targetValue. custom_field conditions also take a field name. Optionally limit a rule to specific environments. Example: [{"name": "Internal users", "passPercentage": 100, "conditions": [{"type": "email", "operator": "str_contains_any", "targetValue": ["@example.com"]}]}]
tagsarray- Tag names to attach, as a JSON array of strings. Tags must already exist (see statsig_list_tags). Example: ["checkout", "web"].
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
teamstring- Name of the owning team (Enterprise only). Example: Growth.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
typestring- Lifecycle type: TEMPORARY for a rollout you plan to remove, PERMANENT for a long-lived gate. Allowed values: PERMANENT, TEMPORARY. Example: TEMPORARY.one of
PERMANENTTEMPORARY
statsig_create_holdoutCreate a holdout.WriteCreate Holdout
Create a holdout. Returns the created holdout, including its id. Use statsig_create_holdout to start one, then statsig_update_holdout to set its percentage and attach gates, experiments or layers.
Inputs
namestringrequired- Name of the holdout. Example: Q4 Global Holdout.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
id_typestring- Unit ID type the entity evaluates on, such as userID, stableID, or a custom unit ID type from statsig_list_unit_id_types. Example: userID.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
statsig_create_layerCreate a layer, a container that lets experiments share parameters and split traffic without overlapping.WriteCreate Layer
Create a layer, a container that lets experiments share parameters and split traffic without overlapping. Returns the created layer, including its id. Use statsig_create_layer before creating experiments that must be mutually exclusive. Use statsig_update_layer to add parameters.
Inputs
id_typestringrequired- Unit ID type the entity evaluates on, such as userID, stableID, or a custom unit ID type from statsig_list_unit_id_types. Example: userID.
namestringrequired- Name of the layer, formatted as an ID ("Checkout Layer" becomes "checkout_layer"). Example: checkout_layer.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
teamstring- Name of the team responsible for the layer. Example: Growth.
statsig_create_segmentCreate a segment, either rule-based (users matching conditions) or an ID list.WriteCreate Segment
Create a segment, either rule-based (users matching conditions) or an ID list. Returns the created segment. Use statsig_create_segment for a new reusable user group. Then use statsig_add_segment_ids to fill an ID list, or statsig_update_segment_rules to set rules.
Inputs
namestringrequired- Name of the segment. Example: Beta Testers.
typestringrequired- Kind of segment: rule_based (defined by conditions), id_list (an uploaded list of IDs), user_store_id_list or analysis_list. Allowed values: id_list, rule_based, analysis_list, user_store_id_list. Example: id_list.one of
id_listrule_basedanalysis_listuser_store_id_list descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
id_typestring- Unit ID type the entity evaluates on, such as userID, stableID, or a custom unit ID type from statsig_list_unit_id_types. Example: userID.
rulesarray- Rules for a rule_based segment as a JSON array. Each rule needs a name, a passPercentage (0-100), and a conditions array. Each condition has a type (for example public, user_id, email, country, custom_field, passes_gate, environment_tier), and most types also take an operator (any, none, str_contains_any, gt, lt, version_gt, and so on) and a targetValue. custom_field conditions also take a field name. Optionally limit a rule to specific environments. Example: [{"name": "Internal users", "passPercentage": 100, "conditions": [{"type": "email", "operator": "str_contains_any", "targetValue": ["@example.com"]}]}]
segment_idstring- Optional ID for the segment. Defaults to the name. Example: beta_testers.
tagsarray- Tag names to attach, as a JSON array of strings. Tags must already exist (see statsig_list_tags). Example: ["checkout", "web"].
teamstring- Name of the owning team (Enterprise only). Example: Growth.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
statsig_create_tagCreate a tag for organizing gates, configs, experiments and metrics.WriteCreate Tag
Create a tag for organizing gates, configs, experiments and metrics. Returns the created tag with its id. Use statsig_create_tag before attaching a new tag name. Use statsig_update_tag to rename one.
Inputs
descriptionstringrequired- What the tag is used for. Example: Everything related to the checkout funnel.
namestringrequired- Name of the tag. Example: checkout.
is_coreboolean- Whether this is a core tag, highlighted across the console. Example: false.
statsig_disable_dynamic_configDisable a dynamic config so it serves its default value to everyone.WriteDisable Dynamic Config
Disable a dynamic config so it serves its default value to everyone. Returns the updated dynamic config. Use statsig_disable_dynamic_config to stop targeting. Use statsig_enable_dynamic_config to turn it back on.
- Idempotent
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
statsig_disable_gateDisable a feature gate so it returns false for every user.WriteDisable Feature Gate
Disable a feature gate so it returns false for every user. Returns the updated gate definition. Use statsig_disable_gate as a kill switch. Use statsig_enable_gate to turn it back on.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse
statsig_enable_dynamic_configEnable a dynamic config so its rules are evaluated again.WriteEnable Dynamic Config
Enable a dynamic config so its rules are evaluated again. Returns the updated dynamic config. Use statsig_enable_dynamic_config to turn a config back on. Use statsig_disable_dynamic_config to turn it off.
- Idempotent
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
statsig_enable_gateEnable a feature gate so its rules are evaluated again.WriteEnable Feature Gate
Enable a feature gate so its rules are evaluated again. Returns the updated gate definition. Use statsig_enable_gate to turn a gate back on. Use statsig_disable_gate to turn it off, or statsig_launch_gate to pass it for everyone.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse
statsig_launch_gateLaunch a feature gate so it passes for everyone, marking the rollout as complete.WriteLaunch Feature Gate
Launch a feature gate so it passes for everyone, marking the rollout as complete. Returns the updated gate definition. Use statsig_launch_gate when a rollout is finished. Use statsig_update_gate to change percentages instead.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse
statsig_schedule_experiment_startSchedule an experiment to start at a future time.WriteSchedule Experiment Start
Schedule an experiment to start at a future time. Returns a confirmation message. Use statsig_schedule_experiment_start for a delayed start. Use statsig_start_experiment to start immediately.
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
scheduled_timenumberrequired- Start time as a Unix timestamp in milliseconds. Example: 1767225600000.
statsig_ship_experimentFinish an experiment by shipping one group to everyone.WriteShip Experiment Group
Finish an experiment by shipping one group to everyone. Returns a confirmation message. Use statsig_ship_experiment to launch the winning group. Use statsig_abandon_experiment to stop without shipping, or statsig_conclude_experiment to stop and decide later.
- Idempotent
Inputs
decision_reasonstringrequired- Reason for the decision, recorded on the experiment. Example: Test group raised checkout conversion by 3%.
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
group_idstringrequired- ID of the group to ship, from the experiment's groups. Example: Test.
holdoutinteger- Integer percentage of users to hold back on the old experience after shipping. Example: 5.
remove_targetingboolean- Whether to remove the targeting gate when shipping. Example: false.
statsig_start_experimentStart an experiment so users begin being assigned to its groups.WriteStart Experiment
Start an experiment so users begin being assigned to its groups. Returns a confirmation message. Use statsig_start_experiment to start now. Use statsig_schedule_experiment_start to start at a future time.
- Idempotent
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
analysis_end_timestring- Warehouse Native analysis-only experiments: end time of the analysis window (ISO 8601). Example: 2026-09-15T00:00:00Z.
analysis_start_timestring- Warehouse Native analysis-only experiments: start time of the analysis window (ISO 8601). Example: 2026-09-01T00:00:00Z.
statsig_unarchive_gateRestore an archived feature gate.WriteUnarchive Feature Gate
Restore an archived feature gate. Returns the restored gate definition. Use statsig_unarchive_gate to bring back a gate archived with statsig_archive_gate.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse unarchive_reasonstring- Reason for unarchiving, shown in the audit history. Example: Restoring for a follow-up test.
statsig_update_dynamic_configPartially update a dynamic config.WriteUpdate Dynamic Config
Partially update a dynamic config. Only the fields you send change; sending rules replaces the whole rule list. Returns the updated dynamic config. Use statsig_update_dynamic_config to change the default value, settings or all rules. Use statsig_update_dynamic_config_rule to change a single rule.
- Idempotent
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
default_valueobject- New JSON object served when no rule matches. Example: {"currency": "USD", "show_banner": true}.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
dry_runboolean- Set true to validate the update without saving it. Example: false.
is_enabledboolean- Whether the config is enabled. Example: true.
namestring- New display name. Example: Pricing Page Config v2.
rulesarray- Full replacement list of rules as a JSON array; omitted rules are removed. Each rule needs a name, a conditions array (same shape as gate conditions) and a returnValue JSON object served to users who match. passPercentage (0-100) is optional. Example: [{"name": "EU users", "passPercentage": 100, "conditions": [{"type": "country", "operator": "any", "targetValue": ["DE", "FR"]}], "returnValue": {"currency": "EUR"}}]
tagsarray- Tag names to attach, as a JSON array of strings. Tags must already exist (see statsig_list_tags). Example: ["checkout", "web"].
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
teamstring- Name of the owning team (Enterprise only). Example: Growth.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
typestring- Lifecycle type: PERMANENT to mark the config long-lived, TEMPORARY to unmark it. Allowed values: PERMANENT, TEMPORARY. Example: PERMANENT.one of
PERMANENTTEMPORARY
statsig_update_dynamic_config_ruleUpdate one rule of a dynamic config.WriteUpdate Dynamic Config Rule
Update one rule of a dynamic config. Only the fields you send change. Returns the updated dynamic config. Use statsig_update_dynamic_config_rule to change one rule's conditions or return value. Use statsig_update_dynamic_config to replace all rules.
- Idempotent
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
rule_idstringrequired- ID of the rule, as returned by the rules list for this entity. Example: 4XnxkZmGpqbV9lnT3ACJQo.
conditionsarray- Replacement conditions as a JSON array. Each condition has a type and, for most types, an operator and a targetValue. Example: [{"type": "country", "operator": "any", "targetValue": ["US", "CA"]}]
dry_runboolean- Set true to validate the update without saving it. Example: false.
environmentsarray- Environments this rule applies in, as a JSON array of environment names. Example: ["production"].
namestring- New name for the rule. Example: EU users.
pass_percentagenumber- Percentage (0-100) of matching users who get this rule's return value. Example: 100.
return_valueobject- JSON object served to users who match this rule. Example: {"currency": "EUR"}.
statsig_update_experimentPartially update an experiment's setup.WriteUpdate Experiment
Partially update an experiment's setup. Only the fields you send change. Returns the updated experiment. Use statsig_update_experiment to edit groups, metrics or settings. Use statsig_start_experiment, statsig_ship_experiment or statsig_abandon_experiment to change its status.
- Idempotent
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
allocationnumber- Percentage (0-100) of the layer's traffic allocated to this experiment. Example: 100.
analytics_typestring- Statistical analysis mode. Allowed values: frequentist, bayesian, sprt. Example: frequentist.one of
frequentistbayesiansprt bonferroni_correctionboolean- Whether to apply a Bonferroni correction per variant. Example: false.
control_group_idstring- ID of the group to treat as control. Defaults to the first group. Example: Control.
default_confidence_intervalstring- Default confidence interval for results. Allowed values: 80, 90, 95, 98, 99. Example: 95.one of
8090959899 descriptionstring- Summary of what the experiment tests. Example: Tests a green checkout button against the current blue one.
durationinteger- Planned length of the experiment in days. Example: 14.
groupsarray- Test groups as a JSON array. Each group needs a name, a size (percentage; sizes add up to 100) and parameterValues, a JSON object of the parameter values that group serves. Example: [{"name": "Control", "size": 50, "parameterValues": {"button_color": "blue"}}, {"name": "Test", "size": 50, "parameterValues": {"button_color": "green"}}]
hypothesisstring- Statement the experiment tests. Example: A green button increases checkout completion.
id_typestring- Unit ID type users are randomized on, such as userID or stableID. Example: userID.
namestring- New display name. Example: Checkout Button Color Test v2.
primary_metric_tagsarray- Metric tag names whose metrics are treated as primary, as a JSON array. Example: ["revenue"].
primary_metricsarray- Main metrics used to judge the hypothesis, as a JSON array of objects with the metric name and type (from statsig_list_metrics). Example: [{"name": "purchase", "type": "event_count"}]
secondary_metric_tagsarray- Metric tag names whose metrics are treated as secondary, as a JSON array. Example: ["engagement"].
secondary_metricsarray- Additional metrics to monitor, as a JSON array of objects with name and type. Example: [{"name": "add_to_cart", "type": "event_count"}]
sequential_testingboolean- Whether to apply sequential testing so results can be read early. Example: true.
tagsarray- Tag names to attach, as a JSON array of strings. Tags must already exist (see statsig_list_tags). Example: ["checkout", "web"].
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
targeting_gate_idstring- ID of a feature gate users must pass to enter the experiment. Example: new_checkout_flow.
teamstring- Name of the owning team (Enterprise only). Example: Growth.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
statsig_update_experiment_overridesAdd overrides that force users, or members of a gate or segment, into specific experiment groups.WriteUpdate Experiment Overrides
Add overrides that force users, or members of a gate or segment, into specific experiment groups. Returns the experiment's overrides after the change. Use statsig_update_experiment_overrides for QA or forced assignment. Use statsig_get_experiment_overrides to read current overrides.
- Idempotent
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
overridesarrayrequired- Gate or segment overrides as a JSON array (use [] for none). Each entry has a type (gate or segment), the gate or segment id, and the groupID its members are forced into. Example: [{"type": "segment", "id": "beta_testers", "groupID": "Test"}]
user_id_overridesarrayrequired- User ID overrides as a JSON array (use [] for none). Each entry has a groupID and an ids array of user IDs forced into that group; optionally an environment and unitType. Example: [{"groupID": "Test", "ids": ["user_123"]}]
statsig_update_gatePartially update a feature gate.WriteUpdate Feature Gate
Partially update a feature gate. Only the fields you send change; sending rules replaces the whole rule list. Returns the updated gate definition. Use statsig_update_gate to edit settings or replace all rules. Use statsig_update_gate_rule to change a single rule, or statsig_enable_gate and statsig_disable_gate to toggle it.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
is_enabledboolean- Whether the gate is enabled. A disabled gate returns false for everyone. Example: true.
namestring- New display name for the gate. Example: New Checkout Flow v2.
rulesarray- Full replacement list of targeting rules as a JSON array; omitted rules are removed. Each rule needs a name, a passPercentage (0-100), and a conditions array. Each condition has a type (for example public, user_id, email, country, custom_field, passes_gate, environment_tier), and most types also take an operator (any, none, str_contains_any, gt, lt, version_gt, and so on) and a targetValue. custom_field conditions also take a field name. Optionally limit a rule to specific environments. Example: [{"name": "Internal users", "passPercentage": 100, "conditions": [{"type": "email", "operator": "str_contains_any", "targetValue": ["@example.com"]}]}]
tagsarray- Tag names to attach, as a JSON array of strings. Tags must already exist (see statsig_list_tags). Example: ["checkout", "web"].
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
teamstring- Name of the owning team (Enterprise only). Example: Growth.
team_idstring- ID of the owning team (Enterprise only), as returned by statsig_list_teams. Example: 2bC4dE6fG8hI0jK2lM4nO6.
typestring- Lifecycle type: TEMPORARY or PERMANENT. Allowed values: PERMANENT, TEMPORARY. Example: PERMANENT.one of
PERMANENTTEMPORARY
statsig_update_gate_ruleUpdate one targeting rule of a feature gate.WriteUpdate Feature Gate Rule
Update one targeting rule of a feature gate. Only the fields you send change. Returns the updated gate definition with all rules. Use statsig_update_gate_rule to change one rule's percentage or conditions. Use statsig_update_gate to replace every rule at once.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
rule_idstringrequired- ID of the rule, as returned by the rules list for this entity. Example: 4XnxkZmGpqbV9lnT3ACJQo.
conditionsarray- Replacement conditions as a JSON array. Each condition has a type and, for most types, an operator and a targetValue. Example: [{"type": "country", "operator": "any", "targetValue": ["US", "CA"]}]
environmentsarray- Environments this rule applies in, as a JSON array of environment names. Example: ["production", "staging"].
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse namestring- New name for the rule. Example: Internal users.
pass_percentagenumber- Percentage (0-100) of users matching the conditions who pass. Example: 50.
statsig_update_holdoutPartially update a holdout.WriteUpdate Holdout
Partially update a holdout. Only the fields you send change. Returns the updated holdout. Use statsig_update_holdout to change its percentage or attach gates, experiments and layers.
- Idempotent
Inputs
holdout_idstringrequired- ID of the holdout, as returned by statsig_list_holdouts. Example: global_holdout_q4.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
experiment_idsarray- Experiment IDs the holdout applies to, as a JSON array. Example: ["checkout_button_color_test"].
gate_idsarray- Feature gate IDs the holdout applies to, as a JSON array. Example: ["new_checkout_flow"].
is_enabledboolean- Whether the holdout is active. Example: true.
is_globalboolean- Whether the holdout applies to all new gates automatically. Example: false.
layer_idsarray- Layer IDs the holdout applies to, as a JSON array. Example: ["checkout_layer"].
pass_percentagenumber- Percentage of users (0-10) held out. Example: 5.
targeting_gate_idstring- ID of a gate that limits who can be held out. Send an empty string to clear it. Example: us_users_only.
statsig_update_layerPartially update a layer's description, parameters or target apps.WriteUpdate Layer
Partially update a layer's description, parameters or target apps. Returns the updated layer. Use statsig_update_layer to add or change layer parameters. Use statsig_get_layer to read current parameters first.
- Idempotent
Inputs
layer_idstringrequired- ID of the layer, as returned by statsig_list_layers. Example: checkout_layer.
descriptionstring- Short summary of what this is used for. Example: Rolls out the redesigned checkout to web users.
parametersarray- Layer parameters as a JSON array. Each parameter has a name, a type (string, number, boolean, object or array), a defaultValue of that type and an optional description. Example: [{"name": "button_color", "type": "string", "defaultValue": "blue"}]
target_appsarray- Target app names to scope evaluation to, as a JSON array of strings (see statsig_list_target_apps). Example: ["web_app"].
statsig_update_segment_rulesReplace the rules of a rule-based segment.WriteUpdate Segment Rules
Replace the rules of a rule-based segment. Returns the updated segment. Use statsig_update_segment_rules to change who matches a rule-based segment. Use statsig_add_segment_ids for ID-list segments.
Inputs
rulesarrayrequired- Full replacement list of rules as a JSON array. Each rule needs a name, a passPercentage (0-100), and a conditions array. Each condition has a type (for example public, user_id, email, country, custom_field, passes_gate, environment_tier), and most types also take an operator (any, none, str_contains_any, gt, lt, version_gt, and so on) and a targetValue. custom_field conditions also take a field name. Optionally limit a rule to specific environments. Example: [{"name": "Internal users", "passPercentage": 100, "conditions": [{"type": "email", "operator": "str_contains_any", "targetValue": ["@example.com"]}]}]
segment_idstringrequired- ID of the segment, as returned by statsig_list_segments. Example: beta_testers.
statsig_update_tagUpdate a tag's name, description or core flag.WriteUpdate Tag
Update a tag's name, description or core flag. Returns the updated tag. Use statsig_update_tag to rename or describe a tag. Use statsig_list_tags to find tag IDs.
- Idempotent
Inputs
tag_idstringrequired- ID of the tag returned when it was created, or the tag name. An exact ID match takes precedence over a name match. Example: checkout.
descriptionstring- New description. Example: Checkout funnel gates and experiments.
is_coreboolean- Whether this is a core tag. Example: true.
namestring- New name for the tag. Example: checkout-funnel.
statsig_delete_dynamic_configPermanently delete a dynamic config.DestructiveDelete Dynamic Config
Permanently delete a dynamic config. Returns a confirmation message. Use statsig_delete_dynamic_config to remove a config for good. Use statsig_archive_dynamic_config to retire it while keeping history.
- Idempotent
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
statsig_delete_dynamic_config_ruleDelete one rule from a dynamic config.DestructiveDelete Dynamic Config Rule
Delete one rule from a dynamic config. Returns the updated dynamic config with the remaining rules. Use statsig_delete_dynamic_config_rule to remove a single rule. Use statsig_list_dynamic_config_rules to find rule IDs.
- Idempotent
Inputs
dynamic_config_idstringrequired- ID of the dynamic config, as returned by statsig_list_dynamic_configs. Example: pricing_page_config.
rule_idstringrequired- ID of the rule, as returned by the rules list for this entity. Example: 4XnxkZmGpqbV9lnT3ACJQo.
statsig_delete_experimentPermanently delete an experiment.DestructiveDelete Experiment
Permanently delete an experiment. Returns a confirmation message. Use statsig_delete_experiment to remove an experiment for good. Use statsig_archive_experiment to retire it while keeping results.
- Idempotent
Inputs
experiment_idstringrequired- ID of the experiment, as returned by statsig_list_experiments. Example: checkout_button_color_test.
statsig_delete_gatePermanently delete a feature gate.DestructiveDelete Feature Gate
Permanently delete a feature gate. Returns a confirmation message. Use statsig_delete_gate to remove a gate for good. Use statsig_archive_gate to retire it while keeping its history.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
statsig_delete_gate_ruleDelete one targeting rule from a feature gate.DestructiveDelete Feature Gate Rule
Delete one targeting rule from a feature gate. Returns the updated gate definition with the remaining rules. Use statsig_delete_gate_rule to remove a single rule. Use statsig_list_gate_rules to find rule IDs.
- Idempotent
Inputs
gate_idstringrequired- ID of the feature gate, as returned by statsig_list_gates (usually the gate name in snake_case). Example: new_checkout_flow.
rule_idstringrequired- ID of the rule, as returned by the rules list for this entity. Example: 4XnxkZmGpqbV9lnT3ACJQo.
include_archive_metadatastring- Set to "true" to include archivedAt, archivedBy and archiveReason on archived gates. Allowed values: true, false. Example: true.one of
truefalse
statsig_delete_layerPermanently delete a layer.DestructiveDelete Layer
Permanently delete a layer. Returns a confirmation message. Use statsig_delete_layer to remove an unused layer. Use statsig_list_layer_experiments first to check it holds no experiments.
- Idempotent
Inputs
layer_idstringrequired- ID of the layer, as returned by statsig_list_layers. Example: checkout_layer.
statsig_delete_segmentPermanently delete a segment.DestructiveDelete Segment
Permanently delete a segment. Returns a confirmation message. Use statsig_delete_segment to remove a segment for good. Use statsig_archive_segment to retire it while keeping history.
- Idempotent
Inputs
segment_idstringrequired- ID of the segment, as returned by statsig_list_segments. Example: beta_testers.
statsig_remove_segment_idsRemove IDs from an ID-list segment.DestructiveRemove IDs from Segment
Remove IDs from an ID-list segment. Statsig rate-limits this endpoint (about 12 requests per 10 seconds). Returns a confirmation message. Use statsig_remove_segment_ids to take IDs out of a list. Use statsig_add_segment_ids to add them.
- Idempotent
Inputs
idsarrayrequired- IDs to remove, as a JSON array of strings. Example: ["user_123"].
segment_idstringrequired- ID of the segment, as returned by statsig_list_segments. Example: beta_testers.
No tools match.
