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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Harness

Harness Feature Flags API

APIs to create and manage Feature Flags

Documentation Provider Profile APIs.io OpenAPI GitHub

Harness Feature Flags API is one of 488 APIs that Harness publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Feature Flags. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 8 operations across 4 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://app.harness.io, https://{vanity}.

8 operations 4 paths 28 schemas 1 DELETE3 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://app.harness.io
Authentication
API Key
Contact
API Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

Harness Feature Flags API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (x-api-key). By default, every request must be authenticated.

  • x-api-key — API key is a token provided while making the API calls. This is used to authenticate the client at the exposed endpoint.

Paths & Operations 8

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

Feature Flags 8

APIs to create and manage Feature Flags

GET
/cf/admin/features
Returns all Feature Flags for the project
GetAllFeatures 22 params → 200401403404500
POST
/cf/admin/features
Creates a Feature Flag
CreateFeatureFlag 2 params body → 201400401403409424500
DELETE
/cf/admin/features/{identifier}
Delete a Feature Flag
DeleteFeatureFlag 6 params → 204400401403404424500
GET
/cf/admin/features/{identifier}
Returns a Feature Flag
GetFeatureFlag 6 params → 200401403404500
PATCH
/cf/admin/features/{identifier}
Updates a Feature Flag
PatchFeature 5 params body → 200400401403404409424500
PUT
/cf/admin/features/{identifier}
Updates a Feature Flag
PutFeatureFlag 4 params body → 200400401403404409424500
GET
/cf/admin/features/{identifier}/dependants
Return a list of dependant flags
GetDependentFeatures 23 params → 200400401403404500
POST
/cf/admin/features/{identifier}/restore
Restore a Feature Flag
RestoreFeatureFlag 5 params → 204400401403404424500

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Feature (22 properties), FeatureCounts (8 properties), FeaturePipeline (5 properties), Pagination (5 properties). Each schema is shown below with its type and property counts.

ActivationUpdate
object
An object used to specify updates for flag activation updates
5 properties 1 required
Prerequisite
object
Feature Flag pre-requisites
2 properties 2 required
FeatureFlagRequestKind
string
FeaturePipeline
object
A pipeline configured to update a feature
5 properties 2 required
JiraIssue
object
A Jira Issue
2 properties 2 required
Tag
object
A Tag object used to tag feature flags - consists of name and identifier
2 properties 2 required
VariationMap
object
A mapping of variations to targets and target groups (segments). The targets listed here should receive this variation.
3 properties 1 required
Distribution
object
Describes a distribution rule
2 properties 2 required
FeatureCounts
object
8 properties
Serve
object
Describe the distribution rule and the variation that should be served to the target
2 properties
Results
object
This result object shows details of how many times a variation has been evaluated
3 properties 3 required
FeatureResponseMetadata
object
1 property
FeatureState
string
The state of a flag either off or on
TargetMap
object
Target map provides the details of a target that belongs to a flag
2 properties 2 required
GitSyncPatchOperation
object
4 properties 1 required
Pagination
object
5 properties 4 required
WeightedVariation
object
A variation and the weighting it should receive as part of a percentage rollout
2 properties 2 required
PatchInstruction
array
A list of Patch Instructions
CfGitDetails
object
The commit message to use as part of a gitsync operation
1 property 1 required
CCM
object
CCM Details for environment
3 properties 2 required
TargetRulesUpdate
object
An object used to specify updates for flag activation updates
2 properties 1 required
ServingRule
object
The rule used to determine what variation to serve to a target
4 properties 3 required
CfError
object
3 properties 2 required
Features
object
A list of Feature Flags
Clause
object
A clause describes what conditions are used to evaluate a flag
5 properties 4 required
Feature
object
A Feature Flag response
22 properties 8 required
Variation
object
A variation of a flag that can be returned to a target
4 properties 2 required
CfService
object
A Harness service linked to a flag
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-feature-flags-api-openapi.yml Raw ↑

Other APIs Harness publishes across the network.

Harness Continuous Integration API
AE Profile APIs.io
Harness Continuous Delivery and GitOps API
AE Profile APIs.io
Harness Feature Management and Experimentation API
AE Profile APIs.io
Harness Cloud Cost Management API
AE Profile APIs.io
Harness Chaos Engineering API
AE Profile APIs.io
Harness Security Testing Orchestration API
AE Profile APIs.io
Harness Internal Developer Portal API
AE Profile APIs.io
Harness Code Repository API
AE Profile APIs.io
Harness Service Reliability Management API
AE Profile APIs.io
Harness Infrastructure as Code Management API
AE Profile APIs.io
Harness Supply Chain Security API
AE Profile APIs.io
Harness Software Engineering Insights API
AE Profile APIs.io
#Feature Flags
← Back to H APIs
API Details
ID
harness:harness-feature-flags-api
Base URL
https://app.harness.io
Docs
https://apidocs.harness.io
Provider
Harness
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=harness-feature-flags-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/harness-feature-flags-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 Harness Feature Flags 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.