Accelerate the Value of Data

Get Detailed Profile

Learn about the operation to get detailed profiles.

Overview

Use the Get Detailed Profile operation to enrich the account data with most recent and updated information from D&B. The operation takes the entity as the input to the request, and uses the DUNS number to fetch the complete account profile and enrich the account attributes in Reltio. This operation is invoked when you select the Get Company Details button in the UI.

For details about the fields that are enriched with D&B data in the Reltio account profile, see Mapping.

Request

POST {DnBConnectorUri}/getDetailedProfile
Table 1. Parameters
ParameterNameRequiredDetails
HeadersContent-TypeYesMust be Content-Type: application/json.
EnvironmentUrlYesThe environment url of the tenant.

Example: https://dev.reltio.com

TenantIdYesTenant ID
AuthorizationYes Reltio access token in the form Bearer: <<token>>, see Authentication API.
DnB-UserNoD&B account username or Consumer Key in Direct+.
Note: Not required if you provide the D&B token.
DnB-PasswordNoD&B account password or Consumer Secret in Direct+.
Note: Not required if you provide the D&B token.
DnB-TokenNo

D&B token in the form Bearer: <<token>>

Note: Not required if you provide the username and password.
QueryentityURIYesEntity URIs.
plusNotrue or false. The default value is false. If set to true, the Direct+ based Get company details call is started.
Note: You must have a token or an account with the privileges for Direct+ API usage. Otherwise, an authentication error is raised.
productNoThe possible values are cmpelf or cmpelk. The default value is cmpelf.
Note: This parameter is for Direct+ requests only and takes effect only if requests with plus=true. Your account must have access to the required product. If you set an arbitrary value for this parameter, the following DnB error appears: Supplied product or version of the product does not exist.
BodyNo

Example - Request

POST https://dev-dnbconnector.reltio.com/b2bIntegration/dnb/getDetailedProfile?entityURI=entities/1BGfXLUR

Response

{
    "success": "OK",
    "message": "Enrichment successful"
}