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

This contains APIs related to Trigger Event History.

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

Tagged areas include TriggersEvents. 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 6 operations across 6 paths, and defines 25 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}.

6 operations 6 paths 25 schemas 6 GET

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 Events 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 6

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

TriggersEvents 6

This contains APIs related to Trigger Event History.

GET
/pipeline/api/triggers/eventHistory/polledResponse/{triggerIdentifier}
Get all the polled response for a given trigger
polledResponseTriggerIdentifier 5 params → 400500default
GET
/pipeline/api/triggers/eventHistory/{triggerIdentifier}
Get event history for a trigger
triggerEventHistoryNew 10 params → 400500default
GET
/pipeline/api/triggers/eventHistory/events
Get event history for a trigger using filters
triggerEventHistoryUsingFilters 9 params → 400500default
GET
/pipeline/api/triggers/eventHistory/eventCorrelation/{eventCorrelationId}
Get Trigger history event correlation
triggerHistoryEventCorrelation 5 params → 400500default
GET
/pipeline/api/triggers/eventHistory/v2/eventCorrelation/{eventCorrelationId}
Get Trigger history event correlation V2
triggerHistoryEventCorrelationV2 5 params → 400500default
GET
/pipeline/api/triggers/eventHistory/artifact-manifest-info
Get artifact and manifest trigger event history based on build source type
triggerEventHistoryBuildSourceType 9 params → 400500default

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are NGTriggerEventHistoryDTO (17 properties), NGTriggerEventHistoryBaseDTO (11 properties), PageNGTriggerEventHistoryBaseDTO (11 properties), PageNGTriggerEventsApiResponse (11 properties). Each schema is shown below with its type and property counts.

ResponseDTOPageNGTriggerEventHistoryBaseDTO
object
4 properties
NGTriggerEventsApiResponse
object
10 properties 1 required
PipelineErrorMetadata
object
This implements different error meta data objects
1 property
ValidationError
object
2 properties
PollingInfoForTriggers
object
4 properties
Sort
object
3 properties
PipelineError
object
This is Error entity as defined in Harness
7 properties
PolledResponse
object
1 property
NGTriggerEventInfo
object
TriggerEventStatus
object
2 properties
Pageable
object
6 properties
NGTriggerEventHistoryBaseDTO
object
11 properties
NGTriggerEventHistoryDTO
object
17 properties
Failure
object
This is Failure entity as defied in Harness
5 properties
ResponseDTOPollingInfoForTriggers
object
4 properties
TargetExecutionSummary
object
7 properties
PipelineScope
object
4 properties 1 required
PageNGTriggerEventsApiResponse
object
11 properties
PageNGTriggerEventHistoryDTO
object
11 properties
NGTriggerMetaData
object
2 properties
ResponseMessage
object
7 properties
ResponseDTOPageNGTriggerEventsApiResponse
object
4 properties
PageNGTriggerEventHistoryBaseDTO
object
11 properties
PerpetualTaskInfoForTriggers
object
6 properties
ResponseDTOPageNGTriggerEventHistoryDTO
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-triggersevents-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 Events 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.