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 External Data Provider API

This contains APIs related to External Data Provider Support for CACM

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

Tagged areas include External Data Provider. 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 9 operations across 8 paths, and defines 19 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}.

9 operations 8 paths 19 schemas 2 DELETE1 GET5 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 External Data Provider 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 9

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

External Data Provider 9

This contains APIs related to External Data Provider Support for CACM

POST
/ccm/api/externaldata/filesinfo
Add a new external data file metadata
AddNewExternalDataFileMetadata 1 param body → 400500default
POST
/ccm/api/externaldata/provider
Create External Data Provider
createExternalDataProvider 1 param body → 400500default
POST
/ccm/api/externaldata/dataingestion
Trigger data ingestion
triggerDataIngestion 1 param body → 400500default
DELETE
/ccm/api/externaldata/provider/{providerId}
Delete a provider
CcmdeleteProvider 2 params → 400500default
PUT
/ccm/api/externaldata/filesinfo/{fileId}
Update file metadata
updateFileMetaData 2 params body → 400500default
DELETE
/ccm/api/externaldata/filesinfo/{fileId}
Delete data file and related metadata
deleteDatafileAndMetadata 2 params → 400500default
GET
/ccm/api/externaldata/signedurl
Get a signed url
getSignedUrl 4 params → 400500default
POST
/ccm/api/externaldata/provider/list
get all external data providers
getProviders 1 param → 400500default
POST
/ccm/api/externaldata/provider/filesinfo
get all files info for list of providers
listProvidersFileInfo 1 param body → 400500default

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are ExternalDataFiles (19 properties), ExternalDataProvider (16 properties), CcmError (7 properties), ResponseMessage (7 properties). Each schema is shown below with its type and property counts.

ExternalDataProviderList
object
1 property
ExternalDataIngestionRequest
object
This has the query to list Enforcement Count
3 properties
ResponseDTOListExternalDataProvider
object
4 properties
ResponseDTOExternalDataProvider
object
4 properties
ValidationError
object
2 properties
ResponseDTOExternalDataFiles
object
4 properties
ResponseDTOMapStringListExternalDataFiles
object
4 properties
CcmError
object
This is Error entity as defined in Harness
7 properties
CreateExternalDataFilesDTO
object
1 property
ExternalDataProvider
object
This object will contain the information on the external data providers for an account
16 properties
ResponseDTOBoolean
object
4 properties
CreateExternalDataProviderDTO
object
1 property
Failure
object
This is Failure entity as defied in Harness
5 properties
CcmErrorMetadata
object
This implements different error meta data objects
1 property
InvoicePeriodStatus
object
data exists
3 properties
ResponseMessage
object
7 properties
ResponseDTO
object
4 properties
ExternalDataFiles
object
This object will contain the information on the external data file uploads for an account
19 properties
EmbeddedUser
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-external-data-provider-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 External Data Provider 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.