List the accounts a repo issue can be assigned to

GET/api/repos/{owner}/{repo}/assignees

listRepoAssignees

The accounts that can write this repository — the bar `addIssueAssignee` holds a repo issue's assignee to — ordered by handle and capped at 200 (`truncated` says when more exist). The issue's author is assignable on top of this list. Requires `Write` on the repository; a caller without it gets 404, the repo routes' one deny shape.

Requires authentication using a bearer token or a session cookie — see tokens and scopes.

curl

curl -X GET 'https://neosource.dev/api/repos/OWNER/REPO/assignees' \
  -H 'Authorization: Bearer $NEOSOURCE_TOKEN'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO/assignees", {
  method: "GET",
  headers: {
    Authorization: "Bearer $NEOSOURCE_TOKEN",
  },
});

Path parameters

ownerrequired: Repository owner or organization slug.
string
reporequired: Repository name.
string

Responses

200Assignee candidates

application/json

AssigneeCandidateListResponse

object

candidatesrequired

array

Ordered by handle.

items

AssigneeCandidateResponse

object

One account a repo issue can be assigned to: the shape of `TeamMemberResponse`, so the picker renders either source the same way.

account_idrequired: string
display_namerequired: string
handlerequired: string

truncatedrequired

boolean

More assignable accounts exist than the list carries (it is capped).

Standard errors

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

400Bad Request — one of: invalid_input
401Authentication required
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