Identify potential matches across Data and Customer Tenants
Learn about DTSS match search APIs to identify potential entity matches between the Data Tenant and Customer Tenant, or within the Data Tenant.
The Data Tenant Subscription Service (DTSS) provides APIs that enable you to search for a DT-matched entity based on an input CT entity, and to search for a CT-matched entity using an input DT entity. These operations help ensure that redundant or duplicate records are identified before you initiate data subscriptions or onboarding workflows.
Each API uses match rules defined in the MANUAL_MATCH section of your Synchronization Configuration. These rules determine which attributes are compared and how match candidates are scored.
When should you use DTSS Match search APIs?
Use the DTSS Match search APIs to:
- Check whether a DT entity already exists in a CT before subscribing.
- Search for duplicates within the DT before onboarding.
- Evaluate the match quality using your defined manual match rules.
Who should use these APIs?
The DTSS match search APIs are primarily used by a:
Developer building entity matching workflows
Solution Architect designing data exchange patterns
Reltio Configurator managing tenant onboarding and synchronization logic
Choose the right DTSS Match search API
Reltio provides two DTSS APIs to help you search for potential entity matches. Use the table below to select the appropriate endpoint based on your scenario:
| Scenario | Recommended API | Why |
|---|---|---|
| You want to verify whether an entity from the DT already exists in the CT before subscription. | Search for potential matches in Customer Tenants (CT) | Prevents duplicate profiles from being introduced into the CT during subscription. |
| You want to check for existing duplicates among DT entities before onboarding. | Search for potential matches in Data Tenants (DT) | Improves data quality by identifying redundant DT entities before onboarding. |