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 Execution Input API

APIs for runtime execution input on pipeline steps and stages.

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

Tagged areas include Execution Input. 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 3 operations across 2 paths, and defines 122 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}.

3 operations 2 paths 122 schemas 1 GET2 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 Execution Input 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 3

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

Execution Input 3

APIs for runtime execution input on pipeline steps and stages.

GET
/pipeline/api/pipeline/execution-input/{nodeExecutionId}
Get the template for Execution time inputs for any stage/step
getExecutionInputTemplate 4 params → 400500default
POST
/pipeline/api/pipeline/execution-input/{nodeExecutionId}
Submit the Execution Input for a Stage/Step and continue execution
submitExecutionInput 4 params body → 400500default
POST
/pipeline/api/pipeline/execution-input/variables
Get all the Variables which can be used as expression in the Pipeline at…
createVariablesForPipelineExecution 7 params → 400500default

Schemas 122

The contract defines 122 schemas that model the data the API accepts and returns. The most detailed are FileOptions (44 properties), FileOptionsOrBuilder (40 properties), FileDescriptorProto (38 properties), CvDescriptorProto (36 properties). Each schema is shown below with its type and property counts.

ParserMessageLite
object
UninterpretedOption
object
20 properties
FieldDescriptor
object
26 properties
ParserLocation
object
FieldOptionsOrBuilder
object
27 properties
EnumValueDescriptorProtoOrBuilder
object
11 properties
ParserEnumValueDescriptorProto
object
DescriptorProtoOrBuilder
object
31 properties
ParserFieldDescriptorProto
object
CvDescriptorProto
object
36 properties
Location
object
19 properties
FeatureSupport
object
14 properties
ExecutionInputDTO
object
Contains the template for Execution time inputs.
5 properties
ParserFeatureSupport
object
ExtensionRangeOrBuilder
object
10 properties
MessageOptionsOrBuilder
object
16 properties
TemplateDescriptorProtoOrBuilder
object
32 properties
ResponseDTOExecutionInputVariablesResponse
object
4 properties
OneofOptionsOrBuilder
object
11 properties
FieldDescriptorProtoOrBuilder
object
23 properties
ReservedRangeOrBuilder
object
8 properties
CvDescriptor
object
14 properties
ExtensionRange
object
13 properties
ParserFileDescriptorProto
object
FileOptions
object
44 properties
VariableMergeServiceResponse
object
This contains Pipeline YAML with the version.
4 properties
OneofDescriptor
object
9 properties
NamePart
object
12 properties
ParserReservedRange
object
ParserEnumOptions
object
YamlPropertiesOrBuilder
object
15 properties
ParserEditionDefault
object
ParserYamlOutputProperties
object
ServiceOptionsOrBuilder
object
12 properties
ServiceDescriptorProto
object
16 properties
ParserMethodDescriptorProto
object
ParserOneofDescriptorProto
object
ParserMessageOptions
object
DeclarationOrBuilder
object
13 properties
ServiceOptions
object
16 properties
UninterpretedOptionOrBuilder
object
17 properties
OneofOptions
object
15 properties
ServiceDescriptor
object
7 properties
ParserExtensionRange
object
ResponseMessage
object
7 properties
ParserUninterpretedOption
object
ParserFieldOptions
object
FeatureSetOrBuilder
object
12 properties
ParserServiceOptions
object
Descriptor
object
14 properties
MethodDescriptor
object
11 properties
ParserOneofOptions
object
SourceCodeInfo
object
13 properties
LocationOrBuilder
object
16 properties
FieldDescriptorProto
object
26 properties
ParserDescriptorProto
object
OneofDescriptorProto
object
13 properties
EditionDefaultOrBuilder
object
9 properties
EnumReservedRangeOrBuilder
object
8 properties
YamlProperties
object
18 properties
FileDescriptorProto
object
38 properties
PipelineErrorMetadata
object
This implements different error meta data objects
1 property
ExecutionInputStatus
object
Contains the Input Instance ID and the status If the Execution Input is valid
3 properties
ParserMethodOptions
object
ParserExtensionRangeOptions
object
ParserServiceDescriptorProto
object
PipelineError
object
This is Error entity as defined in Harness
7 properties
ServiceDescriptorProtoOrBuilder
object
13 properties
ParserFeatureSet
object
Message
object
8 properties
MethodDescriptorProtoOrBuilder
object
16 properties
ByteString
object
2 properties
ParserYamlProperties
object
ParserYamlExtraProperties
object
ParserMessage
object
YamlExtraProperties
object
15 properties
EnumOptionsOrBuilder
object
14 properties
ResponseDTOExecutionInputDTO
object
4 properties
EnumDescriptorProto
object
21 properties
ParserSourceCodeInfo
object
MethodOptionsOrBuilder
object
13 properties
EnumValueDescriptorProto
object
14 properties
ExecutionInputVariablesResponse
object
Contains the yaml that was used to execute
2 properties
ParserEnumValueOptions
object
ParserEnumDescriptorProto
object
UnknownFieldSet
object
6 properties
EnumValueOptions
object
19 properties
MethodDescriptorProto
object
19 properties
TemplateDescriptorProto
object
36 properties
FeatureSet
object
16 properties
EnumValueDescriptor
object
8 properties
ExtensionRangeOptions
object
19 properties
ParserDeclaration
object
EnumDescriptorProtoOrBuilder
object
18 properties
FeatureSupportOrBuilder
object
11 properties
EnumOptions
object
18 properties
EnumValueOptionsOrBuilder
object
15 properties
EditionDefault
object
12 properties
FileDescriptor
object
12 properties
ValidationError
object
2 properties
OneofDescriptorProtoOrBuilder
object
10 properties
MessageOptions
object
20 properties
FileOptionsOrBuilder
object
40 properties
ParserFileOptions
object
ServiceExpressionProperties
object
2 properties
YamlOutputProperties
object
13 properties
ResponseDTOExecutionInputStatus
object
4 properties
ParserEnumReservedRange
object
ParserNamePart
object
NamePartOrBuilder
object
9 properties
CvDeclaration
object
16 properties
VariableResponseMapValue
object
3 properties
ExtensionRangeOptionsOrBuilder
object
15 properties
Failure
object
This is Failure entity as defied in Harness
5 properties
MethodOptions
object
17 properties
MessageLite
object
4 properties
FieldOptions
object
31 properties
EnumReservedRange
object
11 properties
ReservedRange
object
11 properties
EnumDescriptor
object
9 properties
SourceCodeInfoOrBuilder
object
9 properties
Parser
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-execution-input-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 Execution Input 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.