Retrieves all individual records associated with a unified record across different data sources. This endpoint allows you to find all individual IDs for a person across various systems, such as retail sales, loyalty programs, and mobile identity platforms.
Syntax
- HTTP Method: GET
- Availability: Data 360 v1.0, Salesforce API version 54.0 and later
- Format: REST
- URI:
/api/v1/universalIdLookup/{entityName}/{DataSourceId__c}/{DataSourceObjectId__c}/{SourceRecordId__c}
Path Parameters
| Parameter | Type | Description |
|---|---|---|
| entityName | string | Required. The name of the bridge table entity. |
| DataSourceId__c | string | Required. The data source ID. |
| DataSourceObjectId__c | string | Required. The data source object ID. |
| SourceRecordId__c | string | Required. The primary key of the data source record. |
note: SourceRecordId__c maps to Individual ID of Individual data model object. For more information, see Individual DMO.
Response Structure
The response includes:
data: Array of record objects containing the requested data- Each record contains:
SourceRecordId__c: The source record IDUnifiedRecordId__c: The unified record IDssot__DataSourceObjectId__c: The data source object IDssot__DataSourceId__c: The data source ID
Examples
Request
GET https://{TSE}.360a.salesforce.com/api/v1/universalIdLookup/IndividualIdentityLink__dlm/SFMC1487860/SFMC1487860_EmailProfile/100060522
Response
{
"data": [
{
"SourceRecordId__c": "100060522",
"UnifiedRecordId__c": "c7ac3830-77c0-3d3d-851ccee3e8d9c2c6",
"ssot__DataSourceObjectId__c": "SFMC1487860_EmailProfile",
"ssot__DataSourceId__c": "SFMC1487860"
},
{
"SourceRecordId__c": "138408",
"UnifiedRecordId__c": "c7ac3830-77c0-3d3d-851ccee3e8d9c2c6",
"ssot__DataSourceObjectId__c": "Mobile_AllSubscribers",
"ssot__DataSourceId__c": "MobileSDK"
},
{
"SourceRecordId__c": "0043V00001ENHZ",
"UnifiedRecordId__c": "c7ac3830-77c0-3d3d-851ccee3e8d9c2c6",
"ssot__DataSourceObjectId__c": "Salesforce_0043V00001ENHZ",
"ssot__DataSourceId__c": "Contact"
}
]
}
Notes
- The API follows REST standards for consistency
- All responses are in JSON format
- Error responses include detailed error messages
- The API supports both primary and secondary key searches
- You must explicitly specify fields to retrieve more than 10 fields