EN
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Talk to sales
MenuClose
Talk to sales

Preferences

LanguageEnglish
AppearanceSystem
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Monitoring

Which of my customers or suppliers changed status, and because of which publication?

You register your book once, and the platform compares every subject with each new publication of the lists, the registry, the debt, LEIs, tax lists, courts and the press. Only material changes are reported, once, with the publication that caused them.

Illustrative example · invented data

Changes to a monitored customer

  1. New publication of the example list
  2. Monitored customer affected by the change
  3. One notice sent by webhook, with the publication that caused it

Times are invented.

What you get

  • A book encrypted per organization

    Subjects registered one by one, upserted by your reference or imported as JSON Lines, kept encrypted under a key of your organization’s own, managed by dembli, and deleted when monitoring ends.

  • Rescreened on every publication

    Every party a publication changes is compared with every book. Each subject is also swept weekly and whenever a version, a served source or its segment’s profile changes.

  • Only what is material

    Added, removed, classification raised or lowered, designations changed, each reported once. A decided false positive stays quiet while neither the party nor the subject changes.

  • Signed webhooks

    Standard Webhooks signatures, rotation with two signatures, seven retries, resend by the customer, and administrators told when an endpoint stops.

  • A company watched without screening

    A company registered by LEI or taxpayer identifier, never compared with the lists, told what each golden copy week, registry month, debt quarter and tax list publication changes.

  • Group, lawsuits and press

    Members one link from a company compared with every publication; the processes court communications name it in, each morning; CNIA convictions, municipal gazettes and press mentions.

Event names carry their version, such as monitoring.registry_change.v1, monitoring.debt_change.v1, monitoring.lei_change.v1, monitoring.tax_list_change.v1, monitoring.group_change.v1 and monitoring.media_mentions.v1, so your integration knows exactly what it receives.

A lookback compares your book with what the lists said at every instant of a period, and reports what monitoring would have reported.

How it works

  1. The sanctions lists of the UN, the United States, the European Union, the United Kingdom, Canada, Switzerland and Argentina’s RePET are checked every five minutes and read when they move; the rest follow each publisher’s schedule.

  2. Each new publication is stored, and the parties it changes are compared with every book.

  3. A versioned state decides whether the change is material for your organization’s class or your segment profile’s thresholds.

  4. The change reaches the feed, the console and the webhook with the publication that caused it, and opens a review.

How it is delivered

  • API
  • Console
  • Webhook
  • MCP server

Related products

Talk to sales

Which of my customers or suppliers changed status, and because of which publication?

Talk to sales