Get Organization Match
The Get Org Match API is called through the Get Match button on the User Interface.
The API takes an entity as input and then uses the account data like name and address from the entity to search for the matching organizations in D&B. The result of the API is the set of matched records with D&B DUNS number.
The D&B DUNS number is updated in the account profile. If more than one DUNS numbers are found, multiple account profiles with matching criteria are returned and updated in the associated data tenant as potential matches. The data steward can then select one of the potential matches and merge the record. If no match is found, the API returns an error with an appropriate message.
The following Account profile attributes are updated as a result of the merge process.
| D&B Match Detail Label | Descriptions |
|---|---|
| Name | Organization name used for D&B match. |
| entityURI | A unique identifier provided by Reltio for every account. |
| Address | All addresses returned by the get match request are displayed here. |
| Auto Match Flag | Part of match rule for auto merge potential matches from DT to CT through the DTSS service |
| Suspected Match Flag | Part of suspect match rule for potential matches from DT to CT through the DTSS service |
| Vendor Verification Status | Options are Match or Match Error If the match process executes successfully and matching records are found in D&B, the flag is changed to a value of Match. If however, an error occurs during the match process, this value is changed to Match Error. |
| DUNS Number | The DUNS number is the unique identifier assigned by D&B to this profile. |
| Organization Detail | Contains details about the organization status. If the organization is active the default attributes Member Role, Standalone, Operation status and Boneyard Organization are displayed. |
| Match Quality | The match quality is the confidence code. This code represents the confidence level of the data from D&B. |
| Vendor Verification Date | The last date when a D&B Match or Enrichment request was made by Account 360 application. This date value in tandem with the Vendor Verification Status can be used to determine when a D&B operation was performed on a profile in Reltio. |
Request
POST {{DnBConnectorUri}}/getOrgMatch| Parameter | Name | Required | Details |
|---|---|---|---|
| Headers | Content-Type |
Yes | Must be Content-Type: application/json |
EnvironmentUrl |
Yes | The environment url of the tenant. Example: https://dev.reltio.com |
|
TenantId |
Yes | Tenant ID | |
|
|
No | Reltio username Note: Not required if you provide the Reltio token.
|
|
Reltio-Password |
No | Reltio password Note: Not required if you provide the Reltio token.
|
|
Authorization |
No |
Reltio token in the form Bearer: <<token>> Note: Not required if you provide the username and password.
|
|
DnB-User |
No | D&B account username or Consumer Key in Direct+. Note: Not required if you provide the D&B token.
|
|
DnB-Password |
No | D&B account password or Consumer Secret in Direct+. Note: Not required if you provide the D&B token.
|
|
DnB-Token |
No | D&B token in the form Bearer: <<token>> Note: Not required if you provide the username and password.
|
|
| Query | entityURI |
Yes | Entity URI's in the form entities/XXXX |
plus |
No | true or false. The default value is false. If set to
true, the Direct+ based Get Org Match 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. |
|
| Body | No |
Example - Request
POST https://dev-dnbconnector.reltio.com/b2bIntegration/dnb/getOrgMatch?entityURI=entities/1BGfXLURResponse
{
"success": "OK",
"message": "1 Match(es)",
"entities": [
"entities/1GsuMoU2"
]
}