Reltio Connect

Hi All,

Am looking for options to check the Reltio system/Application logs that are not included in the Activity logs,  can be used to analyze the failures happening during data load or internal events triggered either by data changes coming from source or directly from the Hub. This should determining RCA for the failures within MDM. 
All your inputs would be helpful. 

Thanks!

Hello, Vinoth Kumar Chittibabu, 

Based on my knowledge and my own research, I've reached the following solution to your case:

1. Data Loader API – identify which records failed on upload

Every time you upload a CSV or JSON file, Reltio spins up a Data Loader job that records success and failure for each row. Start by listing all completed jobs, then download the error report for any job that failed:

GET https://361-dataloader.reltio.com/dataloader/api/{{tenantID}}/project/jobs?inProgress=false&page=1&size=20  
Authorization: Bearer {token}

This returns an array of jobs with fields like jobId, name, status and the name of the error file. Once you spot a job of interest-say 12345-grab its CSV of failed rows:

GET https://361-dataloader.reltio.com/dataloader/api/{{tenantID}}/project/job/12345/errors?errorFile=errors_12345.csv  
Authorization: Bearer {token}

The CSV includes rowNumber, entityKey and errorMessage, giving you your first clues about what went wrong.
Read more in the "Guide to Accessing Reltio Data Loader API": Data Loader API

2. Unmapped Values API – catch missing or incorrect reference data

Often, load failures stem from lookup values that don't resolve against your reference data. To find every unmapped value in your tenant:

GET https://<RdmService>/unmapped/{{tenantName}}  
Authorization: Bearer {token}

If you need only the failures for a specific lookup type-e.g. Country-append it:

GET https://<RdmService>/unmapped/{{tenantName}}/Country  
Authorization: Bearer {token}

The response shows objects with value, count and firstSeenTimestamp, so you can prioritize fixing the most frequent gaps.
See this blog post: RDM troubleshooting

3. Connector Monitoring API – surface integration errors

For each external connector (Salesforce, Dun & Bradstreet, etc.), Reltio provides a monitoring API that lists sync jobs and their detailed logs:

GET https://{{tenantURL}}/connector-management/v2/jobs?connectorType=SALESFORCE&since=2025-04-22T00:00:00Z  
Authorization: Bearer {token}

Grab the logs for a specific job (e.g. abcde):

GET https://{{tenantURL}}/connector-management/v2/jobs/abcde/logs  
Authorization: Bearer {token}

These responses include success/failure status, batch and server timings, and per-record error messages.
Detailed API reference - Salesforce Connector Monitoring API: Connector Monitoring API 

4. Event Monitoring API – drill into internal pipeline failures

To pinpoint failures in match, merge, transaction or other Data Pipeline steps (in the context of Snowflake environments):

GET https://{{tenantURL}}/pipelines/events?sinceTimestamp=2025-04-01T00:00:00Z&status=ERROR  
Authorization: Bearer {token}

You'll receive entries with eventType, entityId, errorMessage and timestamp, which tells you exactly which internal process stopped and why.
Learn more in the Event Monitoring API docs: Event Monitoring API

By following some of these suggestions above, you'll gather diagnostic data needed to perform a thorough RCA of any failure in your Reltio MDM environment. Good luck!

------------------------------
Temenuzhka Gadzheva
Ulpia Tech
------------------------------