The Monitoring feature provides the ability to receive notifications when changes occur to content contained in specific data products and D-U-N-S Numbers®.
D&B Direct+ data API provides access to numerous products, each with a set of attributes. Monitoring allows you to receive notifications when any of those attribute values change for the D-U-N-S Number in the registration.
For more information on the products, please see the Data Product APIs.
D&B Direct+ Monitoring Registrations represent a request to monitor a set of D-U-N-S Numbers against one of the D&B Direct+ Data Products. It also includes details on how notifications are to be delivered and other information necessary for monitoring.
Note: Subjects can be identified using the D-U-N-S Number (or) other subject ID type.
The D-U-N-S Numbers can be specified as:
The Subject IDs can be specified as:
The Monitoring Registration also allows for an optional request for a seed (or baseline) of the data to be delivered per the delivery channel configuration in the Registration.
Note: For China, due to recent regulatory changes limited data is available for online & monitoring.
A seed file provides a baseline of data for the Monitoring Registration. When you create a registration, if Seed File = True:
Note: Maximum file (compressed) size for Seed and Notification is 3GB. Multiple files will be delivered when output data size is more than 3GB.
Change notifications provide details about changes that occur to D-U-N-S Numbers within the Monitoring Registration.
Once a registration is created and processed, regular notifications are delivered to the destination and at the frequency specified in the registration.
For STP, S3 and GCS, multiple files may be received depending on the number of notifications. The individual notifications are grouped by D-U-N-S Numbers and in date/time ascending order. A single D-U-N-S Number will never be split between multiple files. Best practice to update a single D-U-N-S Number, is to process the notifications in a file in order.
While it is unlikely, it is possible that the same D-U-N-S Number will have more than one UPDATE notification in a single package.
To create a registration to send notifications to a cloud platform, please refer to (See Create a Registration).
Please note the following is not supported for cloud platform notifications:
On successful creation of the registration, the following tables will automatically be created within the Cloud platform:
Cloud platforms currently supported are:
Below additional details are available in the appendix page: