Obtain a Data Cloud-scoped OAuth access token from the Salesforce org's token endpoint using a Connected App with the appropriate Data Cloud permissions.
Issue a GET request to the Profile API endpoint: GET https://<tenant-url>/api/v1/profiles/individuals/<unifiedIndividualId> using the unified individual's ID (ssot__Id__c) as the path parameter.
Parse the response JSON, which includes the unified individual's resolved attributes (name, email, phone) and the list of source profile IDs that were merged into this unified record.
To look up by an external identifier rather than the internal unified ID, POST to the lookup endpoint: POST https://<tenant-url>/api/v1/profiles/individuals/lookup with a JSON body containing the identifier type and value.
Retrieve related engagement events or linked DMO records by querying the Data Cloud Query API with the unified individual's ssot__Id__c as a filter parameter.
Handle 404 responses gracefully — they indicate the unified ID does not exist or has been superseded by a re-resolution run that merged it with another profile.
Known gotchas
The unified individual ID changes if identity resolution re-runs and merges previously separate profiles — do not store this ID as a long-lived external reference; use your source system's identifier and look up the unified ID at runtime.
The Profile API returns the resolved view as of the last completed identity resolution run; very recently ingested records may not yet be reflected.
Profile API access requires the Data Cloud Admin or Data Cloud Data Aware Specialist permission set in addition to the Connected App OAuth scope.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp