Skip to main content
POST
Create Watchlist

Endpoint

Authentication

Requires watchlist:create permission.

Request Body

Webhook URLs and notification emails are configured at the tenant level, not per-watchlist. Contact support to configure your notification channels.

Request Example

Additional Request Examples

Watchlist with Initial Subjects

Watchlist with Alerts

Notification webhooks and emails are configured at the tenant level. The alert_config only controls when to send alerts, not where.

Crypto Wallet Monitoring

Usage Examples

Python

JavaScript

Response

Success Response (201 Created)

Response Fields

Error Responses

400 Bad Request

Common validation errors:
  • Missing or empty name field
  • Invalid check_frequency value
  • Invalid lists_to_monitor values
  • Invalid subject data

403 Forbidden

Your token lacks the watchlist:create permission.

Subject Fields

When adding subjects during creation:

Best Practices

You can create a watchlist without subjects and add them later using the Add Subjects endpoint. This is useful when setting up infrastructure before onboarding subjects.
  • Daily: High-risk entities, regulatory requirements, active monitoring
  • Weekly: Standard monitoring, cost optimization
  • On Update: Static lists, manual control, lowest cost
Set up webhooks and email notifications when creating the watchlist to ensure you don’t miss critical alerts during the first screening cycle.
Only monitor lists relevant to your jurisdiction and risk profile:
  • US entities: Include ofac
  • International: Include un and eu
  • Uruguay PEPs: Include senaclaft_uy

Status Codes

Next Steps

After creating a watchlist:
  1. Add subjects to begin monitoring
  2. Get watchlist details to verify configuration
  3. Set up webhook endpoint to receive alerts
  4. Monitor screening activity with the Usage API