Use the Migrate API to assign population data to master records, which is a one-time activity. A master record must have population data so that the Search Match API version 2 can match it by population.
The API triggers a job. After the job completes, the API assigns population data to the master records. You can monitor the status of the job in the My Jobs page.
The Migrate API assigns a population to a master record based on the following principles:
•If the master record has a single source record, it inherits the population of the source record.
•If the master record is formed by merging source records that have the same population, it inherits that population.
•If the master record is formed by merging source records that have different populations, MDM SaaS doesn't assign a population. For those records, the match process uses the default population of the match model.
For master records created before the April 2026 release, use the Migrate API to assign population data. For master records created after the April 2026 release, MDM SaaS automatically assigns population data to master records based on the populations of their source records.
To assign population data to master records, submit a POST request with the following URI:
POST {baseUrl}/public/api/v1/migrate
The response is in JSON format.
Request body
The following table describes the parameters in the request body:
Parameter
Type
Description
type
String
Type of migration operation. Set to POPULATE_MASTER_POPULATION.
beGuids
Array of String
Unique identifier of the business entity that contains the master records to assign population data to.
Enter a non-blank GUID value, such as c360.person. You can't enter an empty array or multiple values. To cover multiple business entities, submit a separate request for each business entity.
Request response
The response returns the job instance identifier as plain text. Use the job instance identifier to track the progress of the job on the My Jobs page.
For more information, see Monitoring assign population jobs.
Sample requests
The following sample request specifies the type of migration operation and the unique identifier of the business entity:
The beGuids parameter only accepts a single GUID despite being an array type. To run the operation for multiple business entities, submit a separate request for each business entity.
Sample responses
When the request is accepted, the API returns an HTTP 202 status and the job instance identifier as plain text.