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 STO Data Frontend API

Endpoints that power the other modules micro-frontend with STO data

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

Tagged areas include STO Data Frontend. 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 14 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 14 schemas 1 GET5 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 STO Data Frontend 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 — 1 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

STO Data Frontend 6

Endpoints that power the other modules micro-frontend with STO data

POST
/sto/api/v2/sto-data-frontend/all-issues/filters
Distinct filter values for selected targets and variants
STODataFrontend#AllIssuesFilters 3 params body → 200400401403404429500
POST
/sto/api/v2/sto-data-frontend/all-issues/issues
List of issues for selected targets and variants
STODataFrontend#AllIssuesList 3 params body → 200400401403404429500
POST
/sto/api/v2/sto-data-frontend/artifact-scan-summary
STO data FrontendExecution artifact scan summary
STODataFrontend#ExecutionArtifactScanSummary 3 params body → 200400401403404429500
POST
/sto/api/v2/sto-data-frontend/artifact-summary
STO data FrontendExecution artifact summary
STODataFrontend#ExecutionArtifactSummary 3 params body → 200400401403404429500
GET
/sto/api/v2/sto-data-frontend/execution-summary/{executionId}
STO data FrontendExecution summary
STODataFrontend#ExecutionSummary 4 params → 200400401403404429500
POST
/sto/api/v2/sto-data-frontend/issue-counts
STO data FrontendExecution issue counts
STODataFrontend#ExecutionIssueCounts 3 params body → 200400401403404429500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are IssueCountsWithExecutionInfo (15 properties), AllIssuesListRequestBody (10 properties), ScanIssueCountsWithExecutionInfo (10 properties), AllIssueSummaryV2 (9 properties). Each schema is shown below with its type and property counts.

TargetAndVariantNameRequired
object
3 properties 2 required
AllIssuesListRequestBody
object
10 properties
ExecutionArtifactSummaryRequestBody
object
2 properties
TargetAndVariantName
object
3 properties
FrontendIssueCounts
object
7 properties 6 required
NotFound
object
2 properties 1 required
StoPagination
object
5 properties 4 required
ExecutionIssueCountsRequestBody
object
1 property
AllIssuesListResultV2
object
3 properties 2 required
IssueCountsWithExecutionInfo
object
The count of Security Issues, by severity code, for a given Harness Pipeline Execution along with this execution info
15 properties 13 required
ScanIssueCountsWithExecutionInfo
object
The count of Security Issues, by severity code, for a given Harness Pipeline Execution along with this execution info
10 properties 9 required
AllIssuesFiltersResultV2
object
Distinct filter values available for the issues produced by the requested target and variant combinations
4 properties 4 required
MinimalIssueCountsPerScanner
object
The count of Security Issues, by severity code, for a given Harness Pipeline Execution
7 properties 6 required
AllIssueSummaryV2
object
All issue summary V2
9 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-sto-data-frontend-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 STO Data Frontend 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.