API Schema and Structure
Harness' schema determines what parameters your queries can specify as arguments, and what data can be returned.
Following GraphQL conventions, Harness schema is represented in terms of fields, types, enums, nodes, edges, and connections.
!following the type means that this field is required.
In this topic:
Before You Begin
The Harness API's schema includes fields representing the following Harness entities. Note that many of these
<entity> fields are also transformed within the schema into an
<entity>Filter. Use the API Explorer's search box to discover the available fields and their usage.
A Harness deployment (execution).
Artifact deployed via Harness.
Cloud Provider configured in Harness.
Instance deployed via Harness.
Connector configured in Harness.
Description of a Workflow, Pipeline, etc.
Unique ID of a Harness entity.
Name of a Workflow, Pipeline, etc.
Total number of a parent Harness entity.
Deployment's execution status.
Time when deployment was queued in Harness.
Time when deployment's execution began.
Used to group returned statistics (on deployments, instances, etc.) by time.
One or more Harness Triggers.