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 Registry V2 API

registry V2 endpoints

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

Tagged areas include Registry V2. 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 15 operations across 12 paths, and defines 26 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}.

15 operations 12 paths 26 schemas 1 DELETE9 GET4 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 Registry V2 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 15

Across 12 paths, the API surfaces 15 operations — 1 DELETE, 9 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Registry V2 15

registry V2 endpoints

GET
/har/api/v2/artifacts
List Versions
ListVersions 13 params → 200400401403404500
POST
/har/api/v2/copy
Copy Artifact
Copy 11 params → 200400401403404500
GET
/har/api/v2/files/{file_name}
Download file using file path
GetFile 4 params → 200302400401403404500
POST
/har/api/v2/files/bulk-download
Create a bulk download request
CreateBulkDownloadRequest 1 param body → 200400401403404500
GET
/har/api/v2/files/bulk-download/{download_id}
Get bulk download request status
GetBulkDownloadRequestStatus 2 params → 200400401403404500
GET
/har/api/v2/files/search
Search Files
SearchFiles 5 params → 200400401403404500
DELETE
/har/api/v2/metadata
Delete Metadata
DeleteMetadata 1 param body → 200400401403404500
GET
/har/api/v2/metadata
Get Metadata
GetMetadata 6 params → 200400401403404500
POST
/har/api/v2/metadata
Update Metadata
UpdateMetadata 1 param body → 200400401403404500
PUT
/har/api/v2/metadata
Save Metadata
SaveMetadata 1 param body → 200400401403404500
GET
/har/api/v2/metadata/keys
Get Metadata Keys
GetMetadataKeys 6 params → 200400401403404500
GET
/har/api/v2/metadata/values
Get Metadata Values
GetMetadataValues 7 params → 200400401403404500
POST
/har/api/v2/oci/tags
Add tags to OCI artifact
AddOciArtifactTags 4 params body → 200400401403404500
GET
/har/api/v2/packages
List Image/Package
ListPackages 13 params → 200400401403404500
GET
/har/api/v2/registries
List registries
ListRegistries 13 params → 200400401403404500

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are VersionMetadata (26 properties), PackageMetadata (15 properties), RegistryMetadata (14 properties), ListVersion (6 properties). Each schema is shown below with its type and property counts.

BulkDownloadFilesRequestInput
object
Input for bulk download files. Only one of packages or versions should be provided.
4 properties 1 required
CreateBulkDownloadRequestResponseOutput
object
1 property 1 required
RegistryError
object
Standard error response with code, message and optional details
3 properties 2 required
MetadataType
string
Indicates if metadata was manually added (MANUAL) or system-generated (AUTO)
ListRegistry
object
A list of Harness Artifact Registries
6 properties 2 required
VersionMetadata
object
Version Metadata
26 properties 7 required
PackageMetadata
object
Package Metadata
15 properties 7 required
MetadataItemOutput
object
Metadata entry
4 properties 4 required
RegistryType
string
refers to type of registry i.e virtual or upstream
FileMetadata
object
File Metadata
4 properties 4 required
BulkDownloadRequestStatusOutput
object
5 properties 5 required
MetadataInput
object
Request payload containing metadata items to add or update for a specific entity. Priority Logic: 1. If path is present, it takes highest priority and determin…
6 properties 2 required
MetadataOutput
object
Response containing all metadata entries for an entity
1 property 1 required
PerformedBy
object
Principal who performed the relevant action
2 properties 2 required
BulkDownloadRequestStatus
string
Status of the bulk download operation
ArtifactEntityMetadata
object
Artifact Entity Metadata
RegistryMetadata
object
Harness Artifact Registry Metadata
14 properties 6 required
RegistryStatus
string
Request processing status indicator
MetadataItemInput
object
Metadata key-value pair for create/update operations
2 properties 2 required
PackageType
string
refers to package
ListPackage
object
A list of Package
6 properties 2 required
ListVersion
object
A list of Versions
6 properties 2 required
Meta
object
Metadata about the list response
2 properties 2 required
DeploymentMetadata
object
2 properties 2 required
AddTags
object
3 properties 3 required
RegistryArtifactType
string
refers to artifact type

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-registry-v2-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 Registry V2 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.