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

Flagsmith Feature states API

Manage feature states and feature versioning.

Flagsmith Feature states API is one of 24 APIs that Flagsmith publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Feature states. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 17 operations across 11 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against the base URL https://edge.api.flagsmith.com.

17 operations 11 paths 26 schemas 3 DELETE6 GET3 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://edge.api.flagsmith.com
Authentication
HTTP Bearer, HTTP Basic, API Key, API Key, HTTP Basic, API Key
License
BSD License
Resource Areas
1

Authentication & Security 6

Flagsmith Feature states API declares 6 security schemes for authenticating requests. It accepts HTTP bearer tokens (Cohort_Sync_Key). It accepts HTTP basic authentication (Cohort_Sync_Key__Basic). An API key is passed in the header as X-Environment-Key (Environment_API_Key). An API key is passed in the header as Authorization (Master_API_Key). It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as Authorization (tokenAuth).

  • Cohort_Sync_Key — For cohort sync endpoints called by an external cohort source, such as Amplitude.
  • Cohort_Sync_Key__Basic — For cohort sync endpoints called by an external cohort source that can only send Basic credentials, such as Mixpanel. The key is the password; the username is…
  • Environment_API_Key — For SDK endpoints. Find out more .
  • Master_API_Key — For Management API endpoints. Find out more .
  • tokenAuth — Token-based authentication with required prefix "Token"

Paths & Operations 17

Across 11 paths, the API surfaces 17 operations — 3 DELETE, 6 GET, 3 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Feature states 17

Manage feature states and feature versioning.

GET
/api/v1/environment-feature-versions/{id}/
Api v1 environment feature versions retrieve
api_v1_environment_feature_versions_retrieve 1 param → 200
GET
/api/v1/environments/{environment_api_key}/featurestates/
Api v1 environments featurestates list
api_v1_environments_featurestates_list 5 params → 200
POST
/api/v1/environments/{environment_api_key}/featurestates/
Api v1 environments featurestates create
api_v1_environments_featurestates_create 1 param body → 201
GET
/api/v1/environments/{environment_api_key}/featurestates/{id}/
Api v1 environments featurestates retrieve
api_v1_environments_featurestates_retrieve 2 params → 200
PATCH
/api/v1/environments/{environment_api_key}/featurestates/{id}/
Api v1 environments featurestates partial update
api_v1_environments_featurestates_partial_update 2 params body → 200
DELETE
/api/v1/environments/{environment_api_key}/featurestates/{id}/
Api v1 environments featurestates destroy
api_v1_environments_featurestates_destroy 2 params → 204
PATCH
/api/v1/environments/{environment_pk}/features/{feature_pk}/versions/{environment_feature_version_pk}/featurestates/{id}/
Api v1 environments features versions featurestates partial update
api_v1_environments_features_versions_featurestates_partial_update 4 params body → 200
DELETE
/api/v1/environments/{environment_pk}/features/{feature_pk}/versions/{environment_feature_version_pk}/featurestates/{id}/
Api v1 environments features versions featurestates destroy
api_v1_environments_features_versions_featurestates_destroy 4 params → 204
POST
/api/v1/feature-health/{path}
Api v1 feature health create
api_v1_feature_health_create 1 param → 200
GET
/api/v1/features/featurestates/
Api v1 features featurestates list
api_v1_features_featurestates_list 4 params → 200
POST
/api/v1/features/featurestates/
Api v1 features featurestates create
api_v1_features_featurestates_create body → 201
PATCH
/api/v1/features/featurestates/{id}/
Api v1 features featurestates partial update
api_v1_features_featurestates_partial_update 1 param body → 200
GET
/api/v1/features/featurestates/get-by-uuid/{uuid}/
Api v1 features featurestates get by uuid retrieve
api_v1_features_featurestates_get_by_uuid_retrieve 1 param → 200
POST
/api/v1/projects/{project_pk}/feature-health/events/{id}/dismiss/
Api v1 projects feature health events dismiss create
api_v1_projects_feature_health_events_dismiss_create 2 params body → 200
GET
/api/v1/projects/{project_pk}/feature-health/providers/
Api v1 projects feature health providers list
api_v1_projects_feature_health_providers_list 1 param → 200
POST
/api/v1/projects/{project_pk}/feature-health/providers/
Api v1 projects feature health providers create
api_v1_projects_feature_health_providers_create 1 param body → 201
DELETE
/api/v1/projects/{project_pk}/feature-health/providers/{name}/
Api v1 projects feature health providers destroy
api_v1_projects_feature_health_providers_destroy 2 params → 204

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are WritableNestedFeatureState (17 properties), FeatureStateSerializerWithIdentity (17 properties), PatchedWritableNestedFeatureState (17 properties), FeatureStateSerializerBasic (17 properties). Each schema is shown below with its type and property counts.

FeatureHealthEventReasonTextBlock
object
2 properties 1 required
FeatureHealthEventReasonUrlBlock
object
2 properties 1 required
EnvironmentFeatureVersionRetrieve
object
12 properties
CustomCreateSegmentOverrideFeatureSegment
object
4 properties 1 required
FeatureStateSerializerWithIdentity
object
Adds nested create feature
17 properties 2 required
PaginatedWritableNestedFeatureStateList
object
4 properties 2 required
PaginatedFeatureStateSerializerWithIdentityList
object
4 properties 2 required
PatchedWritableNestedFeatureState
object
Adds nested create feature
17 properties
NameEnum
string
Webhook - Webhook Grafana - Grafana
FeatureHealthEvent
object
7 properties 1 required
MultivariateFeatureStateValue
object
3 properties 2 required
PatchedCustomEnvironmentFeatureVersionFeatureState
object
Adds nested create feature
14 properties
FeatureStateSerializerCreate
object
2 properties 1 required
WritableNestedFeatureState
object
Adds nested create feature
17 properties 2 required
NullEnum
null
FeatureStateValue
object
4 properties
BlankEnum
FeatureHealthEventTypeEnum
string
UNHEALTHY - Unhealthy HEALTHY - Healthy
FeatureStateSerializerBasic
object
Adds nested create feature
17 properties 1 required
PatchedFeatureStateSerializerCreate
object
2 properties
CustomEnvironmentFeatureVersionFeatureState
object
Adds nested create feature
14 properties 1 required
CreateFeatureHealthProvider
object
1 property 1 required
FeatureHealthEventReason
object
2 properties 2 required
_Identity
object
2 properties 1 required
FeatureHealthProvider
object
4 properties 2 required
Type975Enum
string
int - Integer unicode - String bool - Boolean

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flagsmith-feature-states-api-openapi.yml Raw ↑

Other APIs Flagsmith publishes across the network.

Flagsmith Flags API
flagsmith Environments API
flagsmith Features API
flagsmith Identities API
flagsmith Organisations API
flagsmith Projects API
flagsmith Segments API
flagsmith Users API
flagsmith Webhooks API
Flagsmith Admin dashboard API
Flagsmith Analytics API
Flagsmith Audit API
Where this information came from

This is an independent, third-party profile of Flagsmith Feature states 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.