The Adaptavist Group LogoDocumentation

HTTP Endpoint Examples

The following example demonstrates how to use an HTTP endpoint to manage issue links for a given Jira issue. The endpoint handles GET, POST, and DELETE requests to read, create, and remove issue links.

Example requests

GET: list linked issues

Retrieve all issue links for a given work item. Use this to inspect relationships between issues without querying Jira's full API directly.

curl -X GET "https://example.atlassian.net/gateway/api/svc/jira/apps/ari:cloud:ecosystem::app/12345678-1234-1234-1234-123456789012_prod/api/issues/ISSUE-42/links" \
  -H "Authorization: Bearer <access_token>" \
  -H "Accept: application/json"

POST: create an issue link

Link two issues together by specifying a target issue and link type. Use this to programmatically define relationships between work items from an external system or automation.

curl -X POST "https://api.atlassian.com/svc/jira/a12bc345-678d-9e1f/zy2x11w1-0v1u-9876-ts54_3aaa01b0-02cc/api/issues/ISSUE-42/links" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{"targetIssue": "ISSUE-99", "linkType": "Relates"}'

Remove an existing link between two issues by providing the link ID. Use this to clean up stale or incorrect relationships without opening Jira manually.

curl -X DELETE "https://example.atlassian.net/gateway/api/svc/jira/apps/ari:cloud:ecosystem::app/12345678-1234-1234-1234-123456789012_prod/api/issues/ISSUE-42/links" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{"linkId": "12345"}'

Search documentation

Start typing to search the docs.