List Intake Tickets
GET/api/support/intake/tickets
Lists the support tickets this caller can see, with exactly the filters, sorts and paging of the production customer ticket list — the response can be handed straight back to your own screens.
Called by another SKU environment (beta, demo, dev) on behalf of its users: authenticate with that environment's intake token and the origin headers described below — not with a Personal Access Token or a session.
What this caller can see: the mapped production tenant's organisation-wide tickets, plus every ticket raised from the address in X-Support-Requester-Email — whichever environment raised them. A ticket outside that set is reported as not found, never as forbidden, so a ticket id can never be probed from another environment. Resolved and closed tickets are excluded by default — pass filter[include_closed]=1, a filter[status] value, a status condition in filter_groups, or the closed queue to see them. filter[queue]=mine and filter[queue]=watching both key off the requester's address rather than a user id.
Each row carries environment (production, beta, demo or dev), origin_tenant_id and origin_host alongside the usual ticket fields, so a list that mixes environments stays legible.
Filtering: filter[search] matches the ticket number, subject, status and priority (by the words the customer sees — waiting, high; three letters or more), requester name and email, tags and the public message thread at once; search_columns narrows it and search_strict_columns makes those fields match exactly. filter[status], filter[priority] and filter[type] each take one value or a comma-separated list, with all meaning no filter. Every other column is filtered with an operator suffix — filter[<column>.<operator>] — and filter_groups expresses AND/OR and nested combinations. An unrecognised filter name or operator is rejected with 400.
Sorting: sort accepts id, subject, status, type, priority, requester_name, first_response_due_at, resolution_due_at, created_at and updated_at, prefixed with - for descending. The default is -updated_at, and the ticket number descending always breaks ties so paging cannot repeat or skip a row.
Pagination: standard pagination envelope — data plus current_page, last_page, per_page, total, from, to and the page links. per_page defaults to 10 and is capped at 100.
work — how far along the ticket is, in customer wording (null only on a ticket raised before work tracking existed). It never says who works the ticket — the support team is always "SKU.io Support":
picked_up_at(ISO-8601, nullable) — when SKU.io Support first picked the ticket upstage(string) — one of: received, investigating, fixing, waiting_on_you, resolved (a ticket SKU.io Support has started on readsinvestigating— the customer is never told it was picked up, or by whom);stage_label(string) —Received,Picked up,Investigating,Working on a fix,Waiting on you,Resolvedworking_now(boolean) andactive_until(ISO-8601, nullable) — SKU.io Support is actively working the ticket right nowprogress_text(string, nullable) andprogress_at(ISO-8601, nullable) — the latest progress update
Who works the ticket, the internal working phase, the stale flag and approval cards are never part of the customer view.
category — what the ticket is about and why it was raised:
feature_key(string, nullable) — akeyfrom the categories list (a SKU.io feature,platform.otherornone); null while uncategorised.feature_labelis its display namearea/area_label(string, nullable) — the product area of that feature (null fornoneor while uncategorised)cause(string, nullable) — one of: how_to, configuration, defect, third_party, request, billing, data_process, other.cause_labelis its display namesource(string, nullable) — who set it:ai(suggested automatically when the ticket was triaged),customer(someone on the account) oragent(SKU.io Support);source_labelis the same in customer wordingsuspected_defect(boolean) — an automatic check suspected a bug that nobody has confirmed yet. It is never counted as a defect; only SKU.io Support (or an engineering link) makes a ticket a defectlocked(boolean) — true once SKU.io Support set the category; the customer can no longer change itset_at(ISO-8601, nullable) — when it was last set
Authentication: the environment token as Authorization: Bearer, plus the X-Support-* identity headers described on the Intake folder. There is no session and no tenant context. An unknown token, or a token presented with another environment, is refused with 403; incomplete identity headers are 422.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Unprocessable Content
Response Headers
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.