Skip to main content
Use the Visitor fingerprints API to inspect visitor identifiers and their recent linked sessions.
Fingerprints endpoints require a secret key. Listing fingerprints requires the fingerprints:list scope, and reading one fingerprint requires the fingerprints:read scope. See Authentication.
You can access retained session observations from your secret key’s environment. Keys in the same organization and environment can access the same records.
  • seen_count counts distinct observed sessions.
  • First/last seen and latest request describe those observations.
  • Visitors without observations in your environment return 404 and do not appear in lists.
You receive null anchors, an empty component vector, and false storage flags because the identity store cannot attribute these fields to an environment. Treat the storage flags as unavailable, not as evidence that browser storage was absent. You can still view organization-wide identity details in the dashboard.

Endpoint summary

GET /v1/fingerprints

Requires a secret key with the fingerprints:list scope. Supported query parameters: Without sort, the list starts with the visitors seen most recently. A limit, sort, or cursor value that isn’t valid returns 422 with request.validation_failed. A cursor works only with the sort value of the request that returned it. See Pagination. Example response:
lifecycle.expires_at is always 9999-12-31T00:00:00.000Z. This value is a sentinel that means the fingerprint doesn’t expire, so don’t treat it as a date to schedule against.

GET /v1/fingerprints/:visitorId

Returns the visitor fingerprint detail plus a recent linked-session summary. Requires a secret key with the fingerprints:read scope. activity.sessions lists up to 100 recent decisions for sessions linked to this visitor, newest first. Example response: