Harness

Harness Input Sets API

This contains APIs for Input Sets.

GitHub OpenAPI

Operations 9

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

POST /v1/orgs/{org}/projects/{project}/input-sets Create an input set for a pipeline · Create an Input Set #
Ask an LLM
“How do I save a reusable set of runtime inputs for a pipeline?”
“Can I store a new input set in Git instead of inline?”
Tell an agent
Create input set {identifier} named {name} for pipeline {pipeline} in project {project} of {org} using YAML {input_set_yaml}.
Add a new input set {name} to pipeline {pipeline} with this YAML: {input_set_yaml}.
GET /v1/orgs/{org}/projects/{project}/input-sets List a pipeline's input sets · List Input Sets #
Ask an LLM
“Which input sets are saved for one of my pipelines?”
“Can I search a pipeline's input sets by name and sort them?”
Tell an agent
List the input sets for pipeline {pipeline} in project {project} of org {org}.
Find input sets on pipeline {pipeline} in {project} whose name matches {search_term}.
GET /v1/orgs/{org}/projects/{project}/input-sets/{input-set} Retrieve an input set · Retrieve an Input Set #
Ask an LLM
“What runtime values does a particular input set supply to my pipeline?”
“Can I load an input set's YAML from a specific Git branch?”
Tell an agent
Show input set {input_set} of pipeline {pipeline} in project {project} under {org}.
Fetch input set {input_set} for pipeline {pipeline} from branch {branch_name}.
PUT /v1/orgs/{org}/projects/{project}/input-sets/{input-set} Update an input set · Update an Input Set #
Ask an LLM
“How do I change the values stored in an existing input set?”
“Can I rename an input set I already saved on a pipeline?”
Tell an agent
Update input set {input_set} on pipeline {pipeline} in {project} of {org} with YAML {input_set_yaml}.
Rename existing input set {input_set} (id {identifier}) on pipeline {pipeline} to {name}, keeping YAML {input_set_yaml}.
DELETE /v1/orgs/{org}/projects/{project}/input-sets/{input-set} Delete an input set · Delete an Input Set #
Ask an LLM
“How do I remove an input set I no longer need from a pipeline?”
“Can I delete one input set without touching the pipeline itself?”
Tell an agent destructive · confirm first
Delete input set {input_set} from pipeline {pipeline} in project {project} of {org}.
Remove the {input_set} input set from pipeline {pipeline}.
POST /v1/orgs/{org}/projects/{project}/input-sets/{input-set}/move-config Move an inline input set to Git · Move InputSet YAML from inline to remote #
Ask an LLM
“How do I move an input set stored inline in Harness into a Git repository?”
“Can I convert an inline input set to a remote one?”
Tell an agent
Move input set {input_set} in project {project} of {org} from inline to remote Git storage.
Push the YAML of input set {input_set} for pipeline {pipeline_identifier} to Git with details {git_details}.
POST /v1/orgs/{org}/projects/{project}/input-sets/{input-set}/import Import an input set from a Git repository · Get Input Set YAML from Git Repository #
Ask an LLM
“Can I import an input set YAML that already lives in my Git repo?”
“How do I register a Git-stored input set with a pipeline?”
Tell an agent
Import input set {input_set} for pipeline {pipeline} in project {project} of {org} from Git.
Pull the input set {input_set} YAML from Git using {git_import_info} and save it for pipeline {pipeline}.
PUT /v1/orgs/{org}/projects/{project}/input-sets/{input-set}/git-metadata Update Git metadata of a remote input set · Update GitMetadata for Remote InputSet #
Ask an LLM
“How do I point a remote input set at a different repo or file path?”
“Can I change the connector used by a Git-backed input set?”
Tell an agent
Update the Git metadata of remote input set {input_set} on pipeline {pipeline} in {project} of {org} to repo {repo_name}.
Set file path {file_path} and connector {connector_ref} on remote input set {input_set}.
POST /v1/orgs/{org}/projects/{project}/input-sets/merge Merge several input sets for a pipeline · Merged input sets #
Ask an LLM
“What do my runtime inputs look like when several input sets are combined?”
“Can I get the merged pipeline YAML for a chosen set of input sets and stages?”
Tell an agent
Merge input sets {input_set_references} for pipeline {pipeline} in project {project} of {org}.
Combine input sets {input_set_references} on pipeline {pipeline} for stages {stage_identifiers} only.

Documentation

📖
Documentation
https://apidocs.harness.io
📖
APIReference
https://apidocs.harness.io
📖
GettingStarted
https://developer.harness.io/docs/platform/automation/api/api-quickstart/
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/authentication/harness-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/rate-limits/harness-rate-limits.yml

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/openapi/harness-input-sets-api-openapi.yml

Other Resources

🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/scopes/harness-scopes.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/errors/harness-error-codes.yml
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/conventions/harness-conventions.yml
🔗
Idempotency
https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/conventions/harness-conventions.yml

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-input-sets-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.

GitHub Google LinkedIn

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

OpenAPI Specification

harness-input-sets-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Harness Input Sets 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 (60 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/openapi/harness-input-sets-api-openapi.yml