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 V3 - Files API

V3 files endpoints

Harness Registry V3 - Files 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 V3 - Files. 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 8 operations across 6 paths, and defines 15 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}.

8 operations 6 paths 15 schemas 5 GET2 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 V3 - Files 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 8

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

Registry V3 - Files 8

V3 files endpoints

GET
/har/api/v3/files
Search Files
ListFilesV3 12 params → 200default
GET
/har/api/v3/files/{id}/content
Download file using file id
GetFileV3 3 params → 200302default
GET
/har/api/v3/files/{id}/metadata
Get File Metadata
GetFileMetadataV3 2 params → 200default
POST
/har/api/v3/files/{id}/metadata
Upsert File Metadata
UpsertFileMetadataV3 2 params body → 200default
PUT
/har/api/v3/files/{id}/metadata
Replace File Metadata
SaveFileMetadataV3 2 params body → 200default
GET
/har/api/v3/files/{id}/preview
Get inline preview URL for a file
GetFilePreviewV3 4 params → 200default
POST
/har/api/v3/files/search
Search Registry Files by path regex
SearchRegistryFilesV3 6 params body → 200default
GET
/har/api/v3/internal/registries/{registry_name}/files
List Registry Files
ListRegistryFilesV3 9 params → 200default

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are FileMetadataV3 (12 properties), FilePreviewDataV3 (5 properties), UserInfoV3 (4 properties), MetadataV3 (4 properties). Each schema is shown below with its type and property counts.

ListFilesResponseBodyV3
SearchRegistryFilesRequestInputV3
object
Input for the search registry files operation. The regex is sent in the body so characters like ?, &, +, and % don't need URL-encoding and aren't mangled by pr…
2 properties 2 required
UserInfoV3
object
Structured user information for a principal
4 properties
MetadataItemInputV3
object
Metadata key-value pair for create/update operations
2 properties 2 required
FileMetadataV3
object
File Metadata
12 properties 10 required
MetaV3
object
Metadata about the list response
2 properties 2 required
FilePreviewDataV3
object
Inline preview details for a file.
5 properties 4 required
FilePreviewResponseBodyV3
object
Single-resource read wrapping the file preview details.
1 property 1 required
ErrorV3
object
An error response
1 property 1 required
MetadataTypeV3
string
Indicates if metadata was manually added (MANUAL) or system-generated (AUTO)
MetadataInputV3
object
Request payload containing metadata key-value pairs to add or update.
1 property 1 required
ApiErrorsV3
object
4 properties 1 required
MetadataV3
object
Metadata entry
4 properties 4 required
PageInfoV3
object
Pagination metadata. - page selects which page of results to return (0 = first page). - size controls how many items are returned per page. - hasMore is true i…
3 properties 3 required
CreatedAtMsV3
integernull
Unix timestamp in milliseconds when the resource was created

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-registry-v3-files-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 V3 - Files 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.