Skip to main content
POST
Add Subjects

Overview

Add one or more subjects to an existing watchlist for ongoing monitoring. Subjects are automatically screened at the next scheduled check interval.
Seat-Based System: Each subject consumes one monitoring seat. Subjects have a TTL (Time-To-Live) and automatically expire after the configured duration (default: 365 days). Expired subjects free up seats automatically.

Add Single Subject

Add one subject at a time.

Endpoint

Authentication

Requires watchlist:update permission.

Path Parameters

string
required
The unique identifier of the watchlist

Request Body

Request Example

Response

Response Fields

Add Multiple Subjects (Batch)

Add multiple subjects in a single request for efficiency.

Endpoint

Authentication

Requires watchlist:update permission.

Request Body

Request Example (Batch)

Response

Batch Response Fields

Subject Fields

Common Identifier Types

Error Responses

400 Bad Request

402 Payment Required - No Seats Available

This error occurs when your tenant has used all available monitoring seats. Purchase additional seats to add more subjects. For batch operations, the error includes the specific counts:

404 Not Found

Status Codes

Best Practices

When adding multiple subjects, always use the batch endpoint (/subjects/batch) instead of making multiple single-subject calls. This:
  • Reduces API calls and stays within rate limits
  • Improves performance
  • Simplifies error handling
While full_name alone is sufficient, providing identifiers improves matching accuracy:
  • More precise matches
  • Reduces false positives
  • Better audit trail
Use specific identifier types to help with matching:
  • document for government IDs
  • wallet for crypto addresses
  • passport for passport numbers
  • tax_id for tax identifiers
For subjects added with check_frequency: "on_update", the watchlist will screen them immediately. For daily or weekly frequencies, subjects are screened at the next scheduled check.You can also trigger monitoring manually to get immediate results.
Subjects automatically expire after a configured period (default: 365 days). The expires_at field in the response shows when each subject will be removed. Plan renewals accordingly to maintain continuous monitoring.
Before adding subjects, verify you have available seats. Use the Usage API to check your current seat consumption and avoid 402 errors.

Next Steps