Match explanation API

Learn about Match explanation API.

Request

Using Postman or some other rest API tool, you can issue the Match explanation post request to your DTSS tenant.

POST {DTSSURL}/entities/_verifyMatches

The header must include the content type, Customer Tenant ID, and Data Tenant ID. The body should list the URIs of the DT and the CT records to be compared using the format shown below.

Request Example

Example: {“dtEntity”:“entities/0000177”, “ctEntity”:”entities/0000BLK”}

The response will contain an attribute-by-attribute comparison of the two records and whether or not they matched.

In this example, the match rule looks for potential matches using NPI IDs. The response in the case of the NPI IDs are an exact match. If there were multiple attributes to find on the match rules, each of them would be listed with either true or false next to it.

The matched property indicates the overall result of the match rule evaluation - either true if there is a match, or false, if not.

Tip: This request is particularly useful when two records you expect to match are not being matched and you want to see why. You'll find a particular attribute listed which is false. This will enable you to investigate why those two attributes did not match.

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

© 2024 The RELTIO® mark is a registered trademark of Reltio, Inc. in the United States and other countries; DataDriven and Reltio Data Cloud are trademarks of Reltio, Inc. Other names or marks are trademarks of their respective owners.

Terms, Privacy Policy, and

Unify and manage your data

Match explanation API

Request

Footer