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 Recommendation Jira API

Recommendation CRUD apis for jira.

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

Tagged areas include Recommendation Jira. 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 10 operations across 8 paths, and defines 20 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}.

10 operations 8 paths 20 schemas 1 DELETE4 GET5 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 Recommendation Jira 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 10

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

Recommendation Jira 10

Recommendation CRUD apis for jira.

POST
/ccm/api/recommendation/jira/create
Create jira for recommendation
createRecommendationJira 1 param body → 400500default
GET
/ccm/api/recommendation/jira/field-mapping
Get all Jira field mappings
getJiraFieldMappings 1 param → 400500default
POST
/ccm/api/recommendation/jira/field-mapping
Replace Jira field mappings for a field type
upsertJiraFieldMapping 2 params body → 400500default
DELETE
/ccm/api/recommendation/jira/field-mapping
Delete Jira field mapping
deleteJiraFieldMapping 3 params → 400500default
POST
/ccm/api/recommendation/jira/delete
Delete Jira from recommendations
deleteJiraFromRecommendations 1 param body → 400500default
GET
/ccm/api/recommendation/jira/statuses
Get all jira statuses
getJiraStatuses 1 param → 400500default
POST
/ccm/api/recommendation/jira/common-fields
Get common Jira fields across projects and issue types
getCommonJiraFields 1 param body → 400500default
POST
/ccm/api/recommendation/jira/common-issue-types
Get common Jira issue types across projects
getCommonJiraIssueTypes 1 param body → 400500default
GET
/ccm/api/recommendation/jira/mapped-projects
Get mapped jira projects for given recommendation
getMappedProjects 2 params → 400500default
GET
/ccm/api/recommendation/jira/resolution-code
Get all jira resolution codes
getResolutionCodes 1 param → 400500default

Schemas 20

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

ResponseDTOCCMJiraDetails
object
4 properties
CCMJiraIssueTypesRequestDTO
object
2 properties 2 required
ResponseDTOListCCMJiraFieldDTO
object
4 properties
ValidationError
object
2 properties
ResponseDTOListString
object
4 properties
JiraFieldMappingValue
object
2 properties
CcmError
object
This is Error entity as defined in Harness
7 properties
CCMJiraCreateDTO
object
6 properties 2 required
ResponseDTOBoolean
object
4 properties
Failure
object
This is Failure entity as defied in Harness
5 properties
CcmErrorMetadata
object
This implements different error meta data objects
1 property
CCMJiraDetails
object
2 properties
ResponseDTOListJiraProjectDetails
object
4 properties
CCMJiraFieldDTO
object
3 properties
JiraFieldMappingRequestDTO
object
3 properties 3 required
JiraProjectDetails
object
2 properties
ResponseMessage
object
7 properties
CCMJiraFieldsRequestDTO
object
4 properties 3 required
JiraIssueNG
object
6 properties 4 required
ResponseDTOMapStringMapStringJiraFieldMappingValue
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-recommendation-jira-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 Recommendation Jira 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.