How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Split Feature Flag Definitions API

Manage feature flag definitions in specific environments, including targeting rules, treatments, percentage rollouts, and default treatments.

Split Feature Flag Definitions API is one of 10 APIs that Split publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Feature Flag Definitions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 7 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.split.io/internal/api/v2.

7 operations 4 paths 11 schemas 1 DELETE2 GET1 PATCH1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Server
https://api.split.io/internal/api/v2
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Split Feature Flag Definitions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Admin API key passed as a Bearer token in the Authorization header.

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Feature Flag Definitions 7

Manage feature flag definitions in specific environments, including targeting rules, treatments, percentage rollouts, and default treatments.

GET
/splits/ws/{workspaceId}/{featureFlagName}/environments/{environmentId}
Get feature flag definition in environment
getFeatureFlagDefinition 3 params → 200401404
POST
/splits/ws/{workspaceId}/{featureFlagName}/environments/{environmentId}
Create feature flag definition in environment
createFeatureFlagDefinition 3 params body → 200400401404
PATCH
/splits/ws/{workspaceId}/{featureFlagName}/environments/{environmentId}
Update feature flag definition in environment
updateFeatureFlagDefinition 3 params body → 200400401404
DELETE
/splits/ws/{workspaceId}/{featureFlagName}/environments/{environmentId}
Delete feature flag definition in environment
deleteFeatureFlagDefinition 3 params → 200401404
GET
/splits/ws/{workspaceId}/environments/{environmentId}
List feature flag definitions in environment
listFeatureFlagDefinitionsInEnvironment 4 params → 200401404
PUT
/splits/ws/{workspaceId}/{featureFlagName}/environments/{environmentId}/kill
Kill feature flag in environment
killFeatureFlag 3 params → 200401404
PUT
/splits/ws/{workspaceId}/{featureFlagName}/environments/{environmentId}/restore
Restore feature flag in environment
restoreFeatureFlag 3 params → 200401404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are FeatureFlagDefinition (12 properties), Matcher (8 properties), FeatureFlagDefinitionUpdate (7 properties), FeatureFlagDefinitionCreate (6 properties). Each schema is shown below with its type and property counts.

FeatureFlagDefinition
object
The full definition of a feature flag in a specific environment, including treatments, targeting rules, and rollout configuration.
12 properties
EnvironmentRef
object
A reference to an environment
2 properties
Condition
object
A condition defining the matching criteria for a targeting rule.
2 properties
FeatureFlagDefinitionCreate
object
Request body for creating a feature flag definition in an environment
6 properties 3 required
TargetingRule
object
A targeting rule that matches specific conditions and assigns treatments to matching traffic.
2 properties
TrafficType
object
A traffic type defining the kind of entity targeted by feature flags.
2 properties
Bucket
object
A bucket defining the percentage of traffic assigned to a specific treatment within a rule.
2 properties
Treatment
object
A treatment representing one of the possible values returned by a feature flag evaluation.
3 properties 1 required
FeatureFlagDefinitionList
object
Paginated list of feature flag definitions
4 properties
FeatureFlagDefinitionUpdate
object
Request body for partially updating a feature flag definition in an environment. Only provided fields are updated.
7 properties
Matcher
object
A matcher defining a single matching criterion based on attributes, segments, or key values.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

split-feature-flag-definitions-api-openapi.yml Raw ↑

Other APIs Split publishes across the network.

Split Admin API
Split JavaScript SDK
Split Node.js SDK
Split Java SDK
Split Python SDK
Split React SDK
Split Evaluation API
Split Events API
Split Feature Flags API
Where this information came from

This is an independent, third-party profile of Split Feature Flag Definitions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.