Real-Time Dark Web Monitoring watches monitored users continuously. Each user carries one or more assets — an email address, a phone number, a domain — and monitoring finds exposures of the assets you attach, and nothing else. A partner protecting someone with three email addresses and two phone numbers registers one user and attaches five assets.

​
Authentication

Send the Access Token in the X-AccessToken request header on every authenticated call:

​
Lifecycle

1

Register the user

Create the monitoring record for the person you are protecting. Continuous evaluation begins at registration.
2

Attach assets

Add the email addresses, phone numbers, and other artifacts to search for. Coverage is only as broad as the assets attached.
3

Keep details current

Update the user and their assets as their details change.
4

Suspend or deregister

Pause coverage when a subscription lapses, and deregister when the end user leaves. Deregistration stops evaluation and event delivery.

​
User operations

​
Asset operations

​
Error codes

Returned in header.response_code when a user or asset request fails. See Errors for the full list.

​
Establishing a baseline

Monitoring reports new exposures from the moment an asset is attached. To see what was already exposed, run a Dark Web Scan for the asset when you attach it.