Skip to main content

Get Intake Meta

GET 
/api/support/intake/meta

How the production desk sees this call: which environment it came from, the origin tenant it named, the production tenant that maps onto, and whether the person has a SKU.io account. Call it to decide what your own support screens may offer before you show them.

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.

Response fields (data)

  • environment (string) — the environment the call was authenticated as: beta, demo or dev
  • origin_tenant_id (string) — the tenant id you sent in X-Support-Origin-Tenant
  • tenant_id (string, nullable) — the production tenant it maps onto; null when there is no mapping
  • mapped (boolean) — false when no production tenant matches. The tickets are still raised and worked; they simply belong to no customer account, are identified by origin_tenant_id, and the desk sends the customer no notices for them
  • requester_user_id (integer, nullable) — the id of the SKU.io account holding X-Support-Requester-Email, or null when no account holds it. A ticket is still opened either way: the address carries the identity

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