Batch Profiles
Profile
Batch Profiles
A POST to the /profiles/batch.json endpoint allows your application to process profiles in batch.
POST
Batch Profiles
Documentation Index
Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
Use this file to discover all available pages before exploring further.
Batch updating or creating profiles
This endpoint allows developers to create or update multiple profiles at once. This can be useful for one-off or incremental imports to Omneo. It is not recommended to use Batch importing to save on API calls, as these profiles will be added to a queue, and are subject to the workload of other jobs in the queue. Because this process is added as a background process, the results of these profiles are not available as an API response. Instead, when a profile is successfully updated or create the appropriateprofile.updated or profile.created webhook event will be triggered.
| Attribute | Description |
|---|---|
profiles ARRAY | An array of Profile Objects. Omneo will use each record in this array to create or update an omneo profile based on the match_criteria |
match_criteria STRING | The criteria to match the batch members with existing Omneo profiles. Specify ‘email’ to match by email. Or specify an identity handle |
Specifying a match_criteria
The match_criteria is used to match members in your batch, to existing Omneo Profiles.
If no profile is found using this criteria, a new Omneo profile will be created instead.
Match criteria can be:
“email” which will attempt to match the email specified in your profile batch
A simple batch import matching by email could look like the below:
identities by the handle
To match profiles by a specified identifier against the profile, simply specify the name of the identity handle in the match_criteria
Omneo will search for the value in your batch profiles[].identities array.
And will attempt to match an Omneo profile with a matching identity.