CloudBees Unify is the modern, opinionated software delivery platform that unifies CI, CD, feature management, analytics, and security into a single workflow. The CloudBees Unify Public API is served from https://api.cloudbees.io and is published as two first-party OpenAPI 3.0.3 documents at apidocs.cloudbees.io: the "Current" specification (v1/v2/v3, 40 operations across organizations, teams, users, components, environments, feature flags, flag configurations, target groups, custom properties and flag lifecycle) and the "Beta" specification (v4, 25 operations across users, teams, team memberships, components and delivery runs with their artifacts, test results, security results, evidences and deployments). Both authenticate with a bearer personal access token. CloudBees directs new integrations at the v4 beta; the current endpoints remain supported but no longer receive new features.
CloudBees Unify Platform API is one of 12 APIs that CloudBees publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include DevOps, Platform, and Software Delivery. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and authentication docs.
This API exposes
40 operations
across 29 paths,
organized into 10 resource areas,
and defines 69 schemas.
It is described by OpenAPI 3.0.3, at version 1.0.0.
Requests are made against a single base URL, https://api.cloudbees.io.
40 operations29 paths69 schemas4 DELETE24 GET1 PATCH7 POST4 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.cloudbees.io
Authentication
HTTP Bearer
Resource Areas
10
Authentication & Security 1
CloudBees Unify Platform API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
By default, every request must be authenticated.
BearerAuth — CloudBees Unify API access token or personal access token
Paths & Operations 40
Across 29 paths, the API surfaces 40 operations — 4 DELETE, 24 GET, 1 PATCH, 7 POST, 4 PUT. They span 10 resource areas: Flag lifecycle, Organizations, Components, Teams, Flag custom properties, Flag configurations, Flags, Target groups, Environments, Users. Each is listed below with its method, path, parameters, and response codes.
Flag lifecycle 2
Track how often each feature flag variation is served within an environment. Use impression data to monitor flag adoption, validate rollout progress, and analyze which variations…
Define the structural and governance boundaries within a CloudBees Unify tenant. Organizations model business units or departments, support parent-child hierarchies, and inherit c…
GET
/v1/organizations
List organizations
listOrganizations12 params→ 200default
GET
/v1/organizations/name
Get organization by name
getOrganizationByName3 params→ 200default
Components 1
List components within an organization, and optionally filter by component type, such as applications or services with an associated repository.
GET
/v1/organizations/{orgId}/services
List applications and components
ServiceEndpoint_ListServices22 params→ 200default
Teams 1
List teams within an organization. Teams group users to manage access and permissions across resources in CloudBees Unify.
GET
/v1/organizations/{organizationId}/teams
List teams in an organization
TeamsService_GetTeams8 params→ 200default
Flag custom properties 8
Create, read, update, and delete custom properties used in targeting conditions and target groups.
Control runtime feature visibility and behavior to enable gradual rollouts, A/B testing, progressive delivery, and safe deployments without redeployment.
Define reusable sets of targeting conditions for feature flags. Specify rules once (such as matching users by role, region, or custom property) and apply them across multiple flag…
Discover and manage environments within your organization. Use environments to maintain an up-to-date inventory for feature flag targeting, deployment scripts, and monitoring work…
Invite or remove users, and define custom attributes for feature flag targeting based on application-specific criteria such as account tier, region, or subscription status.
The contract defines 69 schemas that model the data the API accepts and returns. The most detailed are api.auth.User (17 properties), api.auth.Organization (16 properties), api.auth.Team (16 properties), api.auth.Org (15 properties). Each schema is shown below with its type and property counts.
api.fmimpressions.GetFlagsStatusResponse
object
1 property1 required
api.fmimpressions.FlagStatus
object
2 properties2 required
google.rpc.Status
object
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](h…
3 properties
google.protobuf.Any
object
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
1 property
api.fmimpressions.ImpressionParams
object
Parameters controlling which feature flags and time window are included in the impressions response.
4 properties1 required
api.fmimpressions.GetImpressionsResponse
object
1 property1 required
api.fmimpressions.SdkKeyImpressions
object
1 property1 required
api.fmimpressions.AllFlagImpressions
object
1 property
api.fmimpressions.FlagImpression
object
2 properties
api.fmimpressions.ValuesAndCounters
object
2 properties2 required
api.auth.GetOrganizationsResponse
object
2 properties
api.auth.Organization
object
16 properties
api.Audit
object
Audit records the person that updated the data last.
3 properties
api.auth.Team
object
16 properties
api.auth.User
object
User will live in a separate database from the rest of the platform due to PII
17 properties
api.auth.Login
object
How a user logs in to the system
8 properties
api.auth.Org
object
15 properties
api.auth.Role
object
Roles are a collection of permission actions. PermissionActions can not be granted to a user directly, a role must be created.
8 properties3 required
api.auth.permission.Permission
object
Permission message represents a permission that can be granted to a user on an API entity.
2 properties2 required
api.auth.EmailDomain
object
6 properties
api.auth.Connection
object
13 properties
api.auth.Invite
object
Record of the invitation for a new user for an organization
9 properties
api.Pagination
object
Pagination is sent as part of a request to specify handling for paginated results, and returned with paginated results=
4 properties
api.Sort
object
Sort describes which field to sort the results on and the order in which to sort them
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of CloudBees Unify Platform 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.
