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

Access and modify Exemptions to Security Issues

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

Tagged areas include Exemptions. 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 22 operations across 14 paths, and defines 24 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}.

22 operations 14 paths 24 schemas 3 DELETE8 GET4 POST7 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 Exemptions 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 22

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

Exemptions 22

Access and modify Exemptions to Security Issues

GET
/sto/api/v2/exemptions
ExemptionsList exemptions
Exemptions#ListExemptions 6 params → 200400401403404429500
POST
/sto/api/v2/exemptions
ExemptionsCreate exemption
Exemptions#CreateExemption 4 params body → 200400401403429500
DELETE
/sto/api/v2/exemptions/{id}
ExemptionsDelete exemption
Exemptions#DeleteExemption 4 params → 204400401403404429500
GET
/sto/api/v2/exemptions/{id}
ExemptionsFind exemption by id
Exemptions#FindExemptionById 7 params → 200400401403404429500
PUT
/sto/api/v2/exemptions/{id}
ExemptionsUpdate exemption
Exemptions#UpdateExemption 5 params body → 200400401403404429500
PUT
/sto/api/v2/exemptions/{id}/{action}
ExemptionsApprove exemption
Exemptions#ApproveExemption 6 params body → 200400401403404429500
PUT
/sto/api/v2/exemptions/{id}/promote
ExemptionsPromote exemption
Exemptions#PromoteExemption 5 params body → 200400401403404429500
POST
/sto/api/v2/exemptions/bulk
Bulk create exemptions
Exemptions#BulkCreateExemptions 4 params body → 200400401403429500
GET
/sto/api/v2/exemptions/issue/{issueId}
Get exemption for issue
Exemptions#GetExemptionForIssue 5 params → 200400401403429500
GET
/sto/api/v2/exemptions/issue/{issueId}/history
List exemption history for issue
Exemptions#ListIssueExemptionHistory 9 params → 200400401403429500
GET
/sto/api/v2/exemptions/issue/{issueId}/history/export
Export exemption history for issue as CSV
Exemptions#ExportIssueExemptionHistory 7 params → 200400401403429500
GET
/v1/orgs/{org}/projects/{project}/exemptions
List exemptions for project
listExemptionsForProject 8 params → 200400500
POST
/v1/orgs/{org}/projects/{project}/exemptions
Create exemption for project
createExemptionForProject 3 params body → 201400500
POST
/v1/orgs/{org}/projects/{project}/artifacts/{artifact}/exemptions
Create exemption for artifact
createExemptionForArtifact 4 params body → 201400500
GET
/v1/orgs/{org}/projects/{project}/exemptions/{exemption}
Get exemption for project
getExemptionForProject 4 params → 200400500
PUT
/v1/orgs/{org}/projects/{project}/exemptions/{exemption}
Update exemption for project
updateExemptionForProject 4 params body → 200400500
DELETE
/v1/orgs/{org}/projects/{project}/exemptions/{exemption}
Delete exemption for project
deleteExemptionForProject 4 params → 204400500
GET
/v1/orgs/{org}/projects/{project}/artifacts/{artifact}/exemptions/{exemption}
Get exemption for artifact
getExemptionForArtifact 5 params → 200400500
PUT
/v1/orgs/{org}/projects/{project}/artifacts/{artifact}/exemptions/{exemption}
Update exemption for artifact
updateExemptionForArtifact 5 params body → 200400500
DELETE
/v1/orgs/{org}/projects/{project}/artifacts/{artifact}/exemptions/{exemption}
Delete exemption for artifact
deleteExemptionForArtifact 5 params → 204400500
PUT
/v1/orgs/{org}/projects/{project}/exemptions/{exemption}/review
Review exemption for project
reviewExemptionForProject 4 params body → 200400500
PUT
/v1/orgs/{org}/projects/{project}/artifacts/{artifact}/exemptions/{exemption}/review
Review exemption for artifact
reviewExemptionForArtifact 5 params body → 200400500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Exemption (37 properties), ExemptionHistoryEvent (23 properties), ExemptionResponseDTO (22 properties), CreateExemptionRequestBody (14 properties). Each schema is shown below with its type and property counts.

IDResult
object
1 property 1 required
IssueExemptionHistoryResult
object
2 properties 2 required
ExportIssueExemptionHistoryResponseBody
object
5 properties 5 required
ApproveExemptionRequestBody
object
2 properties 8 required
BulkExemptionItem
object
6 properties 1 required
UpdateExemptionRequestBody
object
9 properties 8 required
NotFound
object
2 properties 1 required
PendingChanges
object
1 property
StoPagination
object
5 properties 4 required
BulkExemptionResult
object
3 properties 3 required
ExemptionsListExemptionsResponseBody
object
2 properties 2 required
CreateExemptionRequestBody
object
14 properties 9 required
PromoteExemptionRequestBody
object
4 properties 8 required
BulkCreateExemptionsRequestBody
object
9 properties 4 required
ExemptionHistoryEvent
object
Single exemption history row with per-event scope snapshot
23 properties 6 required
BulkExemptionItemResult
object
4 properties 2 required
Exemption
object
Information about an Exemption
37 properties 9 required
Operator
ExemptionInitiatorDTO
object
3 properties
ExemptionStatusDTO
string
ExemptionReviewRequestDTO
object
2 properties
ExemptionDurationDTO
object
2 properties
ExemptionResponseDTO
object
22 properties
ExemptionRequestDTO
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-exemptions-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 Exemptions 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.