POST
Creates a user and onboards them to every entry in the services array in a single call. Each entry’s shape varies by service slug: rmd carries personal and address fields, and dwm carries the assets to monitor.
  • URL: /usermanagement/v1/users
  • Full URL: <base_url>/usermanagement/v1/users
  • Request Method: POST
  • Content-Type: application/json

Authentication

Send the Access Token in the X-AccessToken request header on every authenticated call:
Your Secret Key must never be used client-side or committed to source control. Exchange it for an Access Token server-side (see Authentication) and send only the Access Token from client code.

Request Body

string
required
Unique external identifier for the user.
string
required
Default subscription type (e.g. paid).
number
Default subscription period in days, used when a service entry doesn’t override it.
array
required
One entry per service the user is onboarded to (see the service entry fields below).
On rmd entries, the email and phoneNumber fields must be unique — user creation fails if either value already exists in the system. All remaining parameters are optional and should be supplied only if they are enabled as part of the partner’s agreed service scope and configuration.

Sample Request

Response

object
Response envelope.
object

Sample Response

Success

Status Codes

Error codes

Returned in header.response_code when the request fails. See Errors for the response envelope and the full list of codes.

Next steps

Get a User

Retrieve the profile and subscription details of the user you just created.

Dark Web Monitoring

Look up where a user’s identifiers appear in breach data.

Delete a User

Permanently remove a user when the relationship ends.