Web IP Assignee Lookup

This operation provides access to IP resource details, and requires an IP (v4) address.

IMPORTANT: Please note this operation is decommissioned effective July 10th, 2020.

Feature Request

IMPORTANT: Please see the new Online Services Security Enhancement Release, effective November 09, 2020.

Overview

When requesting this D&B Data Exchange feature, a valid IPv4 address will be required. An optional parameter is available to screen on the type of company associated with the address.

Global Availability

This data layer is only available for businesses domiciled in the United States.

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 is entitled as "Data Exchange" for D&B Direct 2.0 customers.

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.

Data Exchange Request Setup

D&B Direct specific request parameters are submitted to D&B Data Exchange service requests in the HTTP Header. Partner specific request parameters are submitted in the URL (GET) or body (POST).

GET/POST/PUT/DELETE https://direct.dnb.com/dataexchange/{PartnerIndentifier}/{Partners’s URI}?{Partner’s Query Parameters}
ApplicationTransactionID: <Transaction ID assigned by the customer>
Accept: application/json
Authorization: <Customer’s Authentication Token>
ArchiveProductOptOutIndicator: <true/false>
ExtendArchivePeriodIndicator: <true/false>
Content-Type: application/json

[BODY]
<Partner Request (POST only)>

GET https://direct.dnb.com/dataexchange/profound/domain/abbott.com
Authorization: <MyToken>
ApplicationTransactionID: ID_001
ArchiveProductOptOutIndicator: false
ExtendArchivePeriodIndicator: false
CustomerReferenceText: Order placed by Joe
CustomerBillingEndorsementText: Order placed by Joe for abbot.com

Specification

GET https://direct.dnb.com/dataexchange/profound/ip/203.206.211.85?dtype=any&view=basic
Authorization: <MyToken>
Accept: application/json
ApplicationTransactionID: ID_001
ArchiveProductOptOutIndicator: false
ExtendArchivePeriodIndicator: false
CustomerReferenceText: Order placed by Joe
CustomerBillingEndorsementText: Order placed by Joe

Endpoint

For each D&B Data Exchange partner operations, a partner identifier and URI are appended to a standard Data Exchange REST URL. As a result of this approach, there may be instances where a partner URI contains version information that is different from the D&B Data Exchange version.

Use the following endpoint for requesting this feature.

Testing

The following suggested parameters may be used for test environment (sandbox) requests to retrieve successful responses.

Feature Response

Specification

NOTE: The information returned from this Data Exchange feature will not be presented in the product canonical model used by other D&B Direct services.

The following is a list of the possible data fields returned by this operation.

NOTE: The D-U-N-S Number returned in the response will be a nine-digit zero-padded, numeric value.

HTTP/1.1 200 OK
ApplicationTransactionID: ID_001
CustomerBillingEndorsementText: Order placed by Joe for abbot.com
CustomerReferenceText: Order placed by Joe
Date: Tue, 12 Nov 2013 15:54:00 GMT
DNB-PortfolioAssetID: 36590291
DNB-ResultID: CM000
DNB-ResultText: success
DNB-ServiceTransactionID: Id-4d7cd8c752824f1822fb470b

{"country_code":"AU","region":"Oceania","domain":"iinet.net.au","dtype":"isp","ip":"203.206.211.85","duns":"750190985","name":"iiNet Limited."}

Data Exchange Response Delivery

D&B Direct specific fields are returned in D&B Data Exchange service responses via the HTTP Header. D&B Direct error information will be returned in case of the following scenarios – Failure to connect to Partner; Authentication / entitlement failure for the user -- and the Partner response will not be returned.

ApplicationTransactionID: <ID passed in request>
DNB-ServiceTransactionID: <ID assigned by the Service>
DNB-ResultID: <PCM Result Code>
DNB-ResultText: <PCM Result Text>
DNB-PortfolioAssetID: <Portfolio Asset ID>

[BODY]
<Partner Response (JSON/XML/SOAP)>

HTTP/1.1 200 OK
ApplicationTransactionID: ID_001
CustomerBillingEndorsementText: Order placed by Joe for abbot.com
CustomerReferenceText: Order placed by Joe
Date: Tue, 12 Nov 2013 15:54:00 GMT
DNB-PortfolioAssetID: 36590291
DNB-ResultID: CM000
DNB-ResultText: success
DNB-ServiceTransactionID: Id-4d7cd8c752824f1822fb470b

{"domain":"abbott.com","country_code":"US","datestamp":20130303,"company_name":"Abbott Laboratories","duns":"001307602","url":"http://www.abbott.com/","view":"basic"}

Response Codes & Error Handling

Responses from this Data Exchange feature will return a D&B response code, along with a partner response code, unless the partner service is not accessible at the time of the request.

Successful service requests will return a CM000 response code in the DNB-ResultID header field. Otherwise, one of the D&B Direct standard response codes will be returned.

This operation may return the following response codes: CM004, SC001-SC009.

NOTE: When a CM004 response code is received, the HTTP status code will be the value returned by the Data Exchange partner.

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 code CM000 is considered successful. A built-in feature exists to prevent duplicate billing when multiple successful feature requests with the same D-U-N-S Number are submitted on the same calendar day (which is based on Eastern Standard Time [GMT-5]).

Feature Notes

This D&B Data Exchange feature will pass-thru the partner HTTP status code whenever a CM004 error is delivered in the DNB-ResultID header field. The following are the possible values from this partner.

• 400 - MissingParameter - request is missing a required parameter
• 401 - InvalidCredentials - request has missing or invalid credentials
• 404 - ResourceNotFound - no matching resource found for the request
• 409 - InvalidArgument - request includes an invalid argument
• 412 - PreconditionFailedError - resource found, but did not satisfy request conditions
• 500 - InternalError - request produced an internal system error

• © Dun & Bradstreet, Inc. 2019 – 2024. All rights reserved.