A profile is how First AML represents an individual or an entity across all cases. It is identified by a profileId.
Profile IDs
The Public API has previously referred to an individual or entity by an individualId or an entityId. Those IDs come from an older model, which profiles replace. Use a profileId in new integrations.
You can search for profiles, query information about a specific profile, and manage profiles on the Public API. The profile examples show these requests.
Using legacy IDs
In order to keep our API backwards compatible, support will continue for individualId and entityId. All places where a profileId can be supplied will also accept these older IDs.
Merged profiles
Profiles can be merged by users via the UI when there is a “duplicate detected”. When a merge happens one profile is picked as the “winner”, and the other profile is folded in.
In order to keep integrations simple, we’ll resolve any profileId, entityId, or individualId from “losing” profiles to the latest “winner” whenever they’re used. This means you don’t have to keep track of the latest profile ID in your records.
If you do want to keep track of the latest profileId, a webhook event is available upon merge which publishes the latest winning profileId along with all historical profile, entity, and individual IDs associated with that profile.
