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 Triggers API

This contains APIs for performing CRUD operations on Triggers.

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

Tagged areas include Triggers. 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 14 operations across 9 paths, and defines 41 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}.

14 operations 9 paths 41 schemas 2 DELETE6 GET3 POST3 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 Triggers 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 14

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

Triggers 14

This contains APIs for performing CRUD operations on Triggers.

POST
/v1/orgs/{org}/projects/{project}/pipelines/{pipeline}/triggers
Create a Trigger
create-trigger 5 params body → 201
GET
/v1/orgs/{org}/projects/{project}/pipelines/{pipeline}/triggers/{trigger}
Retrieve a Trigger
get-trigger 5 params → 200
PUT
/v1/orgs/{org}/projects/{project}/pipelines/{pipeline}/triggers/{trigger}
Update a Trigger
update-trigger 6 params body → 200
DELETE
/v1/orgs/{org}/projects/{project}/pipelines/{pipeline}/triggers/{trigger}
Delete a Trigger
delete-trigger 5 params → 204400
GET
/pipeline/api/triggers
Gets the paginated list of triggers for accountIdentifier, orgIdentifier…
getListForTarget 9 params body → 400500default
POST
/pipeline/api/triggers
Creates Trigger for triggering target pipeline identifier
createTrigger 6 params body → 400500default
POST
/pipeline/api/triggers/v2
Creates Trigger with executor identity in request body (v2 API)
createTriggerV2 6 params body → 400500default
GET
/pipeline/api/triggers/{triggerIdentifier}
Gets the trigger by accountIdentifier, orgIdentifier, projectIdentifier…
getTrigger 5 params → 400500default
PUT
/pipeline/api/triggers/{triggerIdentifier}
Updates trigger for pipeline with target pipeline identifier
updateTrigger 7 params body → 400500default
DELETE
/pipeline/api/triggers/{triggerIdentifier}
Deletes Trigger by identifier
deleteTrigger 6 params → 400500default
GET
/pipeline/api/triggers/catalog
Lists all Triggers
getTriggerCatalog 1 param → 400500default
GET
/pipeline/api/triggers/{triggerIdentifier}/details
Fetches Trigger details for a specific accountIdentifier, orgIdentifier…
getTriggerDetails 5 params → 400500default
GET
/pipeline/api/triggers/{triggerIdentifier}/eventHistorydeprecated
Get event history for a trigger
triggerEventHistory 9 params → 400500default
PUT
/pipeline/api/triggers/{triggerIdentifier}/v2
Updates trigger with executor identity in request body (v2 API)
updateTriggerV2 7 params body → 400500default

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are NGTriggerDetailsResponseDTO (19 properties), NGTriggerEventHistoryDTO (17 properties), NGTriggerResponse (16 properties), TriggerRequestBody (11 properties). Each schema is shown below with its type and property counts.

NGTriggerResponse
object
This contains the trigger details
16 properties
ResponseDTOPageResponseNGTriggerDetailsResponseDTO
object
4 properties
NGTriggerYamlRequest
object
Trigger YAML and optional executor identity for create/update
2 properties 1 required
PipelineErrorMetadata
object
This implements different error meta data objects
1 property
ValidationStatus
object
2 properties
TriggerSource
object
3 properties 2 required
ValidationError
object
2 properties
TriggerGetResponseBody
object
Trigger response body.
7 properties
ParameterFieldListString
object
9 properties
PollingSubscriptionStatus
object
5 properties
Sort
object
3 properties
PipelineError
object
This is Error entity as defined in Harness
7 properties
WebhookDetails
object
2 properties
TriggerRequestBody
object
Trigger request body object
11 properties 4 required
TriggerExecutor
object
Details of a user or service account eligible to execute a trigger. For create/update requests, 'uuid' and 'type' are required. For SERVICEACCOUNT executors, a…
7 properties 2 required
NGTriggerEventInfo
object
TriggerEventStatus
object
2 properties
Pageable
object
6 properties
WebhookInfo
object
1 property
TriggerBody
object
Trigger object
8 properties 3 required
NGTriggerEventHistoryDTO
object
17 properties
ResponseDTOBoolean
object
4 properties
Failure
object
This is Failure entity as defied in Harness
5 properties
TriggerResponseBody
object
Pipeline response body
1 property
BuildDetails
object
1 property
TargetExecutionSummary
object
7 properties
ResponseDTOTriggerCatalogResponse
object
4 properties
ResponseDTONGTriggerDetailsResponseDTO
object
4 properties
PageResponseNGTriggerDetailsResponseDTO
object
8 properties
TriggerCatalogItem
object
This has details of the Trigger Catalog.
2 properties 2 required
PageNGTriggerEventHistoryDTO
object
11 properties
ResponseDTONGTriggerResponse
object
4 properties
LastTriggerExecutionDetails
object
5 properties
ResponseMessage
object
7 properties
WebhookAutoRegistrationStatus
object
2 properties
TriggerStatus
object
8 properties
ResponseDTOPageNGTriggerEventHistoryDTO
object
4 properties
TriggerCatalogResponse
object
This has details of the retrieved Trigger Catalog.
1 property 1 required
TriggerFilterProperties
object
This contains details of the Trigger Filter
5 properties 1 required
NGTriggerDetailsResponseDTO
object
19 properties
InputSetValidator
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-triggers-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 Triggers 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.