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

launchdarkly Custom Roles API

Define custom roles with fine-grained permissions using resource specifiers and actions.

launchdarkly Custom Roles API is one of 68 APIs that LaunchDarkly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Custom Roles. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 3 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://app.launchdarkly.com, https://app.launchdarkly.us, https://app.launchdarkly.com/api/v2.

7 operations 3 paths 31 schemas 1 DELETE3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://app.launchdarkly.com/api/v2
Authentication
API Key, HTTP Bearer
License
Resource Areas
1

Authentication & Security 2

launchdarkly Custom Roles API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (ApiKey). It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — LaunchDarkly API access token. Create personal or service tokens in the LaunchDarkly dashboard under Account Settings.

Paths & Operations 7

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

Custom roles 7

Custom roles is an Enterprise feature Custom roles is available to customers on an Enterprise plan. To learn more, read about our pricing. To upgrade your plan, contact Sales. Cus…

GET
/api/v2/roles
List custom roles
getCustomRoles 2 params → 200401403429
POST
/api/v2/roles
Create custom role
postCustomRole body → 201400401403409429
GET
/api/v2/roles/{customRoleKey}
Get custom role
getCustomRole 1 param → 200401403404429
PATCH
/api/v2/roles/{customRoleKey}
Update custom role
patchCustomRole 1 param body → 200400401404409429
DELETE
/api/v2/roles/{customRoleKey}
Delete custom role
deleteCustomRole 1 param → 204401404429
GET
/roles
List custom roles
listCustomRoles → 200401
POST
/roles
Create a custom role
createCustomRole body → 201400401409

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are CustomRole (12 properties), CustomRole_2 (6 properties), CustomRolePost (6 properties), AccessDeniedReason (6 properties). Each schema is shown below with its type and property counts.

JSONPatch
array
AccessDenied
object
2 properties 2 required
StatementPost
object
5 properties 1 required
CustomRolePost
object
6 properties 3 required
InvalidRequestErrorRep
object
2 properties 2 required
RateLimitedErrorRep
object
2 properties 2 required
AccessDeniedReason
object
6 properties 1 required
UnauthorizedErrorRep
object
2 properties 2 required
ForbiddenErrorRep
object
2 properties 2 required
ActionSpecifier
string
Link
object
2 properties
ActionIdentifier
string
ResourceCategory
string
RoleType
string
Statement
object
5 properties 1 required
PatchOperation
object
3 properties 2 required
StatementPostList
array
Access
object
2 properties 2 required
NotFoundErrorRep
object
2 properties 2 required
StatusConflictErrorRep
object
2 properties 2 required
CustomRole
object
12 properties 5 required
AccessAllowedReason
object
6 properties 1 required
PatchWithComment
object
2 properties 1 required
CustomRoles
object
3 properties 1 required
AccessAllowedRep
object
2 properties 2 required
AssignedToRep
object
2 properties
CustomRoles_2
object
A collection of custom roles.
2 properties
CustomRoleBody
object
The request body for creating a custom role.
4 properties 3 required
Links
object
HATEOAS links for navigating related resources.
1 property
CustomRole_2
object
A custom role with fine-grained permissions.
6 properties
Statement_2
object
A policy statement controlling resource access or event filtering.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

launchdarkly-custom-roles-api-openapi.yml Raw ↑

Other APIs LaunchDarkly publishes across the network.

LaunchDarkly Webhooks API
launchdarkly Access Tokens API
launchdarkly Account Members API
launchdarkly Approvals API
launchdarkly Audit Log API
launchdarkly Client-Side Evaluation API
launchdarkly Client-Side Streaming API
launchdarkly Code References API
launchdarkly Environments API
launchdarkly Experiments API
launchdarkly Feature Flags API
launchdarkly Flag Triggers API
Where this information came from

This is an independent, third-party profile of launchdarkly Custom Roles 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.