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

This contains APIs specific to CD license usage

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

Tagged areas include Usage. 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 18 operations across 18 paths, and defines 34 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}.

18 operations 18 paths 34 schemas 16 GET1 POST1 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 Usage 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 18

Across 18 paths, the API surfaces 18 operations — 16 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Usage 18

This contains APIs specific to CD license usage

GET
/ng/api/license-usage-cd/v2/{usageType}/csv/download
Download CD Usage CSV report
downloadCDUsageCSVReport 3 params → 400500default
GET
/ng/api/usage/cd/active-services/csv/download
Download CSV Active Services report
downloadActiveServiceCSVReport 2 params → 400500default
GET
/ng/api/usage/CD/serviceInstancesLicense
Gets License Usage By Module, Timestamp, and Account Identifier
getCDLicenseUsageForServiceInstances 2 params → 400500default
GET
/ng/api/usage/CD/servicesLicense
Gets License Usage By Module, Timestamp, and Account Identifier
getCDLicenseUsageForServices 2 params → 400500default
GET
/ng/api/usage/{module}
Gets License Usage By Module, Timestamp, and Account Identifier
getLicenseUsage 4 params → 400500default
GET
/ccm/api/usage/cd/active-services/csv/download
Download CSV Active Services report
CcmdownloadActiveServiceCSVReport 2 params → 400500default
GET
/ccm/api/usage/CD/serviceInstancesLicense
Gets License Usage By Module, Timestamp, and Account Identifier
CcmgetCDLicenseUsageForServiceInstances 2 params → 400500default
GET
/ccm/api/usage/CD/servicesLicense
Gets License Usage By Module, Timestamp, and Account Identifier
CcmgetCDLicenseUsageForServices 2 params → 400500default
GET
/ccm/api/usage/{module}
Gets License Usage By Module, Timestamp, and Account Identifier
CcmgetLicenseUsage 4 params → 400500default
GET
/cv/api/usage/SRM/active-monitored-services/csv/download
Download CSV Active Monitored Services report
downloadActiveMonitoredServiceCSVReport 2 params → default
GET
/cv/api/usage/SRM/active-services-monitored/csv/download
Download CSV Active Services Monitored report
downloadActiveServiceMonitoredCSVReport 2 params → default
GET
/cv/api/usage/CV
Cvget license usage
CvgetLicenseUsage 2 params → default
GET
/cv/api/usage/SRM
Get SRM license usage
getSRMLicenseUsage 2 params → default
POST
/cv/api/usage/SRM/active-monitored-services
Returns a List of active monitored services along with identifier,Active…
listSRMActiveMonitoredServices 5 params body → default
GET
/sto/api/usage
UsageReport usage
Usage#ReportUsage 3 params → 200400401403429500
GET
/sto/api/usage/all-accounts
UsageUsage all accounts
Usage#UsageAllAccounts 2 params → 200400401403429500
PUT
/iacm/api/enforcement/client/usage/{metric}
Show usage
usage#getUsage 2 params → 200400401403404408409423
GET
/iacm/api/usage/check-licence
Show licence
usage#checkLicence 1 param → 200400401403404408409423

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are PageActiveMonitoredService (11 properties), ActiveMonitoredService (9 properties), ShowLicenceResponse (8 properties), ResponseMessage (7 properties). Each schema is shown below with its type and property counts.

ServiceUsageDTO
object
7 properties
ValidationError
object
2 properties
AccountUsage
object
Account Usage
5 properties 3 required
ResponseDTOSRMLicenseUsageDTO
object
4 properties
Error1
object
This is Error entity as defined in Harness
7 properties
ResponseDTOServiceUsageDTO
object
4 properties
ServiceInstanceUsageDTO
object
6 properties
ResponseDTOServiceInstanceUsageDTO
object
4 properties
Sort
object
3 properties
PageActiveMonitoredService
object
11 properties
SRMLicenseUsageDTO
object
4 properties
ResponseDTOLicenseUsage
object
4 properties
UsageResult
object
Usage Result
5 properties 5 required
CcmError
object
This is Error entity as defined in Harness
7 properties
UsageAllAccountsResult
object
All Accounts Usage Result
2 properties 2 required
Pageable
object
6 properties
Failure
object
This is Failure entity as defied in Harness
5 properties
CcmErrorMetadata
object
This implements different error meta data objects
1 property
NotFound
object
2 properties 1 required
ReferenceDTO
object
7 properties
ResponseDTOPageActiveMonitoredService
object
4 properties
UsageDataDTO
object
3 properties
ErrorMetadata2
object
This implements different error meta data objects
1 property
ResponseMessage
object
7 properties
Usage
object
Usage
3 properties 3 required
LicenseUsage
object
This is the view of a License Usage object defined in Harness
4 properties 1 required
ActiveServiceMonitoredFilterParams
object
Active Services Monitored Filter Params
3 properties
ActiveMonitoredService
object
This is details of the Active Service Monitored entity defined in Harness.
9 properties 1 required
AnsibleLicenceData
object
2 properties 2 required
ShowUsageResponse
object
2 properties 2 required
UsageData
object
2 properties 1 required
AnsibleUsageData
object
1 property 1 required
IaCMError
object
6 properties 6 required
ShowLicenceResponse
object
8 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-usage-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 Usage 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.