LaunchDarkly · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for LaunchDarkly REST Approvals API

3 actions 3 updates phrasing extends openapi/launchdarkly-approvals-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for LaunchDarkly's API. It is a proposal applied on top of the contract, not a document LaunchDarkly publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info

$.paths['/flags/{projectKey}/{flagKey}/approval-requests/{environmentKey}'].get

$.paths['/flags/{projectKey}/{flagKey}/approval-requests/{environmentKey}'].post

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for LaunchDarkly REST Approvals API
  version: 1.0.0
extends: openapi/launchdarkly-approvals-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/flags/{projectKey}/{flagKey}/approval-requests/{environmentKey}'].get
  update:
    x-apievangelist-phrasing:
      intent: List approval requests for a flag
      effect: read
      questions:
      - Which approval requests are open on this feature flag?
      - Can I see approval requests for a flag in just one environment?
      - How do I check who has asked for sign-off on a flag change?
      instructions:
      - text: List approval requests for flag {flagKey} in project {projectKey}, environment {environmentKey}.
        slots:
          flagKey: path.flagKey
          projectKey: path.projectKey
          environmentKey: path.environmentKey
      - text: Show pending approvals for {flagKey} in {environmentKey} of {projectKey}.
        slots:
          flagKey: path.flagKey
          environmentKey: path.environmentKey
          projectKey: path.projectKey
      method: generated
      generated: '2026-09-26'
- target: $.paths['/flags/{projectKey}/{flagKey}/approval-requests/{environmentKey}'].post
  update:
    x-apievangelist-phrasing:
      intent: Request approval for a flag change
      effect: write
      questions:
      - How do I ask for approval before changing a flag in production?
      - Can I notify specific teammates when I request a flag approval?
      - What does an approval request need besides a description?
      instructions:
      - text: 'Request approval to change {flagKey} in {environmentKey} of project {projectKey}: {description}.'
        slots:
          flagKey: path.flagKey
          environmentKey: path.environmentKey
          projectKey: path.projectKey
          description: requestBody.description
      - text: Submit an approval request for {flagKey} in {projectKey}/{environmentKey} and notify {notifyMemberIds}.
        slots:
          flagKey: path.flagKey
          projectKey: path.projectKey
          environmentKey: path.environmentKey
          notifyMemberIds: requestBody.notifyMemberIds
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this

find_overlaysBrowse and filter every overlay in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This overlay

curl "https://apis.io/api/v1/overlays/launchdarkly-approvals-api-phrasing-overlay"

All openapi overlays

curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.