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

Manage user and group permissions across organisations, projects, and environments.

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

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

This API exposes 34 operations across 12 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version v1.

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

34 operations 12 paths 22 schemas 6 DELETE10 GET6 PATCH6 POST6 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 Permissions 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 34

Across 12 paths, the API surfaces 34 operations — 6 DELETE, 10 GET, 6 PATCH, 6 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Permissions 34

Manage user and group permissions across organisations, projects, and environments.

GET
/api/v1/environments/{environment_api_key}/user-group-permissions/
Api v1 environments user group permissions list
api_v1_environments_user_group_permissions_list 1 param → 200
POST
/api/v1/environments/{environment_api_key}/user-group-permissions/
Api v1 environments user group permissions create
api_v1_environments_user_group_permissions_create 1 param body → 201
GET
/api/v1/environments/{environment_api_key}/user-group-permissions/{id}/
Api v1 environments user group permissions retrieve
api_v1_environments_user_group_permissions_retrieve 2 params → 200
PUT
/api/v1/environments/{environment_api_key}/user-group-permissions/{id}/
Api v1 environments user group permissions update
api_v1_environments_user_group_permissions_update 2 params body → 200
PATCH
/api/v1/environments/{environment_api_key}/user-group-permissions/{id}/
Api v1 environments user group permissions partial update
api_v1_environments_user_group_permissions_partial_update 2 params body → 200
DELETE
/api/v1/environments/{environment_api_key}/user-group-permissions/{id}/
Api v1 environments user group permissions destroy
api_v1_environments_user_group_permissions_destroy 2 params → 204
GET
/api/v1/environments/{environment_api_key}/user-permissions/
Api v1 environments user permissions list
api_v1_environments_user_permissions_list 1 param → 200
POST
/api/v1/environments/{environment_api_key}/user-permissions/
Api v1 environments user permissions create
api_v1_environments_user_permissions_create 1 param body → 201
GET
/api/v1/environments/{environment_api_key}/user-permissions/{id}/
Api v1 environments user permissions retrieve
api_v1_environments_user_permissions_retrieve 2 params → 200
PUT
/api/v1/environments/{environment_api_key}/user-permissions/{id}/
Api v1 environments user permissions update
api_v1_environments_user_permissions_update 2 params body → 200
PATCH
/api/v1/environments/{environment_api_key}/user-permissions/{id}/
Api v1 environments user permissions partial update
api_v1_environments_user_permissions_partial_update 2 params body → 200
DELETE
/api/v1/environments/{environment_api_key}/user-permissions/{id}/
Api v1 environments user permissions destroy
api_v1_environments_user_permissions_destroy 2 params → 204
GET
/api/v1/organisations/{organisation_pk}/user-group-permissions/
Api v1 organisations user group permissions list
api_v1_organisations_user_group_permissions_list 2 params → 200
POST
/api/v1/organisations/{organisation_pk}/user-group-permissions/
Api v1 organisations user group permissions create
api_v1_organisations_user_group_permissions_create 1 param body → 201
PUT
/api/v1/organisations/{organisation_pk}/user-group-permissions/{id}/
Api v1 organisations user group permissions update
api_v1_organisations_user_group_permissions_update 2 params body → 200
PATCH
/api/v1/organisations/{organisation_pk}/user-group-permissions/{id}/
Api v1 organisations user group permissions partial update
api_v1_organisations_user_group_permissions_partial_update 2 params body → 200
DELETE
/api/v1/organisations/{organisation_pk}/user-group-permissions/{id}/
Api v1 organisations user group permissions destroy
api_v1_organisations_user_group_permissions_destroy 2 params → 204
GET
/api/v1/organisations/{organisation_pk}/user-permissions/
Api v1 organisations user permissions list
api_v1_organisations_user_permissions_list 2 params → 200
POST
/api/v1/organisations/{organisation_pk}/user-permissions/
Api v1 organisations user permissions create
api_v1_organisations_user_permissions_create 1 param body → 201
PUT
/api/v1/organisations/{organisation_pk}/user-permissions/{id}/
Api v1 organisations user permissions update
api_v1_organisations_user_permissions_update 2 params body → 200
PATCH
/api/v1/organisations/{organisation_pk}/user-permissions/{id}/
Api v1 organisations user permissions partial update
api_v1_organisations_user_permissions_partial_update 2 params body → 200
DELETE
/api/v1/organisations/{organisation_pk}/user-permissions/{id}/
Api v1 organisations user permissions destroy
api_v1_organisations_user_permissions_destroy 2 params → 204
GET
/api/v1/projects/{project_pk}/user-group-permissions/
Api v1 projects user group permissions list
api_v1_projects_user_group_permissions_list 1 param → 200
POST
/api/v1/projects/{project_pk}/user-group-permissions/
Api v1 projects user group permissions create
api_v1_projects_user_group_permissions_create 1 param body → 201
GET
/api/v1/projects/{project_pk}/user-group-permissions/{id}/
Api v1 projects user group permissions retrieve
api_v1_projects_user_group_permissions_retrieve 2 params → 200
PUT
/api/v1/projects/{project_pk}/user-group-permissions/{id}/
Api v1 projects user group permissions update
api_v1_projects_user_group_permissions_update 2 params body → 200
PATCH
/api/v1/projects/{project_pk}/user-group-permissions/{id}/
Api v1 projects user group permissions partial update
api_v1_projects_user_group_permissions_partial_update 2 params body → 200
DELETE
/api/v1/projects/{project_pk}/user-group-permissions/{id}/
Api v1 projects user group permissions destroy
api_v1_projects_user_group_permissions_destroy 2 params → 204
GET
/api/v1/projects/{project_pk}/user-permissions/
Api v1 projects user permissions list
api_v1_projects_user_permissions_list 1 param → 200
POST
/api/v1/projects/{project_pk}/user-permissions/
Api v1 projects user permissions create
api_v1_projects_user_permissions_create 1 param body → 201
GET
/api/v1/projects/{project_pk}/user-permissions/{id}/
Api v1 projects user permissions retrieve
api_v1_projects_user_permissions_retrieve 2 params → 200
PUT
/api/v1/projects/{project_pk}/user-permissions/{id}/
Api v1 projects user permissions update
api_v1_projects_user_permissions_update 2 params body → 200
PATCH
/api/v1/projects/{project_pk}/user-permissions/{id}/
Api v1 projects user permissions partial update
api_v1_projects_user_permissions_partial_update 2 params body → 200
DELETE
/api/v1/projects/{project_pk}/user-permissions/{id}/
Api v1 projects user permissions destroy
api_v1_projects_user_permissions_destroy 2 params → 204

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are UserList (6 properties), UserPermissionGroupMembership (6 properties), UserPermissionGroupSerializerDetail (5 properties), UserPermissionGroup (5 properties). Each schema is shown below with its type and property counts.

ListUserEnvironmentPermission
object
4 properties 1 required
UserOrganisationPermissionList
object
3 properties 1 required
CreateUpdateUserProjectPermission
object
4 properties 1 required
PatchedCreateUpdateUserEnvironmentPermission
object
4 properties
UserPermissionGroupSerializerDetail
object
5 properties 1 required
ListUserPermissionGroupEnvironmentPermission
object
4 properties 1 required
ListUserProjectPermission
object
4 properties 1 required
UserPermissionGroupOrganisationPermissionUpdateCreate
object
3 properties 1 required
PatchedUserPermissionGroupOrganisationPermissionUpdateCreate
object
3 properties
PatchedCreateUpdateUserPermissionGroupEnvironmentPermission
object
4 properties
UserPermissionGroupMembership
object
6 properties 3 required
CreateUpdateUserPermissionGroupEnvironmentPermission
object
4 properties 1 required
PatchedUserOrganisationPermissionUpdateCreate
object
3 properties
PatchedCreateUpdateUserProjectPermission
object
4 properties
CreateUpdateUserEnvironmentPermission
object
4 properties 1 required
ListUserPermissionGroupProjectPermission
object
4 properties 1 required
UserPermissionGroup
object
5 properties 1 required
PatchedCreateUpdateUserPermissionGroupProjectPermission
object
4 properties
UserOrganisationPermissionUpdateCreate
object
3 properties 1 required
CreateUpdateUserPermissionGroupProjectPermission
object
4 properties 1 required
UserPermissionGroupOrganisationPermissionList
object
3 properties 1 required
UserList
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flagsmith-permissions-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 Permissions 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.