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 Orchestration Processes API

The Orchestration Processes API from Harness — 7 operation(s) for orchestration processes.

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

Tagged areas include Orchestration Processes. 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 11 operations across 7 paths, and defines 8 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}.

11 operations 7 paths 8 schemas 2 DELETE4 GET3 POST2 PUT

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 Orchestration Processes 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 11

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

Orchestration Processes 11
POST
/rmg/api/orchestration/process
Create Orchestration Process
post-orchestrationProcess 3 params body → 200400403500
GET
/rmg/api/orchestration/process/summary
Fetch List of Orchestration Processes
get-orchestrationProcess-summary 7 params → 200400403404500
GET
/rmg/api/orchestration/process/{identifier}
Get Orchestration Process
get-orchestrationProcess 4 params → 200400404500
PUT
/rmg/api/orchestration/process/{identifier}
Update Orchestration Process
put-orchestration-process 4 params body → 200400403404500
DELETE
/rmg/api/orchestration/process/{identifier}
Delete Orchestration Process
delete-orchestration-process 4 params → 204400403404500
POST
/rmg/api/orchestration/process/{identifier}/input
Create Orchestration Process Input
post-orchestrationProcessInput 4 params body → 200400403404500
GET
/rmg/api/orchestration/process/{processIdentifier}/input/{identifier}
Get Orchestration Process Input
get-orchestration-process-input 5 params → 200400403404500
PUT
/rmg/api/orchestration/process/{processIdentifier}/input/{identifier}
Update Orchestration Process Input
put-orchestration-process-input 5 params body → 200400403404500
DELETE
/rmg/api/orchestration/process/{processIdentifier}/input/{identifier}
Delete Orchestration Process Input
delete-orchestration-process-input 5 params → 204400403404500
GET
/rmg/api/orchestration/process/{processIdentifier}/input/summary
Fetch List of Orchestration Process Inputs
get-orchestration-process-input-summary 8 params → 200400403404500
POST
/rmg/api/orchestration/process/{identifier}/attachedReleaseGroups
Fetch List of Attached Release Groups for Orchestration Process
post-orchestrationProcess-attachedReleaseGroups 8 params body → 200400403404500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are OrchestrationProcessDTO (8 properties), ProcessInputSummaryDTO (6 properties), AttachedReleaseGroupDTO (6 properties), RmPageable (6 properties). Each schema is shown below with its type and property counts.

RmError
object
Error Response
2 properties 1 required
AttachedReleaseGroupDTO
object
6 properties 4 required
CreatedByDTO
object
Details of the user who created the event
3 properties 2 required
ProcessInputSummaryDTO
object
6 properties 5 required
RmPageable
object
6 properties
LastUpdatedByDTO
object
3 properties 1 required
PageableSort
object
3 properties
OrchestrationProcessDTO
object
8 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-orchestration-processes-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 Orchestration Processes 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.