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 Catalog Custom Properties API

Catalog Custom Properties

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

Tagged areas include CatalogCustomProperties. 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 3 paths, and defines 16 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 3 paths 16 schemas 3 DELETE2 GET3 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 Catalog Custom Properties 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 3 paths, the API surfaces 8 operations — 3 DELETE, 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

CatalogCustomProperties 8

Catalog Custom Properties

POST
/v1/catalog/custom-properties
Ingest catalog custom properties
ingest-catalog-custom-properties 2 params body → 200
DELETE
/v1/catalog/custom-properties
Delete catalog custom properties
delete-catalog-custom-properties 2 params body → 200
GET
/v1/catalog/custom-properties/entity
Get catalog custom properties for given entity
get-catalog-custom-properties-by-entity 2 params → 200
POST
/v1/catalog/custom-properties/entity
Ingest catalog custom properties for given entity
ingest-catalog-custom-properties-by-entity 2 params body → 200
DELETE
/v1/catalog/custom-properties/entity
Delete catalog custom properties for given entity
delete-catalog-custom-properties-by-entity 2 params body → 200
GET
/v1/catalog/custom-properties/property
Get entities for given custom property
get-entities-by-catalog-custom-property 2 params → 200
POST
/v1/catalog/custom-properties/property
Ingest entities for given custom property
ingest-entities-by-catalog-custom-property 2 params body → 200
DELETE
/v1/catalog/custom-properties/property
Delete entities for given custom property
delete-entities-by-catalog-custom-property 2 params body → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are ScorecardFilter (5 properties), CustomPropertiesBase (4 properties), PropertyValue (3 properties), CustomPropertyFilterDeleteRequest (3 properties). Each schema is shown below with its type and property counts.

PropertyValue
object
Value overrides for custom property
3 properties 2 required
CustomPropertyByEntityDeleteRequest
object
3 properties 1 required
EntityValue
object
Value overrides for custom property
2 properties 1 required
CustomPropertyByFieldDeleteResponse
object
2 properties 2 required
CustomPropertyByFieldRequest
ScorecardFilter
object
5 properties 1 required
CustomPropertyByEntityGetResponse
object
1 property
CustomPropertyByFieldResponse
object
3 properties 3 required
CustomPropertyEntitiesCount
object
2 properties 1 required
CustomPropertiesBase
object
Custom properties base
4 properties
CustomPropertyFilterDeleteRequest
object
Custom Property filter delete request
3 properties 2 required
CustomPropertyFilterRequest
Custom Property filter request for ingestion
CustomPropertyResponse
object
2 properties 2 required
CustomPropertyByFieldGetResponse
object
2 properties
CustomPropertyByEntityRequest
CustomPropertyByFieldDeleteRequest
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-catalogcustomproperties-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 Catalog Custom Properties 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.