Add Monitoring Registration
| Product | D&B Direct 2.0 |
| Product Code(s) | Not Applicable |
| Options(s) | None |
| Monitoring Available | No |
| Interface | REST |
| Method | POST |
| Format(s) | JSON |
| Service | Monitoring |
| {version} | 4.1 |
| 4.1 Released on | December 12, 2014 |
This function allows a customer to specify one D-U-N-S Number, along with active monitoring and notification profiles, and initiates the monitoring process for that organization.
The Monitoring Registration combines Monitoring and Notification Profiles with a specific D-U-N-S Number and initiates the Data Field Monitoring process. There are two levels of monitoring: change events only, or events with data layer included.
Update History
No modifications have been made to this data layer since the initial release.
What to do First
Feature Request
IMPORTANT: Please see the new Online Services Security Enhancement Release, effective November 09, 2020.
NOTE: As of August 22, 2014, for performance reasons, this function no longer performs a Product Availability check during the course of registering a D-U-N-S Number. As a result, it is possible for a registration to be successful, but later result in an unsuccessful state. An upcoming release will provide a method for viewing these cases.
Data Layer Entitlement
For customers in U.S. and Canadian markets, the API is provisioned for specific collections of products, reports, and/or features (collectively referred to as data layers) for production and trial usage. Entitlement is not required for testing in the sandbox environment.
- This feature does not require entitlement for production and trial usage. While this component does not require entitlement, customers will only be permitted to monitor data layers to which they have been entitled.
For customers in the UK, Ireland, Belgium, Netherlands and Luxembourg markets, the API is provisioned as a specific set of data layers for production, trial, and sandbox usage.
- This particular data layer is NOT included in the D&B Direct Onboard suite.
Specification
The Product Availability Lookup feature should be utilized PRIOR TO CALLING THIS OPERATION to determine if the D&B Direct product that will monitored is available for a given D-U-N-S Number.
When monitoring the People data layer, a principal identification number (Principal ID) will be required by this operation.
Restriction: The sequence of Request Parameters submitted to POST/PUT operations currently MUST follow the order presented in this section. This applies to REST calls only.
Restriction: An XML namespace statement MUST be included as the first statement within the primary Aggregate of the request. Please refer to the Sample Request for an example. This applies to REST calls only.
POST https://direct.dnb.com/V4.1/monitoring/registrations
Content-Type: application/json
Authorization: <MyToken>
{
"mon:AddMonitoringRegistrationRequest": {
"@xmlns$mon": "http://services.dnb.com/MonitoringServiceV2.0",
"TransactionDetail": {
"ApplicationTransactionID": "ID_003",
},
"AddMonitoringRegistrationRequestDetail": {
"InquiryDetail": {
"DUNSNumber": "16144166",
"CountryISOAlpha2Code": "US"
},
"MonitoringRegistrationSpecification": {
"MonitoringProfileID": 272,
"NotificationProfileID": 704,
"TradeUpIndicator": "false",
"AutoRenewalIndicator": "false",
"SubjectCategoryText": "High"
},
"InquiryReferenceDetail": {
"CustomerReferenceText": "16144166_Monitoring_Sept2013",
"CustomerBillingEndorsementText": "16144166_Monitoring"
}
}
}
}
| Name | Characteristics |
|---|---|
| AddMonitoringRegistrationRequest | Aggregate |
| AddMonitoringRegistrationRequest@ServiceVersionNumber | Attribute |
| AddMonitoringRegistrationRequest@xsi:schemaLocation | Attribute |
| AddMonitoringRegistrationRequest { TransactionDetail | Aggregate, Optional Records information necessary to process this request. |
| AddMonitoringRegistrationRequest { TransactionDetail { ApplicationTransactionID | string up to 64 chars., Optional A number assigned by the calling application to uniquely identify this request. |
| AddMonitoringRegistrationRequest { TransactionDetail { TransactionTimestamp | DateTimestamp, Optional The date and time when this request was created. When the request is from an intermediary, such as a workflow manager or service bus, this is the date and time when the message was sent to the D&B function, i.e., the date and time when the xml document was created by the requesting intermediary. |
| AddMonitoringRegistrationRequest { TransactionDetail { SubmittingOfficeID | string up to 64 chars., Optional A number that identifies the system or the software application from where this request originated. / A number used to uniquely identfy the D&B business segment or delivery channel from where this request originated. |
| END: AddMonitoringRegistrationRequest } TransactionDetail | /Aggregate |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail | Aggregate, Required Records the details to add company / companies for monitoring, allowing the customer to receive alerts when there is a data change for the company. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { InquiryDetail | Aggregate, Required |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { InquiryDetail { DUNSNumber | string up to 9 chars. Pattern: {([0-9]*)}., Required Records the duns number that is provided by the customer to register for Monitoring. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { InquiryDetail { PrincipalIdentificationNumberDetail { PrincipalIdentificationNumber | string, Optional A number assigned by an external body or by D&B which either uniquely identifies or helps to identify an individual. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { InquiryDetail { CountryISOAlpha2Code | string at least 2 chars. up to 2 chars., Optional The two-letter country code, defined in the ISO 3166-1 scheme published by International Organization for Standardization (ISO)identifying the country of the inquired subject. |
| END: AddMonitoringRegistrationRequest } AddMonitoringRegistrationRequestDetail } InquiryDetail | /Aggregate |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { MonitoringRegistrationSpecification | Aggregate, Required Records details of an organization to be monitored and the preferences that the customer has set for registering an organization for Monitoring. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { MonitoringRegistrationSpecification { MonitoringProfileID | int, Required A number that uniquely identifies a set of events and their thresholds, used to monitor a DUNS or a set of DUNS. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { MonitoringRegistrationSpecification { NotificationProfileID | int, Required A number that uniquely identifies the delivery preferences that the customer has set for Monitoring Alerts. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { MonitoringRegistrationSpecification { TradeUpIndicator | boolean, Optional When true (set to 1) this denotes that the customer has requested that D&B return the data for the Headquarters when the requested organization is a Branch. When false (set to 0) this denotes that the customer has not requested that D&B return the data for the Headquarters when the requested organization is a Branch; however as this is the assumed condition there is no requirement to create this tag to represent this fact. Note: There are D&B WorldWide Network operations where the Headquarters information will be returned automatically, regardless of the customer request. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { MonitoringRegistrationSpecification { AutoRenewalIndicator | boolean, Optional When true (set to 1), it means that this registration is set for Auto Renewal. When false (set to 0), it means that this registration is not set for Autorenewal. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { MonitoringRegistrationSpecification { SubjectCategoryText | string up to 32 chars., Optional An alphanumeric value identifying the category in which the Customer has classified the subject. Possible values: High; Medium; Low |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { MonitoringRegistrationSpecification { RegistrationReasonCode | integer up to 7 digits., Optional Code identifying the reason for the Customer showing interest to monitor this subject. This reason needs to be captured to comply with German Data Protection Laws. |
| END: AddMonitoringRegistrationRequest } AddMonitoringRegistrationRequestDetail } MonitoringRegistrationSpecification | /Aggregate |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { InquiryReferenceDetail | Aggregate, Optional Records data that allows the customer to specify information to be linked to the request in order to support subsequent order reconciliation. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { InquiryReferenceDetail { CustomerReferenceText | string up to 240 chars., Optional(Up to 5x) A freeform reference string provided by the customer to be linked to the product in order to support subsequent order reconciliation. |
| AddMonitoringRegistrationRequest { AddMonitoringRegistrationRequestDetail { InquiryReferenceDetail { CustomerBillingEndorsementText | string at least 1 chars. up to 240 chars., Optional Text that is filled in by customer and commonly contains requesting individual or department name, or customer's own account/reference number and/or name for the case on which the product was provided.This text is a reference used during the billing process. |
| END: AddMonitoringRegistrationRequest } AddMonitoringRegistrationRequestDetail } InquiryReferenceDetail | /Aggregate |
| END: AddMonitoringRegistrationRequest } AddMonitoringRegistrationRequestDetail | /Aggregate |
| END: AddMonitoringRegistrationRequest | /Aggregate |
| AddMonitoringRegistrationResponse { AddMonitoringRegistrationResponseDetail { InquiryDetail { PrincipalIdentificationNumberDetail { PrincipalIdentificationNumber | string, Optional A number assigned by an external body or by D&B which either uniquely identifies or helps to identify an individual. |
| AddMonitoringRegistrationResponse { AddMonitoringRegistrationResponseDetail { MonitoringRegistrationDetail { PrincipalIdentificationNumberDetail { PrincipalIdentificationNumber | string, Optional A number assigned by an external body or by D&B which either uniquely identifies or helps to identify an individual. |
Endpoint
Use the following endpoint for requesting this feature. The {version} is dependent on the underlying service delivering the response.
| Endpoint (Monitoring) |
|---|
| POST https://direct.dnb.com/V{version}/monitoring/registrations |
Testing
This operation will return a static set of results in the D&B Direct test environment (sandbox), regardless of the request parameters.
Feature Response
NOTE: The D&B Direct REST implementation uses the BadgerFish approach for JSON with some minor variations.
Specification
The following is a list of the possible data fields returned by this operation in the JSON response. Samples are provided for testing successful and failed retrieval, and to demonstrate the basic layout of a response. The data returned in samples may not represent actual values that this feature will deliver.
NOTE: The D-U-N-S Number returned in the response will be a nine-digit zero-padded, numeric value.
{"AddMonitoringRegistrationResponse": {
"@ServiceVersionNumber": "4.0",
"TransactionDetail": {
"ApplicationTransactionID": "ID_003",
"ServiceTransactionID": "Id-fd8a0c3e5244711b099bffff-2",
"TransactionTimestamp": "2013-09-26T13:38:38-04:00"
},
"TransactionResult": {
"SeverityText": "Information",
"ResultID": "CM026",
"ResultText": "Request accepted.Processing pending."
},
"AddMonitoringRegistrationResponseDetail": {
"InquiryDetail": {
"DUNSNumber": "016144166",
"CountryISOAlpha2Code": "US"
},
"MonitoringRegistrationDetail": {
"DUNSNumber": "016144166",
"MonitoringProfileID": 272,
"NotificationProfileID": 704,
"StartDate": {"$": "2013-09-26"},
"EndDate": {"$": "2014-06-05"}
},
"InquiryReferenceDetail": {
"CustomerReferenceText": ["16144166_Monitoring_Sept2013"],
"CustomerBillingEndorsementText": "16144166_Monitoring"
}
}
}}
Response Codes
Successful service requests will return a CM026 response code in the TransactionResult ResultID field, however, the registration will be set to a pending status until several asynchronous steps are completed. Otherwise, one of the D&B Direct standard response codes will be returned.
This operation may return the following response codes: CM001, CM002, CM004, CM009, CM011, CM012, CM023, MN001, MN002, PD003, PD005, PD016, PD017, SC001-SC009.
Use the List Monitoring Registation operation to determine when the additional asynchronous steps are complete, and for the success/failure of the registration (value in MonitoringRegistrationStatusText).
D&B Direct 2.0 API requests are provided on a metered basis; and may require entitlement prior to use in the production environment. In addition, a concurrency limit (QPS) is monitored to ensure that it is not exceeded. An error code will be returned in the event that a transaction is throttled.
Qualified usage (e.g., a successful response) is tracked and billed according to the terms & conditions of the customer's contract. The response codes CM000, CM010, PD002 and PD015 are considered successful. A built-in feature exists to prevent duplicate billing when multiple successful requests with the same criteria are submitted on the same calendar day (which is based on Eastern Standard Time [GMT-5]).
Operation-specific supplemental response code explanations:
| CM001 | Invalid Monitoring Profile ID; or Invalid Notification Profile ID. |
| CM002 | Any schema validation failure (e.g. elements that are mandatory in the schema are not present in the request, Sequence of the element is not matching in the schema, Data type mismatch or Invalid notification Level). |
| CM009 | Missing reason code |
| CM012 | Invalid subject- Duns number |
| CM023 | Duplicate Registration |
| PD003 | DUNS stop distribution |
| PD005 | Requested Product not available |
| PD016 | DUNS transferred |
| PD017 | DUNS out of business |
What to do Next
- List Registrations
- Update Registrations
- Process Change Notices
- List Recent Change Notices
- Get Latest Product Copies
- Bulk Monitoring Registration (up to 100 companies per batch)
- © Dun & Bradstreet, Inc. 2019 – 2024. All rights reserved.