Harness

Harness Pipeline Input Set API

This contains APIs related to Input Sets

GitHub OpenAPI

Operations 14

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

GET /pipeline/api/inputSets List a pipeline's input sets · List Input Sets #
Ask an LLM
“What input sets have been saved for a pipeline?”
“Can I list only overlay input sets, or search input sets by name?”
Tell an agent
List the input sets for pipeline {pipelineIdentifier} in project {projectIdentifier}.
Show {inputSetType} input sets of pipeline {pipelineIdentifier}.
POST /pipeline/api/inputSets 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 a new input set be stored in a Git repo on a new branch?”
Tell an agent
Create an input set for pipeline {pipelineIdentifier} in project {projectIdentifier}.
Save a new input set for pipeline {pipelineIdentifier} to {filePath} on branch {branch}.
POST /pipeline/api/inputSets/overlay Create an overlay input set · Create an Overlay Input Set for a pipeline #
Ask an LLM
“Can I combine several input sets into one overlay input set?”
“Where would a new overlay input set be committed if I keep it in Git?”
Tell an agent
Create an overlay input set for pipeline {pipelineIdentifier}.
Add an overlay input set to pipeline {pipelineIdentifier} with commit message {commitMsg}.
GET /pipeline/api/inputSets/{inputSetIdentifier} Get a regular input set · Fetch an Input Set #
Ask an LLM
“What values are stored in a particular input set?”
“Can I read an input set from a specific Git branch?”
Tell an agent
Show input set {inputSetIdentifier} of pipeline {pipelineIdentifier}.
Fetch input set {inputSetIdentifier} from branch {branch}.
PUT /pipeline/api/inputSets/{inputSetIdentifier} Update a regular input set · Update an Input Set #
Ask an LLM
“How do I change the values in an existing input set?”
“Can I commit an input set update to Git with my own message?”
Tell an agent
Update input set {inputSetIdentifier} for pipeline {pipelineIdentifier}.
Save changes to input set {inputSetIdentifier} on branch {branch} with message {commitMsg}.
DELETE /pipeline/api/inputSets/{inputSetIdentifier} Delete an input set · Delete an Input Set #
Ask an LLM
“How do I delete an input set I no longer use?”
“Does deleting a Git-backed input set create a commit?”
Tell an agent destructive · confirm first
Delete input set {inputSetIdentifier} from pipeline {pipelineIdentifier}.
Remove input set {inputSetIdentifier} with commit message {commitMsg}.
POST /pipeline/api/inputSets/get/batch-input-sets-metadata List input sets across several pipelines · List regular Input Sets for multiple pipelines (excludes overlay input sets) #
Ask an LLM
“Can I see the regular input sets for many pipelines in one call?”
“Are overlay input sets included when listing input sets across pipelines?”
Tell an agent
List regular input sets for pipelines {pipelineIdentifiers}.
Show every accessible input set in project {projectIdentifier}, across all pipelines.
POST /pipeline/api/inputSets/get/bulk Fetch several input sets by id · Get multiple input sets by identifiers (non-deleted only) #
Ask an LLM
“Can I fetch a handful of input sets by their identifiers at once?”
“Will a bulk input set lookup return ones that were deleted?”
Tell an agent
Get input sets {inputSetIdentifiers} of pipeline {pipelineIdentifier} in one call.
Bulk fetch input sets {inputSetIdentifiers}.
POST /pipeline/api/inputSets/merge Merge input sets into one runtime YAML · Merge given Input Sets into a single Runtime Input YAML #
Ask an LLM
“What runtime input YAML results from combining several input sets?”
“Can I preview merged input sets alongside the merged pipeline YAML?”
Tell an agent
Merge input sets {inputSetReferences} for pipeline {pipelineIdentifier} into one runtime input YAML.
Combine input sets {inputSetReferences} for stages {stageIdentifiers} only.
GET /pipeline/api/inputSets/overlay/{inputSetIdentifier} Get an overlay input set · Gets an Overlay Input Set by identifier #
Ask an LLM
“Which input sets does a given overlay input set reference?”
“Can I read an overlay input set from a fallback branch?”
Tell an agent
Show overlay input set {inputSetIdentifier} for pipeline {pipelineIdentifier}.
Get overlay input set {inputSetIdentifier} from branch {branch}.
PUT /pipeline/api/inputSets/overlay/{inputSetIdentifier} Update an overlay input set · Update an Overlay Input Set for a pipeline #
Ask an LLM
“How do I change which input sets an overlay combines?”
“Can an overlay input set edit go to a new Git branch?”
Tell an agent
Update overlay input set {inputSetIdentifier} of pipeline {pipelineIdentifier}.
Commit my overlay input set {inputSetIdentifier} changes to branch {branch}.
POST /pipeline/api/inputSets/template Get a pipeline's runtime input template · Fetch Runtime Input Template #
Ask an LLM
“Which runtime inputs does a pipeline expect before it can run?”
“Can I get the input template for just certain stages?”
Tell an agent
Get the runtime input template for pipeline {pipelineIdentifier}.
Show the runtime inputs needed by stages {stageIdentifiers} of pipeline {pipelineIdentifier}.
GET /pipeline/api/inputSets/refresh-and-get/{inputSetIdentifier} Refresh a remote input set from Git · Refresh cache and fetch an Input Set #
Ask an LLM
“How do I force Harness to reload a Git-stored input set instead of using its cache?”
“Is a branch required when refreshing a remote input set?”
Tell an agent
Refresh the Git cache for input set {inputSetIdentifier} on branch {branch} and return it.
Re-pull remote input set {inputSetIdentifier} of pipeline {pipelineIdentifier} from branch {branch}.
PUT /pipeline/api/inputSets/{inputSetIdentifier}/update-git-metadata Change a remote input set's Git location · Update git-metadata in remote input-set #
Ask an LLM
“Can I point a remote input set at a different repo or file path?”
“What Git metadata of an input set can be changed?”
Tell an agent
Move input set {inputSetIdentifier}'s Git file path to {filePath}.
Point input set {inputSetIdentifier} at repo {repoName} via connector {connectorRef}.

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