Skip to main content
An identification is one browser check, identified by identification_id. An account is the user represented by the pseudonymous user_hid you provide.

​
Key differences

​
Reading both together

At login or checkout, obtain a fresh Identification ID and read its verified result on your backend. Check its age, domain and association with the authenticated account before acting. A familiar account may have an unusual new identification. For example, VPN (30) and Anti-Detect Browser (60) produce a Risk Score of 90, Dangerous. The previous account history adds context; it does not make the new check Trusted. Conversely, several accounts can share a device while each check has a low score. Multi-accounting detects relationships across activity; it is not a weight added to one identification.

​
Receiving results

  • identification.scored delivers a scored check. Its hre object can carry account sharing, impossible travel and account takeover results when evaluated.
  • hre.multi_account.changed delivers a group change, with its members, revision and lifecycle action. It has no Identification ID or Risk Score and requires separate enablement.
  • History returns identification and identity cards, including current risk categories where available. It does not reconstruct missed group-change events.
See the webhook reference for the two payloads and availability details.

​
Choosing a check

Normal snippet checks are throttled within the browser visit. A skipped call does not create a new identification. See Snippet methods and Identification flow. The current account category is not the maximum score of the last History page. Use that distinction when comparing backend decisions with the analytics dashboard.