Skip to main content

October 2026

History reference pages

Domain, Search and Card are separate pages. Search lists identifications or users for one domain. Card reads one identification, user, visitor, device or IP.

History methods

The account History API lists a domain, then reads identifications and users or one visitor, device, or IP. Filters such as risk_bands, is_vpn, risk_signals, source, and campaign are query parameters.

History reference

A History response is an entity card. Read risk.score when risk.state is ok, and continue a list with next_page_token.

Risk signal names

The current scored webhook uses private_relay, network_check_incomplete, latency_test and banned_ip. The connection type is private_relay.

Plan request rate

Each registered domain now allows fewer identification requests per second: 3 on Free and Starter, 5 on Growth, and 7 on Scale. See Billing and Rate limits.

Current product and integration reference

  • History responses, scored webhooks and the server SDKs name one check identification_id.
  • Named the glossary field for an identification’s Trusted, Suspicious, or Dangerous label Risk band.
  • Grouped the API reference sidebar by the integration steps: run a check, get the result, account, and contracts.
  • Corrected risk weights, including VPN 30, Proxy 30, Private Relay 30, IP Mismatch 45 and Browser Automation 90.
  • Distinguished source detections from grouped dashboard labels.
  • Documented the separate multi-account group webhook, its enablement, lifecycle and revisions.
  • Updated webhook retry and deduplication guidance and separated History fields from scored payloads.
  • Corrected current identity risk and the Traffic quality.
  • Replaced dashboard illustrations with screenshots of the current analytics dashboard code, using synthetic example data, including the account-event graph.
  • Shortened use-case guides and linked them to complete runnable tutorials.
  • Updated the scored webhook flags and signal catalog for the 20-field schema.
  • Split the glossary into entities, the fields of an identification, risk signals and a separate integration glossary.
  • Session ID and Cookie ID are identifiers on a check, not entities. The identifier model separates the identification, the user and the visitor from the device anchor.
Check the received webhook schema version and your installed SDK version when integrating.

September 2026

The docs added analytics dashboard walkthroughs and account-level concepts, plus browser and server SDK guides. The event terminology uses four High-Risk Events with Medium/High confidence, separate from the three risk bands.

Earlier updates

Setup, billing, History API paths and infrastructure limits were consolidated into their reference pages. Use Billing, Rate limits, Errors and Webhooks for current behavior.