Glossary of terms

A list of important terms used in this documentation.


A URL for a page where your clients can confirm their affiliation with you. After a client goes to the page and submits the requested information, we send you a legal entity ID for that client. You need a legal entity ID if you want to create properties with the API.

Learn more about getting affiliate links and legal entity IDs here.


Booking Assistant

A chatbot that handles messages between guests and properties. It acts as an intermediary, answering the simplest questions itself, and forwarding those that need human attention.

If you use Messaging API, you'll see the name "Booking Assistant" appear in messages as both sender and recipient.

See also the Booking Assistant video for property owners.


independent property

A property owned by a person under their own name, rather than by a company. Common examples are holiday homes and private apartments.

The creation process for independent properties is slightly different than the regular process.


An identifier for the legal entity that owns or manages a property (such as a property management company or a hotel chain.). When you create a property with Content API, you must provide a legal entity ID in the creation request.

Learn more about how to request a legal entity ID here.


machine account

A set of credentials (username and password) that grants access to the functions of the Connectivity APIs. You can manage your machine accounts in the Connectivity Portal.

Each API call must include a machine account username and password.



A sender or receiver of a message exchanged via Messaging API.


Payment Card Industry. "PCI" is often used as shorthand for "PCI compliant", which means "compliant with the standards created by the PCI Security Standards Council".


A hotel, bed & breakfast, or other type of guest accommodation. For a full list of supported accommodation types, see Property Class Type Codes.


reply option

A concept important for Messaging API. Read more here.


Response Unique IDentifier. Every API response body contains an RUID string at the end, like this:

<?xml version="1.0" encoding="UTF-8"?>
<!-- RUID: [UmFuZG9etc] -->

The string is unique for every response.

The Connectivity Support team uses RUIDs to find specific requests/responses in the API logs. If you need to contact Connectivity Support for troubleshooting or integration help, always provide one or more RUIDs.


special request

A message sent by a guest to a property, asking for a change to their reservation in one of these areas:

  • check-in/check-out time
  • extra bed
  • bed type
  • airport shuttle
  • parking reservation

If you use Messaging API, responding to special requests works differently than responding to other messages.


Single property owner. See independent property.