LEleakradar
Notifications

Create notification

Changed on

Create a new notification bound to an existing notification method.

Supported types

  • email requires value (email). second_type is not allowed.
  • domain requires value (domain). second_type optional: one of domain leak types, default ALL.
  • advanced requires filters (no value). Bulk is not allowed.
  • raw and dark_web require filters (no value). Bulk is not allowed.

Datasets

  • dataset picks the corpus of email, domain and advanced alerts: stealer_logs (default) or combolist.
  • raw alerts always monitor raw_files and dark_web alerts always monitor dark_web: the server sets it from the type and rejects any other value.

Bulk creation

  • For email and domain, set bulk=true and provide newline-separated values in value to create several notifications at once.

Limit

  • Max notifications = plan limit + extra monitoring assets purchased.
post/notifications

Request

Request body

method_idinteger nullable

Notification method ID to use.

dataset'stealer_logs' | 'combolist' | 'raw_files' | 'dark_web'

Dataset to monitor. For email, domain and advanced: stealer_logs (default) or combolist. raw alerts are bound to raw_files and dark_web alerts to dark_web: the server sets it from the type and rejects any other value (stealer_logs is still accepted there as the historical default).

type'email' | 'domain' | 'advanced' | 'raw' | 'dark_web' required
valuestring nullable

Value to monitor (required for EMAIL/DOMAIN types).

filtersobject nullable

Filters when type=ADVANCED or RAW. Parsed according to type.

auto_unlockboolean nullable

If true, automatically unlock new matching leaks (consumes points).

max_pointsinteger nullable

Daily points cap for auto-unlock (if enabled).

second_type'ALL' | 'EMPLOYEES' | 'THIRD_PARTIES' | 'CUSTOMERS'
bulkboolean nullable

Create multiple notifications at once (e.g., newline-separated values).

Example request

{
  "method_id": 1,
  "type": "domain",
  "value": "example.com"
}

Response

Notification created successfully.

OR

Changes

  • 180678ba6e6eRevision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

  • 4939be6a7cccRevision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property / to the response with the status