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 Metadata API

Manage metadata fields and model configuration.

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

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

This API exposes 9 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version v1.

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

9 operations 5 paths 6 schemas 1 DELETE5 GET1 PATCH1 POST1 PUT

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 Metadata 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 9

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

Metadata 9

Manage metadata fields and model configuration.

GET
/api/v1/auth/saml/{name}/metadata/
Api v1 auth saml metadata retrieve
api_v1_auth_saml_metadata_retrieve 2 params → 200
GET
/api/v1/metadata/fields/
Api v1 metadata fields list
api_v1_metadata_fields_list 3 params → 200
POST
/api/v1/metadata/fields/
Api v1 metadata fields create
api_v1_metadata_fields_create body → 201
GET
/api/v1/metadata/fields/{id}/
Api v1 metadata fields retrieve
api_v1_metadata_fields_retrieve 1 param → 200
PUT
/api/v1/metadata/fields/{id}/
Api v1 metadata fields update
api_v1_metadata_fields_update 1 param body → 200
PATCH
/api/v1/metadata/fields/{id}/
Api v1 metadata fields partial update
api_v1_metadata_fields_partial_update 1 param body → 200
DELETE
/api/v1/metadata/fields/{id}/
Api v1 metadata fields destroy
api_v1_metadata_fields_destroy 1 param → 204
GET
/api/v1/projects/{project_pk}/metadata/fields/
Api v1 projects metadata fields list
api_v1_projects_metadata_fields_list 5 params → 200
GET
/api/v1/projects/{project_pk}/metadata/fields/{id}/
Api v1 projects metadata fields retrieve
api_v1_projects_metadata_fields_retrieve 2 params → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are MetadataField (7 properties), PatchedMetadataField (7 properties), PaginatedMetadataFieldList (4 properties), MetadataModelFieldNested (3 properties). Each schema is shown below with its type and property counts.

PatchedMetadataField
object
7 properties
PaginatedMetadataFieldList
object
4 properties 2 required
MetadataFieldTypeEnum
string
int - Integer str - String bool - Boolean url - Url multilinestr - Multiline String
MetadataModelFieldRequirement
object
2 properties 2 required
MetadataField
object
7 properties 2 required
MetadataModelFieldNested
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flagsmith-metadata-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 Metadata 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.