Split · Controlled Vocabulary
Split Vocabulary
Normative vocabulary for Split (now Harness Feature Management and Experimentation), a feature flag and experimentation platform. Covers feature flag lifecycle, targeting, treatments, segmentation, and experimentation concepts.
17 Terms
Updated 2026-05-02
Split Vocabulary is a controlled vocabulary published by Split on the APIs.io network, defining 17 terms.
Defined terms include Feature Flag, Split, Treatment, Workspace, and Environment.
A controlled vocabulary pins the words an API’s schemas, parameters and documentation use to one agreed definition each — the shared language a human or an agent needs to read the API the same way its authors do.
Feature Flag
A toggle mechanism that controls whether a specific feature or code path is active for a given user or traffic segment. Also called a "split" in the Split platform. Feature flags enable progressive delivery and experimentation without code deployments.
Split
The platform's term for a feature flag. Each split has a name, a traffic type, and one or more treatments. Evaluated by SDK or Evaluator API to return a treatment.
Treatment
A named variant that a feature flag can return (e.g., on, off, v1, v2, control). Treatments can carry dynamic configuration (JSON) to adjust behavior without redeployment.
Workspace
A project-level namespace in Split that organizes feature flags, environments, and segments. Corresponds to a business unit, application, or team boundary.
Environment
A deployment context (e.g., staging, production) within a workspace where feature flags can have independent definitions, targeting rules, and rollout configurations.
Targeting Rule
A conditional expression that matches a subset of traffic and assigns treatments based on attribute values, segment membership, or percentage-based bucketing. Rules are evaluated in order; the first matching rule determines the treatment.
Segment
A reusable group of identity keys (e.g., user IDs) used in targeting rules. Segments can be managed via CSV upload or individual key management operations.
Traffic Type
Defines the entity kind that a feature flag evaluates against (e.g., user, account, device). Each feature flag is associated with a traffic type at creation.
Traffic Allocation
The percentage of incoming traffic that participates in feature flag evaluation (0-100%). Traffic outside this allocation always receives the default treatment.
Default Treatment
The treatment returned when no targeting rules match a given key, or when the feature flag is killed. Acts as the safe fallback for all unmatched traffic.
Kill
An emergency operation that overrides all targeting rules and forces all evaluations to return the default treatment. Used as an immediate feature shut-off.
Change Request
A formal request to modify a feature flag definition that requires approval from designated reviewers before being applied. Enables controlled governance workflows.
Impression
A record of a feature flag evaluation event for a specific key. Impressions are used for monitoring, debugging, and calculating experimentation metrics.
Evaluator
The Split Evaluator is a standalone HTTP microservice that wraps an SDK to provide REST-based feature flag evaluation for applications that cannot embed an SDK directly.
Admin API
The Split REST API for programmatic management of workspaces, environments, flags, segments, users, groups, and API keys. Requires Admin API key authentication.
SDK
A language-specific library that embeds Split's evaluation engine locally, synchronizing flag definitions and evaluating treatments with low latency without making per-evaluation network calls. Available for JavaScript, Node.js, Java, Python, Android, iOS, React, and more.
Bucket
A percentage allocation within a targeting rule or default rule that assigns a specific treatment to a portion of matching traffic. Buckets in a rule must sum to 100%.
name: Split Vocabulary
description: >-
Normative vocabulary for Split (now Harness Feature Management and Experimentation),
a feature flag and experimentation platform. Covers feature flag lifecycle, targeting,
treatments, segmentation, and experimentation concepts.
version: "1.0"
created: "2026-05-02"
modified: "2026-05-02"
terms:
- term: Feature Flag
definition: >-
A toggle mechanism that controls whether a specific feature or code path is active
for a given user or traffic segment. Also called a "split" in the Split platform.
Feature flags enable progressive delivery and experimentation without code deployments.
tags:
- Core
- Feature Management
- term: Split
definition: >-
The platform's term for a feature flag. Each split has a name, a traffic type,
and one or more treatments. Evaluated by SDK or Evaluator API to return a treatment.
tags:
- Core
- Feature Management
- term: Treatment
definition: >-
A named variant that a feature flag can return (e.g., on, off, v1, v2, control).
Treatments can carry dynamic configuration (JSON) to adjust behavior without redeployment.
tags:
- Core
- Experimentation
- term: Workspace
definition: >-
A project-level namespace in Split that organizes feature flags, environments,
and segments. Corresponds to a business unit, application, or team boundary.
tags:
- Organization
- Administration
- term: Environment
definition: >-
A deployment context (e.g., staging, production) within a workspace where feature
flags can have independent definitions, targeting rules, and rollout configurations.
tags:
- Organization
- Deployment
- term: Targeting Rule
definition: >-
A conditional expression that matches a subset of traffic and assigns treatments
based on attribute values, segment membership, or percentage-based bucketing.
Rules are evaluated in order; the first matching rule determines the treatment.
tags:
- Targeting
- Rollouts
- term: Segment
definition: >-
A reusable group of identity keys (e.g., user IDs) used in targeting rules.
Segments can be managed via CSV upload or individual key management operations.
tags:
- Targeting
- Identity
- term: Traffic Type
definition: >-
Defines the entity kind that a feature flag evaluates against (e.g., user, account,
device). Each feature flag is associated with a traffic type at creation.
tags:
- Targeting
- Identity
- term: Traffic Allocation
definition: >-
The percentage of incoming traffic that participates in feature flag evaluation
(0-100%). Traffic outside this allocation always receives the default treatment.
tags:
- Rollouts
- Experimentation
- term: Default Treatment
definition: >-
The treatment returned when no targeting rules match a given key, or when the
feature flag is killed. Acts as the safe fallback for all unmatched traffic.
tags:
- Core
- Feature Management
- term: Kill
definition: >-
An emergency operation that overrides all targeting rules and forces all
evaluations to return the default treatment. Used as an immediate feature shut-off.
tags:
- Operations
- Safety
- term: Change Request
definition: >-
A formal request to modify a feature flag definition that requires approval from
designated reviewers before being applied. Enables controlled governance workflows.
tags:
- Administration
- Governance
- term: Impression
definition: >-
A record of a feature flag evaluation event for a specific key. Impressions are
used for monitoring, debugging, and calculating experimentation metrics.
tags:
- Observability
- Experimentation
- term: Evaluator
definition: >-
The Split Evaluator is a standalone HTTP microservice that wraps an SDK to provide
REST-based feature flag evaluation for applications that cannot embed an SDK directly.
tags:
- Service
- Integration
- term: Admin API
definition: >-
The Split REST API for programmatic management of workspaces, environments, flags,
segments, users, groups, and API keys. Requires Admin API key authentication.
tags:
- API
- Administration
- term: SDK
definition: >-
A language-specific library that embeds Split's evaluation engine locally,
synchronizing flag definitions and evaluating treatments with low latency without
making per-evaluation network calls. Available for JavaScript, Node.js, Java,
Python, Android, iOS, React, and more.
tags:
- Integration
- Client
- term: Bucket
definition: >-
A percentage allocation within a targeting rule or default rule that assigns
a specific treatment to a portion of matching traffic. Buckets in a rule must
sum to 100%.
tags:
- Rollouts
- Targeting
Every vocabulary here is available over the APIs.io API and to AI agents over MCP. Vocabularies is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for vocabularies
3 MCP tools reach this
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
Search the catalog
curl "https://apis.io/api/v1/search?q=split-vocabulary&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/split-vocabulary"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.