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

Harness Infrastructure API

The infrastructure service for working with infrastructures

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

Tagged areas include Infrastructure. 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 9 operations across 8 paths, and defines 23 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}.

9 operations 8 paths 23 schemas 1 DELETE5 GET3 POST

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
Terms of Service
Resource Areas
1

Authentication & Security 1

Harness Infrastructure 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 9

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

Infrastructure 9

The infrastructure service for working with infrastructures

GET
/api/infrastructures
List Infrastructure
Infrastructure#List 6 params → 200400404409500501
POST
/api/infrastructures/{executionID}/abort
Abort Infrastructure
Infrastructure#Abort 2 params body → 200400404409500501
DELETE
/api/infrastructures/{id}
Delete Infrastructure
Infrastructure#Delete 4 params → 200400404409500501
GET
/api/infrastructures/{id}
Get Infrastructure
Infrastructure#Get 4 params → 200400404409500501
GET
/api/infrastructures/{id}/executions
ListExecutions Infrastructure
Infrastructure#ListExecutions 7 params → 200400404409500501
GET
/api/infrastructures/{id}/specs
ListSpecs Infrastructure
Infrastructure#ListSpecs 7 params → 200400404409500501
POST
/api/infrastructures/approve
ApprovePipelineExecution Infrastructure
Infrastructure#ApprovePipelineExecution 1 param body → 200400404409500501
POST
/api/infrastructures/execute
Execute Infrastructure
Infrastructure#Execute 3 params body → 200400404409500501
GET
/api/infrastructures/executions/{id}
GetExecution Infrastructure
Infrastructure#GetExecution 4 params → 200400404409500501

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are InfrastructureExecution (15 properties), PipelineApproval (8 properties), Steps (6 properties), InfraInstance (6 properties). Each schema is shown below with its type and property counts.

PipelineApproval
object
8 properties 5 required
SchemasRequestBody
object
Scope for the request, including account, org and project.
2 properties
ExecuteRequestBody
object
Scope for the request, including account, org and project.
3 properties 1 required
InfrastructureOutput
object
4 properties 3 required
InfrastructureSpec
object
3 properties
Infrastructure1
object
5 properties 2 required
ExecutionOutput
object
2 properties 1 required
InfrastructureState
object
4 properties
InfrastructureList
object
2 properties
InfrastructureExecutionList
object
2 properties
ExecutionEvent
object
3 properties 2 required
InfraInstance
object
6 properties 1 required
Dependency
object
2 properties 1 required
Steps
object
6 properties 2 required
InfrastructureProgress
object
1 property 1 required
Error
object
4 properties 2 required
State
object
1 property 1 required
Output
object
3 properties 1 required
ApprovePipelineExecutionRequestBody
object
3 properties 2 required
InfrastructureSpecList
object
2 properties
InstanceApproval
object
2 properties 2 required
Implementation
object
3 properties 2 required
InfrastructureExecution
object
15 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-infrastructure-api-openapi.yml Raw ↑

Other APIs Harness publishes across the network.

Harness Continuous Integration API
Harness Continuous Delivery and GitOps API
Harness Feature Management and Experimentation API
Harness Cloud Cost Management API
Harness Chaos Engineering API
Harness Security Testing Orchestration API
Harness Internal Developer Portal API
Harness Code Repository API
Harness Service Reliability Management API
Harness Infrastructure as Code Management API
Harness Supply Chain Security API
Harness Software Engineering Insights API
Where this information came from

This is an independent, third-party profile of Harness Infrastructure 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.