Create Notification Profile
Product | D&B Direct 2.0 |
Product Code(s) | Not Applicable |
Option(s) | None |
Monitoring Available | No |
Interface | SOAP |
WSDL | download |
Format(s) | XML |
Service | Monitoring |
Operation | CreateNotificationProfile |
{version} | 4.1 |
4.1 Released on | December 12, 2014 |
This function allows a customer to specify a user preference and the frequency for testing monitoring profile conditions.
A Notification Profile establishes the protocol by which change events should be delivered to customers, and references user preferences setup in the User Service. This is the PUSH component of the Data Field Monitoring feature.
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.
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 function does not require entitlement for production and trial usage. Entitlement for monitoring is only required for the Add Monitoring Registration function, and for the data layers that will monitored.
Specification
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mon="http://services.dnb.com/MonitoringServiceV2.0"> <soapenv:Header> <wsse:Security soapenv:mustUnderstand="0" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-7" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:Username>MyUserName</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">MyPassword</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <mon:CreateNotificationProfileRequest ServiceVersionNumber="4.0"> <CreateNotificationProfileRequestDetail> <NotificationProfileSpecification> <NotificationProfileName>MonitoringNotificationProfile-MikeEmail</NotificationProfileName> <NotificationProfileDescription>Monitoring Notification Profile using Mike's Email</NotificationProfileDescription> <DeliveryMode>Email</DeliveryMode> <DeliveryChannelUserPreferenceName>Mike-Email</DeliveryChannelUserPreferenceName> <DeliveryFrequency>Immediate</DeliveryFrequency> <DeliveryFormat>XML</DeliveryFormat> <StopDeliveryIndicator>false</StopDeliveryIndicator> </NotificationProfileSpecification> </CreateNotificationProfileRequestDetail> </mon:CreateNotificationProfileRequest> </soapenv:Body> </soapenv:Envelope>
Name | Characteristics |
---|---|
CreateNotificationProfileRequest | Aggregate |
CreateNotificationProfileRequest@ServiceVersionNumber | Attribute |
CreateNotificationProfileRequest@xsi:schemaLocation | Attribute |
CreateNotificationProfileRequest. TransactionDetail | Aggregate, Optional Records information necessary to process this request. |
CreateNotificationProfileRequest. TransactionDetail. ApplicationTransactionID | string up to 64 chars., Optional A number assigned by the calling application to uniquely identify this request. |
CreateNotificationProfileRequest. 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. |
CreateNotificationProfileRequest. 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: CreateNotificationProfileRequest. TransactionDetail | /Aggregate |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail | Aggregate, Required |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification | Aggregate, Required |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification. NotificationProfileName | string at least 1 chars. up to 64 chars. Pattern: {.*[^\s].*}., Required A name that is provided by the user to the profile. |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification. NotificationProfileDescription | string up to 256 chars., Optional A string that records the description of the profile |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification. DeliveryMode | DeliveryModeEnum, Required Possible values: Email; HTTPCallBack; MQOutput |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification. DeliveryChannelUserPreferenceName | string at least 1 chars. up to 64 chars. Pattern: {.*[^\s].*}., Optional |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification. DeliveryFrequency | DeliveryFrequencyEnum, Required Possible values: Immediate; Hourly; Daily; Weekly |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification. DeliveryFormat | DeliveryFormatEnum, Required Possible values: XML, JSON |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification. StopDeliveryIndicator | boolean, Required |
END: CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. NotificationProfileSpecification | /Aggregate |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. InquiryReferenceText | Aggregate, Optional Records data that allows the customer to specify information to be linked to the request in order to support subsequent order reconciliation. |
CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. InquiryReferenceText. 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. |
END: CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail. InquiryReferenceText | /Aggregate |
END: CreateNotificationProfileRequest. CreateNotificationProfileRequestDetail | /Aggregate |
END: CreateNotificationProfileRequest | /Aggregate |
Endpoint
Use the following endpoint with the downloadable WSDL to request this feature.
SOAP (Monitoring) |
---|
https://direct.dnb.com/Monitoring/V{version} |
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
Specification
The following is a list of the possible data fields returned by this operation in the XML 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.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soap-env:Body xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <mon:CreateNotificationProfileResponse ServiceVersionNumber="4.0" xmlns:mon="http://services.dnb.com/MonitoringServiceV2.0"> <TransactionDetail> <ServiceTransactionID>Id-a867e332520e3ed4044b5d09-1</ServiceTransactionID> <TransactionTimestamp>2013-08-16T11:01:40.163-04:00</TransactionTimestamp> </TransactionDetail> <TransactionResult> <SeverityText>Information</SeverityText> <ResultID>CM000</ResultID> <ResultText>Success</ResultText> </TransactionResult> <CreateNotificationProfileResponseDetail> <NotificationProfileDetail> <NotificationProfileName>MonitoringNotificationProfile-MikeEmail</NotificationProfileName> <NotificationProfileID>1583</NotificationProfileID> </NotificationProfileDetail> </CreateNotificationProfileResponseDetail> </mon:CreateNotificationProfileResponse> </soap-env:Body> </soapenv:Envelope>
NOTE: There may be additional request and/or response elements specified in the WSDL that are not applicable for D&B Direct customers. Data elements that are not listed on this page are currently unused by this operation.
Response Codes & Error Handling
Successful service requests will return a CM000 response code in the TransactionResult ResultID field. Otherwise, one of the D&B Direct standard response codes will be returned.
This operation may return the following response codes: CM002, CM004, CM007, CM023, SC001-SC009.
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.
While this operation is provided on a metered basis, usage is tracked; however, no billing for successful calls is recorded.
Operation-specific supplemental response code explanations:
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). |
CM007 | Delivery Channel User Preference Name is invalid. |
CM023 | Duplicate Profile Name |
Feature Notes
The DeliveryChannelUserPreferenceName parameter value should match the PreferenceSpecification.PreferenceName value that was used to create the User Preference.
NOTE: When the HTTPCallBack delivery mode is specified, the corresponding User Preference must include values for both the Credentials.UserID and Credentials.Password, as these fields will be supplied in the header when the call back is performed.