ongoingMonitoring controls whether a client is monitored against local and public watchlists. This release changes how clients with ongoingMonitoring set to false are handled: they are no longer screened against any watchlist, and they no longer count toward your public watchlist quota.

​
Watchlist Screening

A client is screened against local watchlists and public watchlists (sanctions, PEPs and news media) only while ongoingMonitoring is true. Screening entities are not affected and are still screened once against local and public watchlists. The table below shows what changes for a client with ongoingMonitoring set to false. These clients no longer get new matches, so no EntityMatchesUpdate webhook is sent for them. Matches found before this release stay on the client, but they are no longer updated. To screen a client, set ongoingMonitoring to true with PATCH entities/client/{entityId}. The client is screened against local and public watchlists right away and monitored from then on.

​
Public Watchlist Quota

When you create clients, only those with ongoingMonitoring set to true count toward your public watchlist quota. This applies to POST entities/client and POST entities/client/bulk. A client starts counting toward the quota once ongoingMonitoring is set to true. When nothing in a request counts toward the quota, the quota in the response has the code NOT_COUNTED and remaining set to 0.