List issues linked from a PR

GET/api/repos/{owner}/{repo}/pulls/{number}/issues

listPullRequestIssues

Returns links the engine extracted from the PR body (`fixes`/`closes`/`resolves` → fixes link; `refs`/`references`/`part of` → references link).

Authentication is not described for this operation in the spec — that does not mean it is public. Check tokens and scopes.

curl

curl -X GET 'https://neosource.dev/api/repos/OWNER/REPO/pulls/NUMBER/issues'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO/pulls/NUMBER/issues", {
  method: "GET",
});

Path parameters

application/json

IssuePrLinkListResponse

object

linksrequired

array

items

IssuePrLinkResponse

object

created_atrequired: integerint64
created_byrequired: string
issue_idrequired: string
link_kindrequired: IssuePrLinkKind
pr_idrequired: string
pr_number: integer | nullint32
PR coordinates resolved at read time (route-layer enrichment on the issue-side listing) so the SPA can render `owner/repo#N` links. `None` on the PR-side listing or if the PR row went away.
pr_status: one of
null
PullRequestStatus
pr_title: string | null
repo_name: string | null
repo_owner: string | null

Bodies documented once for the whole API — see standard errors.

400Bad Request — one of: invalid_input
403Forbidden — one of: forbidden
404Not Found — one of: not_found
423Locked — one of: busy
429Rate limited — retry after the `Retry-After` header
500Internal server error
503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
504Gateway timeout — the request exceeded the server's handling budget

Referenced above. Listed here rather than expanded inline, so the same definition is not repeated at every level.

string

How a PR relates to an issue. `Fixes` links auto-transition the issue's status; `References` links are advisory backlinks only.

"fixes""references"

string

Lifecycle status of a pull request.

"open""merged""closed"