v3
latestOpenAPI 3.0.42026-07-312008682.1 MBAdd customer
Adds a new customer to the system and returns details of the added customer. If a customer with the specified email already exists, and OverwriteExisting is set to true, then the existing customer profile information is overwritten and the existing customer data returned. If OverwriteExisting is set to false, an error response is returned. Note this operation supports Portfolio Access Tokens.
Request body
Token identifying the client application.
Access token of the client application.
Name and version of the client application.
Type of the title prefix of the customer.
Note that the value should not be used as-is, but localized. For example, the value Misses should be displayed as Mrs. in English and Fr. in German.
Mister (Mr.)
Miss (Ms.)
Misses (Mrs.)
First name of the customer.
Last name of the customer.
Second last name of the customer.
ISO 3166-1 code of the Country.
Language and culture code of the customer's preferred language, according to their profile. For example: en-GB, fr-CA.
Date of birth in ISO 8601 format.
Country of birth.
Province of birth.
Place of birth.
Occupation of the customer.
Email address of the customer.
Phone number of the customer (possibly mobile).
Loyalty code of the customer.
Internal notes about the customer.
Registration number of the customer's car.
Customer's dietary requirements, e.g. Vegan, Halal.
Tax identification number of the customer.
Unique identifier of Company the customer is associated with.
Classifications of the customer.
Options of the customer.
Unique identifier of the chain. Required when using PortfolioAccessTokens, ignored otherwise.
Whether an existing customer should be overwritten in case of duplicity. This applies only to basic personal information (Title, FirstName, LastName, ...).
Value of Italian destination code.
Value of Italian fiscal code.
Value of Italian lottery code.
Response
OK
Unique identifier of the customer.
Unique identifier of the chain.
Unique number of the customer (max 19 digits).
Type of the title prefix of the customer.
Note that the value should not be used as-is, but localized. For example, the value Misses should be displayed as Mrs. in English and Fr. in German.
Mister (Mr.)
Miss (Ms.)
Misses (Mrs.)
Male
Female
First name of the customer.
Last name of the customer.
Second last name of the customer.
ISO 3166-1 code of the Country.
Language and culture code of the customer's preferred language, according to their profile. For example: en-GB, fr-CA.
Language and culture code of the customer's language, based on multiple sources. These sources include the preferred language specified in internal data based on previous bookings, and the preferred language of the customer specified in their profile. If neither of these sources are present, we use the native language based on the customer's nationality. The format is, for example, en-US or fr-FR.
Date of birth in ISO 8601 format.
ISO 3166-1 alpha-2 code of the birth country.
ISO 3166-2 code of the administrative division, e.g. ES-C.
Place of birth.
Occupation of the customer.
Email address of the customer.
Whether the customer's email address is a temporary email address from an OTA. For more details, see the product documentation.
Phone number of the customer (possibly mobile).
Tax identification number of the customer.
Loyalty code of the customer.
Accounting code of the customer.
Billing code of the customer.
Internal notes about the customer.
Registration number of the customer's car.
Customer's dietary requirements, e.g. Vegan, Halal.
Creation date and time of the customer in UTC timezone in ISO 8601 format.
Last update date and time of the customer in UTC timezone in ISO 8601 format.
Unique identifier of the Address of the customer.
Classifications of the customer.
Options of the customer.
Value of Italian destination code.
Value of Italian fiscal code.
Italian lottery code.
Unique identifier of Company the customer is associated with.
Unique identifier of the account (Customer) to which this customer is linked.
Activity State of customer record, i.e. whether active or deleted.
Whether the customer record is still active.
A list of room preferences, such as view type, bed type, and amenities.
Unique identifier of the user who created the customer.
Unique identifier of the user who last updated the customer.