List Issue Requesters
GET/api/support/agent/links/jira/:key/requesters
Lists every ticket linked to one issue key, with the tenant and requester behind each — how much customer demand is waiting on a single piece of engineering work.
support:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Path parameters
key(string) — the issue key, e.g.ENG-4521. Letters, digits and underscores, a hyphen, then digits.
Response fields (data)
key(string) — the key that was asked forticket_count(integer) — tickets linked to ittenant_count(integer) — distinct tenants behind those tickets; a tenant that raised three tickets counts once, and a ticket raised internally (no tenant) is listed but does not raise this countimportant_count(integer) — how many of those tickets are flagged important to their tenantrequesters[]—ticket_id,ticket_number,subject,status,status_label,tenant_id,tenant_name,requester_name,requester_user_id,important_to_customer,console_url(a direct link to the ticket). Flagged tickets come first.
An unlinked key returns zero counts and an empty requesters list rather than a 404.
Authentication: Bearer token with the support:read scope, or an authenticated session, from a caller with an active support role. No tenant context — this endpoint is central.
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
Unauthorized
Response Headers
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.