Skip to main content
The Profiles API creates, reads, updates, and deletes customer profiles. A Profile is the central object in Omneo: transactions, incentives, identities, ratings, and lists all link to a profile. See Profiles for a full conceptual overview.
Before adding a profile, use the preflight endpoints to confirm the email or mobile is available. This avoids handling a 422 Unprocessable Entity on every duplicate.
Add Profile (POST /v3/profiles) rejects duplicates. If the supplied email or mobile_phone is already in use by an active (non-soft-deleted) profile, the request returns 422 Unprocessable Entity. The profile is not created and no update is performed. An email previously held by a soft-deleted profile is treated as available.Edit Profile (PUT /v3/profiles/{profile}) has destructive-replace semantics on several nested collections. Including addresses, tags, statuses, regions, or organisations in the body replaces the entire set on the profile, soft-deleting or detaching anything not in the supplied list. Omitting the key leaves the collection untouched. identities, custom_attributes, and dates_attributes are upserts and do not destroy unmatched entries. comms_attributes is a partial merge.See Mutation semantics on POST and PUT for the complete table.

What is a profile?

Profiles are the core of customer data within Omneo. Use the Profiles API to quickly get access to core customer data such as name, gender, phone, birthday. Or even attribute data such as hair colour or jacket size. Profiles are one of the core features to the Omneo CX platform, and are used to link many other features of Omneo. Use this API to Create, Read, Update and Delete customer Profiles.

Profile Properties

Event Context

The profile context available in webhooks and targets.