Get Support Summary
GET/api/support/summary
Returns the tenant's support overview for a trailing window: open/waiting/awaiting-release counts, tickets created and resolved in the window, median first-response and resolution time in minutes, the percentage of first-response SLAs met, a breakdown by ticket type, the 5 most recently resolved tickets, the last 5 releases that shipped a fix for one of your tickets, and your CSAT for the window.
support:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Replaces Get Support Tickets Summary (GET /api/support/tickets/summary): this endpoint returns every key that one does plus releases and csat. New integrations should call this one.
Query parameters
days(integer, optional) — size of the trailing window in days. Clamped between 7 and 365. Default 30.
Response fields (data)
window_days(integer) — the window actually used after clampingopen(integer) — tickets not yet resolved or closed (any status other thanresolved/closed), regardless of agewaiting_on_customer(integer) — tickets inwaiting_on_customerawaiting_release(integer) — tickets inawaiting_releasecreated_in_window(integer) — tickets opened inside the windowresolved_in_window(integer) — of those, how many have been resolvedmedian_first_response_minutes(integer, nullable) — median minutes from open to first agent response, over tickets opened in the window that have one; null when nonemedian_resolution_minutes(integer, nullable) — median minutes from open to resolution; null when none resolvedfirst_response_sla_met_pct(integer, nullable) — percentage of first responses that landed before their SLA target; null when no ticket in the window had both a response and a targetby_type(object) — count of tickets opened in the window keyed by type:bug,question,feature_request,billing, oruntypedfor tickets without a typerecently_resolved[](array, up to 5, newest first) —id,number(the#iddisplay form),subject,resolved_atreleases[](array, up to 5, newest first) — releases that shipped a fix for one of your visible tickets:ticket_id,subject(nullable),build(the build identifier — a tag, SHA or release name),label(human-readable release label),url(nullable link to the deploy or release notes),released_atcsat.average(number, nullable) — mean rating (1–5, two decimals) over your visible tickets rated inside the window; null when nonecsat.count(integer) — how many ratings that average covers
All counts, medians, releases and CSAT respect the same visibility rules as List Support Tickets (org-wide tickets plus the ones you raised or were added to).
Authentication: Bearer token with the support:read scope, or an authenticated session. Customer endpoints run in tenant context — send the X-Tenant-Id header or call from a tenant subdomain.
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthorized
Response Headers
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
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.