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.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.
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
| Attribute | Description |
|---|---|
id READ-ONLY STRING | The profile ID (UUID V4). |
external_id STRING READ-ONLY | The profile external ID. This field references the primary identities identifier. Denoted by the identity is_primary attribute. |
title STRING | The profile salutation. |
first_name STRING | The profiles first name. |
last_name STRING | The profiles last name. |
full_name STRING READ-ONLY | The profiles full name. A concatenation of first_name and last_name |
email STRING EMAIL | The profile email. This field must be unique, and cannot exist on another profile. |
gender STRING | The profile gender. Accepted values are: * NULL - Omit the gender field * female * male * withheld * other |
currency STRING | The default currency attached to the profile Must be configured as a valid currency in Omneo |
joined_at DATE-TIME | The date the customer joined Omneo |
mobile_phone STRING PHONE | The primary mobile phone number with attached country code. example format: “+61412323123” This must be unique, and cannot exist on another profile |
mobile_phone_country INTEGER READ-ONLY | The country code for the provided mobile_phone example: “61” |
mobile_phone_national STRING READ-ONLY | The mobile_phone number without the country code. example: “412323123” |
mobile_phone_national_prefix STRING READ-ONLY | The mobile_phone_national with previx example: “0412323123” |
mobile_phone_e164 STRING READ-ONLY | the E. 164 compliant mobile_phone number e.g “+61412323123” |
secondary_phone STRING | The secondary phone number for the profile. |
birth_year INTEGER | The year of birth example: Birthday: 1-5-1990 the birth_year is 1990 |
birth_month INTEGER | The month of birth Represented as a numeric value from (1-12) |
birth_day INTEGER | The day of birth |
company STRING | The company of the profile |
occupation STRING | the occupation of the profile |
avatar_url STRING URL | The image used as the profile avatar |
preferred_location_id INTEGER | The profiles preferred location id Represented as the id of a valid location configured in Omneo |
preferred_location_external_id STRING | An external reference for the profiles preferred location. This is usually the location reference as it sits in your primary system outside Omneo |
joined_location_id INTEGER | The profiles joined location. Represented as the id of a valid location configured in Omneo |
joined_location_external_id STRING | An external reference for the profiles joined location. This is usually the location reference as it sits in your primary system outside Omneo |
joined_location INTEGER READ-ONLY | location data for the specified joined_location_id |
preferred_location INTEGER | location data for the specified preferred_location_id |
tier_handle STRING READ-ONLY | The tier_handle of the profile Which displays the achieved tier the profile has reached. |
tier OBJECT | Accompanying tier data for the profiles tier_handle |
birth_date DATE READ-ONLY | YYYY-MM-DD representation of birth_year, birth_month and birth_day |
birth_days INTEGER READ-ONLY | The count of days until the profiles next birthday. Calculated as the difference of days from this years birth_date until now. If this yearsbirth_date is in the past, then the following year will be used for the calculation |
birth_days_past INTEGER READ-ONLY | Value will return null if birth_date of this year, is in the future. If this years birth_date is in the past, birth_days_past will equal the number of days passed, since the profiles last birthday |
next_birthday DATE | The date of the profiles next birthday calculated 1 year from the profiles birth_date |
identities ARRAY | The profiles attached identities` |
tags ARRAY | The profiles attached tags |
attributes ARRAY | The profiles attached attributes |
statuses STRING | An array of the profiles attached Statuses Specify the status handle example: “influencer”, “media”, “staff” use Browse Statuses to review available statuses. |
custom_attributes ARRAY | Custom attributes attached to the profile |
address STRING | The default address against the profile. |
addresses ARRAY | All addresses against the profile. |
created_at DATE-TIME READ-ONLY | The UTC date & time the Profile record was created in ISO 8601 format. |
updated_at DATE-TIME READ-ONLY | The UTC date & time the Profile record was last updated in ISO 8601 format. |
profile_type STRING | Accepted values: * temporary * pending * active * deleted |