Manual match API

Request

The manual match task scans the customer tenant and creates potential matches for each entity using the DT match rules and updates the CT match tables. Both suspect and automatic match rules are used to create the potential matches. This operation is similar to the manual subscribe task, except in this case, instead of subscribing or merging the records, potential matches are created.

Note: You must enable the Potential match facet for the data tenants in the customer tenant UI in order to see the potential matches.

POST {DTSSURL}/tasks/manual_match

The details of what needs to be evaluated for the potential matches can be specified in the body of the request. If they're not specified, they'll be taken from the MANUAL_MATCH section of the synchronizationConfig section of the subscription.

This task will be triggered by default for any of the following configuration changes:

The physical configuration of the DT or CT
The (L3) or metadata configuration of the DT or CT
The DTSS subscription between the DT and the CT

This task should be used where manual synchronization or pull is used to create potential matches in the customer tenant from the data tenant.

Tip: The REALTIME mode will perform this operation automatically, so you would not use this task if you're in the REALTIME mode.

The body will contain the data tenant and the customer tenant IDs. If you want to do a manual match between a subset of URIs, you can specify the URIs in the optional entityUris section.

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

Manual match API

Request

Footer