One contact's authentication history
Requires customers:read. What happened to this account: every sign-in, how it happened and where from, newest first (100 most recent).
It is the answer to the support conversation that starts with “was that me?” — and it matters more than usual because there is deliberately no way to lift two-factor off a contact who lost their phone and their recovery codes, so seeing the history is the least that conversation needs.
ip and user_agent are attributes of the request a session was minted on: what the proxy left, and a string the caller chose. They are for a person to recognise their own device, never for an authorization decision.
Anonymous visitors never appear. The widget mints one on every page load, none of them is an account, and a history full of them is a history nobody reads.
Autorizações
A staff session token, uk_st_…. Minted by sign-up, sign-in or the two-factor exchange.
Cabeçalhos
The organization the caller is acting on — the org_… code that appears in the panel URL. It identifies; the membership JOIN is what authorizes, so a forged code reads nothing. Absent, the session's default organization answers.
Parâmetros de caminho
Parâmetros de consulta
Which environment to read. A view parameter, valid only on the staff surface.
live, test Resposta
The history.