Jira

Jira Security Information API

Send security information to Jira Software and enable your teams to turn unplanned vulnerabilities into planned and tracked work. Security is everyone's responsibility, and the security feature in Jira lets you triage and track relevant vulnerabilities as a team. Discuss and prioritise issues, minimise errors and duplication, and plan security work to complete in your sprints. APIs related to integrating Security information with Jira Software are available to Atlassian Connect apps. To use these APIs you must have a security info provider module in your Connect app's descriptor. See https://developer.atlassian.com/cloud/jira/software/modules/security-information/. These APIs are available to Forge apps with the `devops:securityInfoProvider` module in the Forge app's manifest. See https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-software-security-info/.

GitHub OpenAPI
Business capability
Vulnerability Management BC-620.40

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /rest/security/1.0/linkedWorkspaces/bulk Link security workspaces to the Jira site · Submit Security Workspaces to link #
Ask an LLM
“How does my security app link its workspaces to a Jira site?”
“What happens if I submit a security workspace that's already linked?”
Tell an agent
Link security workspaces {workspaceIds} to this Jira site, authenticating with {Authorization}.
Submit workspace IDs {workspaceIds} to connect them with Jira using token {Authorization}.
DELETE /rest/security/1.0/linkedWorkspaces/bulk Unlink security workspaces from Jira · Delete linked Security Workspaces #
Ask an LLM
“How do I disconnect security workspaces from a Jira site in bulk?”
“Can my app remove several linked security workspaces at once?”
Tell an agent destructive · confirm first
Unlink the matching security workspaces from Jira using app token {Authorization}.
Bulk delete linked security workspaces, authenticated as the app with {Authorization}.
GET /rest/security/1.0/linkedWorkspaces List linked security workspaces · Get linked Security Workspaces #
Ask an LLM
“Which security workspaces are currently linked to my Jira site?”
“Does the linked workspace list reflect pending updates?”
Tell an agent
List all security workspaces linked to this Jira site with token {Authorization}.
Show every linked security workspace as the app authenticated by {Authorization}.
GET /rest/security/1.0/linkedWorkspaces/{workspaceId} Get one linked security workspace · Get a linked Security Workspace by ID #
Ask an LLM
“Is a specific security workspace linked to my Jira site?”
“Can I fetch a linked security workspace by its ID?”
Tell an agent
Get linked security workspace {workspaceId} using token {Authorization}.
Check whether workspace {workspaceId} is linked, authenticated with {Authorization}.
POST /rest/security/1.0/bulk Send vulnerability data to Jira · Submit Vulnerability data #
Ask an LLM
“How does my security tool push vulnerabilities into Jira?”
“Will resubmitting a vulnerability with the same ID overwrite the old data?”
Tell an agent
Submit vulnerabilities {vulnerabilities} to Jira using app token {Authorization}.
Upsert vulnerabilities {vulnerabilities} tagged with properties {properties}, authenticated with {Authorization}.
DELETE /rest/security/1.0/bulkByProperties Bulk delete vulnerabilities by property · Delete Vulnerabilities by Property #
Ask an LLM
“How do I delete all vulnerabilities I tagged with a certain property?”
“If I pass several properties, are vulnerabilities deleted only when all of them match?”
Tell an agent destructive · confirm first
Delete every vulnerability matching the given properties, authenticating with {Authorization}.
Bulk remove vulnerabilities by property as the app with token {Authorization}.
GET /rest/security/1.0/vulnerability/{vulnerabilityId} Get a stored vulnerability by ID · Get a Vulnerability by ID #
Ask an LLM
“How do I check what vulnerability data Jira has stored for an ID?”
“Can I confirm a vulnerability was deleted by fetching it?”
Tell an agent
Get vulnerability {vulnerabilityId} using token {Authorization}.
Show the stored data for vulnerability {vulnerabilityId}, authenticated with {Authorization}.
DELETE /rest/security/1.0/vulnerability/{vulnerabilityId} Delete a vulnerability by ID · Delete a Vulnerability by ID #
Ask an LLM
“How do I remove one vulnerability from Jira?”
“Is deleting a single vulnerability done asynchronously?”
Tell an agent destructive · confirm first
Delete vulnerability {vulnerabilityId} using token {Authorization}.
Remove the stored vulnerability {vulnerabilityId}, authenticated as the app with {Authorization}.

Documentation

📖
Documentation
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/
📖
Authentication
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#authentication
📖
Documentation
https://developer.atlassian.com/cloud/jira/software/rest/intro/
📖
Documentation
https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/
📖
APIReference
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-security-information-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/jira:jira-security-information-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

jira-security-information-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  contact:
    url: https://getsupport.atlassian.com
  description: Jira Software Cloud REST API documentation
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  termsOfService: http://atlassian.com/terms/
  title: Jira Software Cloud Security Information API
  version: 1001.0.0
servers:
- url: https://your-domain.atlassian.net
tags:


# --- truncated at 32 KB (86 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-security-information-api-openapi.yml