For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Contact SalesGet Support
HomeGuidesAPI reference
HomeGuidesAPI reference
  • Get started
    • Quickstart—Verify a Business
    • Quickstart—Register an entity for payroll taxes
    • Learn how Middesk works
    • Security
    • Changelog
  • Build with Middesk
    • Get your API keys
    • Understand API changes
    • Status codes and errors reference
    • Implement webhooks
    • Secure webhooks
    • Use GraphQL
    • Connect MCP
  • Verify a business (KYB)
    • Verify TIN
    • Verify name and address
    • Verify Secretary of State status
    • Verify owners and officers
    • Screen for sanctions and watchlists
    • Search for adverse media
    • Search for Politically Exposed Persons
    • Implement KYC
    • Discover connections
    • Evaluate online presence
    • Assess credit risk
    • Accelerate onboarding
    • Monitor business activity
      • How Monitoring works
      • Monitor watchlist hits
      • Monitor bankruptcies
      • Monitor liens
    • Manage business entities
    • Work with agents
LogoLogo
Contact SalesGet Support
On this page
  • Prerequisites
  • Learn the monitoring lifecycle
  • Monitor watchlist hits
Monitor business activity

Monitor watchlist hits

Was this page helpful?
Previous

Monitor bankruptcies

Next
Built with

This guide describes how to monitor a business for new watchlist hits on Middesk’s Identity Platform.

Watchlist Monitoring helps you stay compliant when the business name (including DBAs) or an associated person (both submitted and discovered) matches a watchlist after the business was initially verified. When a new watchlist hit is found, Middesk updates the business record and sends a watchlist_result.created webhook event so you can review and take action.

Prerequisites

Before you begin:

  • Ensure that you can authenticate against the Middesk API, create businesses, and ingest Middesk results with webhooks

Learn the monitoring lifecycle

Here’s the typical lifecycle of monitoring for watchlist hits:

  1. A business gets created with the POST /businesses endpoint.
  1. The business is subscribed to Watchlist Monitoring (using the watchlist_result event type).
  2. Middesk monitors the business for new watchlist results.
  3. Middesk sends a webhook event to registered webhook endpoint(s) when it detects a new watchlist hit (watchlist_result.created).
  4. The client application ingests and evaluates the change in the business record.

For a full list of webhook events, see Webhook events. For details on the watchlist data model, see the Watchlist object.

Monitor watchlist hits

1

Submit a business

Start by submitting a business for verification.

For best matching, submit the most complete business profile you can (business name, address, and any known associated people).
2

Subscribe a business

You can enable monitoring on Middesk businesses using four different strategies.

With an automatic monitoring subscription
With a policy action
With the API
With the Dashboard

Automatically subscribe all businesses when a business verification order completes.

Get a demo
Contact your account manager or contact sales to inquire about access.