Skip to main content

Get Intake Insights Evidence

GET 
/api/support/intake/insights-evidence

Returns the per-ticket facts a Support Insights report on this environment is built from: every ticket the origin tenant raised from this environment (matched on X-Support-Environment + X-Support-Origin-Tenant) created between from and to. Metadata and subjects only — never a message body or an internal note, and never the staff-only fields.

Environment intake token

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.

Account-level data, so the caller must administer the origin tenant: send X-Support-Tenant-Admin: 1, otherwise the request is refused with 403.

Query parameters

  • from / to (UTC instant, required) — e.g. 2025-10-01T07:00:00Z; to on or after from, and no more than 37 months after it

Response fields (data)

  • tickets[] — one row per ticket, sorted by id: id, created_utc, subject, status, type, priority, source, private (requester-only ticket), requester_key (stable pseudonymous key: u:<user id> or e:<email>), requester_name, requester_state (active, deactivated or deleted), requester_staff (raised by SKU.io staff), first_response_h / resolution_h (wall-clock hours, null while pending), first_response_bh / resolution_bh (business hours on the ticket's calendar), calendar (a key into calendars), sla_first_response_met (true, false, or null when not yet due or no target), reopened_count, csat_score, feature_key, cause, category_source (ai, customer, agent, or null while uncategorised), suspected_defect, defect (confirmed: an engineering link, or SKU.io Support set the cause to defect) and attachment_only (the opening message was only attachments)
  • first_ticket_utc (string, nullable) — when this tenant's first ticket from this environment was raised, across all time
  • data_as_of_utc (string, nullable) — the newest change to any ticket in the range
  • calendars (object) — the business-hours calendars used, keyed like calendar: label, timezone, tickets

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​

OK

Response Headers
    Content-Type