CloudBees · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for CloudBees Unify API (Current) Flag lifecycle API

3 actions 3 updates phrasing extends openapi/cloudbees-flag-lifecycle-api-openapi.yml

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

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info

$.paths['/v1/applications/{organizationId}/environments/{environmentId}/flags-status'].get

$.paths['/v1/applications/{organizationId}/environments/{environmentId}/impressions'].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 CloudBees Unify API (Current) Flag lifecycle API
  version: 1.0.0
extends: openapi/cloudbees-flag-lifecycle-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['/v1/applications/{organizationId}/environments/{environmentId}/flags-status'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the status of all flags in an environment
      effect: read
      questions:
      - What is the current status of every feature flag in an environment?
      - Can I see which flags in production look stale or inactive?
      instructions:
      - text: Show the status of all flags in environment {environmentId} of application {organizationId}.
        slots:
          environmentId: path.environmentId
          organizationId: path.organizationId
      - text: Get flag lifecycle statuses for env {environmentId} in app {organizationId}.
        slots:
          environmentId: path.environmentId
          organizationId: path.organizationId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/applications/{organizationId}/environments/{environmentId}/impressions'].post
  update:
    x-apievangelist-phrasing:
      intent: Get impression counts for feature flags
      effect: read
      questions:
      - How many times has a feature flag been evaluated over the last day?
      - Can I get daily impression data for a flag covering the last 30 days?
      - Is impression data available hourly as well as daily?
      instructions:
      - text: Get impressions for flag {flagname} in environment {environmentId} of app {organizationId}.
        slots:
          flagname: requestBody.flagname
          environmentId: path.environmentId
          organizationId: path.organizationId
      - text: Show {mode} impressions for flag {flagname} in env {environmentId}, app {organizationId}, from {from} to {to}.
        slots:
          mode: requestBody.mode
          flagname: requestBody.flagname
          environmentId: path.environmentId
          organizationId: path.organizationId
          from: requestBody.from
          to: requestBody.to
      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/cloudbees-flag-lifecycle-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.