Harness Overrides API

This contains APIs related to Overrides

Operations 11

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

PUT /ng/api/overrides Update a service or environment override · Update an Override Entity #
Ask an LLM
“How do I change the values in an existing environment or service override?”
“Can I edit the YAML of an infrastructure-specific deployment override?”
Tell an agent
Update the {type} override for environment {environment} with this YAML: {yaml}.
Change the existing {type} override on environment {environment} for service {service}.
POST /ng/api/overrides Create a service or environment override · Create an Override Entity #
Ask an LLM
“How do I override variables or manifests for one service in a specific environment?”
“Can I create a deployment override that applies only to a single infrastructure?”
Tell an agent
Create a new {type} override for service {service} in environment {environment}.
Add a {type} override for infrastructure {infra} in environment {environment}.
GET /ng/api/overrides/{identifier} Get a deployment override by identifier · Gets Overrides by Identifier #
Ask an LLM
“What values does a particular service or environment override set?”
“Can I read a deployment override's YAML by its identifier?”
Tell an agent
Get deployment override {identifier} in account {account}.
Show the YAML of environment override {identifier} in project {project}.
DELETE /ng/api/overrides/{identifier} Delete a deployment override · Delete a Override entity #
Ask an LLM
“How do I remove a service or environment override so defaults apply again?”
“Can I delete a deployment override at org or project scope?”
Tell an agent destructive · confirm first
Delete deployment override {identifier} in account {account}.
Remove the environment override {identifier} from project {project}.
POST /ng/api/overrides/move-config Move an override between inline and Git storage · Move Override YAML from inline to remote or remote to inline #
Ask an LLM
“Can I move an override's YAML out of Harness and into a Git repo?”
“How do I bring a remote override stored in Git back inline?”
Tell an agent
Move override {identifier} to remote Git repo {repo} at {file_path} on branch {branch}.
Move override {identifier} with move type {move_type}.
PUT /ng/api/overrides/update-git-metadata Update Git metadata of a remote override · Update git-metadata in remote Override Entity #
Ask an LLM
“If I moved an override's file in Git, how do I update the path Harness points to?”
“Can I change the connector or repo recorded for a remote override?”
Tell an agent
Update remote override {identifier} to point at {file_path} in repo {repo}.
Set Git connector {connector} on remote override {identifier}.
GET /sto/api/v2/overrides List security issue overrides · Overrides#List overrides #
Ask an LLM
“Which security scan findings have had their severity or status overridden in STO?”
“Can I list security test overrides for one project?”
Tell an agent
List STO issue overrides in account {account}.
Show security issue overrides for project {project} in org {org}, account {account}.
POST /sto/api/v2/overrides Override a field on a security issue · Overrides#Create override #
Ask an LLM
“How do I change the severity of a security finding STO reported, with a reason?”
“Can a security issue override also apply to future occurrences of the same issue?”
Tell an agent
Override {field} to {value} on security issue {issue} because {reason}, requested by {requester}.
In project {project}, set issue {issue}'s {field} to {value} with reason {reason} for requester {requester}.
DELETE /sto/api/v2/overrides/{id} Delete a security issue override · Overrides#Delete override #
Ask an LLM
“How do I undo a security finding override so the original value shows again?”
“Which field name do I need to supply to delete an STO override?”
Tell an agent destructive · confirm first
Delete STO override {id} for field {field} in account {account}.
Remove the {field} override {id} from the security issue.
GET /sto/api/v2/overrides/{id} Get a security issue override · Overrides#Find override by id #
Ask an LLM
“Who overrode this security finding, and what reason did they give?”
“Can I look up a single STO override by its ID?”
Tell an agent
Get security issue override {id} in account {account}.
Show the reason and requester on STO override {id}.
PUT /sto/api/v2/overrides/{id} Update a security issue override · Overrides#Update override #
Ask an LLM
“Can I change the new severity value on a security override I already made?”
“How do I update the reason on an existing STO override?”
Tell an agent
Change STO override {id} so {field} is {value}, reason {reason}, requested by {requester}.
Update the {field} value on security override {id} to {value} because {reason}; requester {requester}.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/harness:harness-overrides-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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

OpenAPI Specification

harness-overrides-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Harness Overrides API
  version: '1.0'
  description: The Harness Software Delivery Platform uses OpenAPI Specification v3.0.
  contact:
    name: API Support
    email: contact@harness.io
    url: https://harness.io/
  x-logo:
    url: https://mma.prnewswire.com/media/779232/Harnes_logo_horizontal.jpg?p=facebook
    altText: Harness
  termsOfService: https://harness.io/terms-of-use/
servers:
- url: https://app.harness.io
  description: Harness host URL
- url: https://{vanity}
  description: Vanity URL
  variables:
    vanity:
      default: app.harness.io
security:
- x-api-key: []
tags:


# --- truncated at 32 KB (232 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/openapi/harness-overrides-api-openapi.yml