Skip to main content
Call agent.identify() before signup, login, checkout or another protected action. Each successful call starts a new identification, including inside the background-check cooldown.
For an anonymous visitor, omit userId:

Options

string
A stable, pseudonymous User HID computed on your server. Omit it for anonymous checks. Empty or whitespace-only strings and the exact values anonymous, fail, -1 and unknown are rejected.Use a URL-safe opaque token or hash. The SDK warns about email-like values and identifiers containing /, ?, #, %, or consisting of . or ... A warning does not transform the supplied value.
number
Milliseconds to wait for initialization. Defaults to the timeout passed to load(), which is 10,000 ms unless changed. Must be greater than 0 and at most 2,147,483,647.

Return value

Promise<IdentifyResult> resolves when the browser agent reports initialization:
string
required
Identification ID for this identification. Pass it to your backend with the protected action and use it to retrieve the stored result.
string | null
required
The User HID supplied to this call. null for an anonymous identification.
Initialization does not mean scoring or storage has finished. Use bounded retries when reading a new result. See Identification flow.

Errors and usage

The call rejects with invalid_options, not_initialized or timeout. A timeout does not establish whether a check was accepted. Retrying can start another identification and consume additional volume. See error handling and usage.