# Mews Glossary for Open API users

This glossary lists the terms used within the **Mews Open API** and explains their meaning. The terms are presented in alphabetical order.

## Access Token <a href="#accesstoken" id="accesstoken"></a>

An Access Token is a unique security token for a given [Property](#Property) integration, which you need in order to access that property's data through the [Mews Connector API](#ConnectorAPI). The token encodes the permissions granted to that [Integration](#Integration). Integration partners are sent the Access Token by Mews when authorized by the property, alternatively the property can obtain the Access Token directly through Mews Operations, see [Find an integration access token](https://help.mews.com/s/article/find-an-integration-s-access-token?language=en_US). Note that in cases where there is more than one instance of the same [Integration](#Integration) in one [Property](#Property), each instance has a separate Access Token.

In the Connector API, most API endpoints require Access Token, [Client Token](#ClientToken) and [Client](#Client) fields to be included in the request data in order to authenticate the [Client](#Client) and to authorize access to the requested data and services. In the Channel Manager API, on the Mews side, most API endpoints instead require [Connection Token](#ConnectionToken) and [Client Token](#ClientToken) to perform a similar role.

Access Tokens normally allow access to a single [Property](#Property) or [Enterprise](#Enterprise), however some tokens may be [Portfolio Access Tokens](#PortfolioAccessToken), which allow access to all the properties within a [Portfolio](#Portfolio).

## Accommodation <a href="#accommodation" id="accommodation"></a>

Accommodation is synonymous with '[Stay](#Stay)' and refers to room-stay based services offered by a Property. These are the main services that properties offer to their customers, in fact a default [Stay](#Stay) service is created automatically by Mews and cannot be deleted. Accommodation services are [Bookable Services](#BookableService), i.e. they can be reserved or booked prior to a [Customer](#Customer)'s arrival.

## Account <a href="#account" id="account"></a>

Depending on context, Account could refer to a property account, user account or a financial account. However, the most common meaning of Account is a [Customer](#Customer) or [Company](#Company).

* The normal meaning of Account is a [Customer](#Customer) or [Company](#Company), i.e. it is a general term that covers both, and for which there is a single unique identifier or GUID.
* A property account is a record containing the details of a [Property](#Property), e.g. its name and address, see [Set up your property account](https://help.mews.com/s/article/set-up-your-property-account?language=en_US).
* A user account is a record containing the details of a [Property](#Property) [Employee](#Employee) and their access permissions, see [Setting up your account](https://help.mews.com/s/article/setting-up-your-account?language=en_US).
* A financial account is a record of financial transactions, e.g. a [Paymaster](#Paymaster) account or guest [Bill](#Bill).

## Accounting Category <a href="#accountingcategory" id="accountingcategory"></a>

Accounting Categories are used to categorize [Accounting Items](#AccountingItem) (both [Orders](#Order) and [Payments](#Payment)) and they are configured differently for each [Property](#Property). All [Accounting Items](#AccountingItem) belong to an Accounting Category. Each Accounting Category has a name, a classification, and associated codes used for accounting purposes. Accounting Category is specified for a [Service](#Service) in the service settings, so when an [Order](#Order) is made against a [Service](#Service) then it uses that Accounting Category.

## Additional Services <a href="#additionalservices" id="additionalservices"></a>

Additional Services are [Services](#Service) that cannot be purchased when a [Reservation](#Reservation) is made, unlike [Bookable Services](#BookableService). They are additional or extra to the main service, and can be purchased on-site and added to a guest's [Bill](#Bill). Examples include room service, airport transfer and spa services.

## Accounting Item <a href="#accountingitem" id="accountingitem"></a>

All [Order](#Order) items and [Payment](#Payment) items are types of Accounting Item. [Order](#Order) items are consumed items, [Payment](#Payment) items are payments or invoices.

## ARI <a href="#ari" id="ari"></a>

ARI is a general hospitality industry term and stands for [Availability](#Availability), [Rates](#Rate) and [Inventory](#Inventory).

## Availability <a href="#availability" id="availability"></a>

Availability is the quantity of [Spaces](#Space) of specified [Space Categories](#SpaceCategory) (or quantity of [Resources](#Resource) of specified [Resource Categories](#ResourceCategory) ) that are open for sale during a specified time period.

## Availability Block <a href="#availabilityblock" id="availabilityblock"></a>

Availability Block is synonymous with Group Block, it implies a block of [Inventory](#Inventory) set aside for group sales, e.g. a block of guest rooms set aside for a wedding, or a block of rooms set aside for a tour operator. Normally these are a group of similar [Spaces](#Space) belonging to the same [Space Category](#SpaceCategory) and subject to the same [Rate](#Rate).

Availability Blocks are different than [Resource Blocks](#ResourceBlock), which are groups of [Spaces](#Space) taken out of Inventory because they are out-of-service or being used for other purposes.

## Bill <a href="#bill" id="bill"></a>

A Bill is a financial account for a [Customer](#Customer) or [Company](#Company), synonymous with 'folio'. It can contain a mix of [Order](#Order) items and [Payment](#Payment) items. A Bill can be 'open', i.e. you can modify it, or 'closed', i.e. closed to further changes. A closed Bill is assumed to be balanced, i.e. sums to zero, and 'settled' by the [Customer](#Customer) or [Company](#Company).

Note that a [Customer](#Customer) Bill is linked to the [Customer](#Customer) [Profile](#Profile), not to the [Reservation](#Reservation). However, using the API you can still identify the [Reservations](#Reservation), Bills and [Services](#Service) that an [Accounting Item](#AccountingItem) is linked to.

For more information, search "Bill" in [Mews Help](https://help.mews.com/s/?language=en_US).

## Bookable Service <a href="#bookableservice" id="bookableservice"></a>

Bookable Services are the main [Services](#Service) in a [Property](#Property) that your guests can book or reserve, such as the default [Stay](#Stay) [Service](#Service). They are displayed on the system timeline and don't depend on any other [Service](#Service) for their purchase, as opposed to [Additional Services](#AdditionalServices). See [Set up a bookable service](https://help.mews.com/s/article/set-up-a-bookable-service?language=en_US).

## Booker <a href="#booker" id="booker"></a>

A Booker is a [Customer](#Customer) who makes a [Reservation](#Reservation) for another Customer. They are not the main Customer linked to the Reservation, who is referred to as the Reservation [Owner](#Owner).

## Booking <a href="#booking" id="booking"></a>

This term is synonymous with [Reservation](#Reservation).

## Booking Engine <a href="#bookingengine" id="bookingengine"></a>

Booking Engine implies the part of a booking website or app through which users can make bookings in customer properties. The **Mews Booking Engine** is part of the Mews product portfolio.

## Booking Engine API <a href="#bookingengineapi" id="bookingengineapi"></a>

The **Mews Booking Engine API** is one of the main APIs within the [Mews Open API](#OpenAPI-MewsOpenAPI). It can be used by custom Booking Engines to enable users to check availability and make reservations directly in Mews.

## Business Segment <a href="#businesssegment" id="businesssegment"></a>

Business Segments, Channel Manager Segments, or just Segments, are used to classify [Reservations](#Reservation) by attributes relevant to a [Property](#Property)'s operations, such as traveler type or whether the [Reservation](#Reservation) is group or individual. They allow the [Property](#Property) to gather information from reports to identify trends and to target customers more effectively. See [Create, modify or delete a segment](https://help.mews.com/s/article/create-modify-or-delete-a-segment?language=en_US\&Language=en_US).

## Cashier <a href="#cashier" id="cashier"></a>

A Cashier is a role for handling payments. Multiple cashiers can be configured for a [Property](#Property), and [Employees](#Employee) allocated against them. Each cashier has a specified currency that they work in. See [Create or delete a cashier](https://help.mews.com/s/article/create-or-delete-a-cashier?language=en_US).

## Chain <a href="#chain" id="chain"></a>

A Chain is a group of multiple [Properties](#Property) or [Enterprises](#Enterprise) under the same management. In the context of the Mews system, Chains are used to define legal relationships between [Enterprises](#Enterprise), and for sharing certain data which is common across the Chain. Note that Chains are separate to [Portfolios](#Portfolio) used for [Multi-property](#Multi-property) working as part of **Mews Multi-Property**.

## Channel <a href="#channel" id="channel"></a>

Channel is shorthand for the sales channel through which [Bookings](#Booking) are made, e.g. direct from the [Property](#Property) website, from a Central Reservation System (CRS), from a Global Distribution System (GDS) or from an Online Travel Agent (OTA).

## Channel Manager <a href="#channelmanager" id="channelmanager"></a>

A Channel Manager is a hub for managing the various sales [Channels](#Channel) that a [Property](#Property) may be connected to. Typically a [Property](#Property) would connect its Mews Property Management System (Mews Operations) to a Channel Manager and the Channel Manager would in turn connect to the various Channels. SiteMinder is a well-known example of a Channel Manager.

Mews Operations passes ARI data ([Availability](#Availability), [Rates](#Rate) and [Inventory](#Inventory)) to the Channel Manager, which distributes them to the connected [Channels](#Channel), and Mews Operations receives [Reservations](#Reservation) from the Channel Manager.

The part of the [Mews Open API](#OpenAPI-MewsOpenAPI) that supports this two-way functionality is called the [Channel Manager API](#ChannelManagerAPI). Typically, this is connected via an [Integration](#Integration) to a Channel Manager, however the same API may also be used to connect other sales channels. From the API's point of view, they all have the same functionality, sending outgoing updates of ARI data ([Availability](#Availability), [Rates](#Rate) and [Inventory](#Inventory)) and receiving incoming [Reservations](#Reservation).

## Channel Manager API <a href="#channelmanagerapi" id="channelmanagerapi"></a>

The **Mews Channel Manager API** is one of the main APIs within the [Mews Open API](#OpenAPI-MewsOpenAPI). It is used by Channel Managers and other distribution channels to fetch availability, rates and inventory, and make reservations.

## Channel Manager ID <a href="#channelmanagerid" id="channelmanagerid"></a>

This is another name for the [Connection Token](#ConnectionToken) used in the Channel Manager API, because each [Connection Token](#ConnectionToken) identifies a unique [Channel Manager](#ChannelManager) [Connection](#Connection) (or any other client application connection).

## Channel Manager Segment <a href="#channelmanagersegment" id="channelmanagersegment"></a>

See [Business Segment](#BusinessSegment).

## Charge Rule <a href="#chargerule" id="chargerule"></a>

Charge Rule is the particular method of calculation that the system uses for deriving a [Product](#Product) charge or price, e.g. 'per person per night' implies that the charge is the individual nightly rate multiplied by the number of people and the the number of nights.

## Check-in <a href="#checkin" id="checkin"></a>

Check-in is the process of registering a [Customer](#Customer)'s arrival at a [Property](#Property) at the beginning of their stay, although this may be performed in advance of their physical arrival on site, using an online check-in process. The [Mews Open API](#OpenAPI-MewsOpenAPI) may describe this process as 'start reservation', implying the start of the reserved period of stay.

## Check-out <a href="#checkout" id="checkout"></a>

Check-out is the process of registering a [Customer](#Customer)'s departure from a [Property](#Property) at the end of their [Stay](#Stay). The [Mews Open API](#OpenAPI-MewsOpenAPI) may describe this process as 'process reservation', implying that the the [Bill](#Bill) has been settled and therefore it can be processed and closed.

## Client <a href="#client" id="client"></a>

The meaning of Client depends on context, but it generally refers to the client application or partner application which is accessing the API and consuming API data and services - thus it is a client of the API. For example, the [Client Token](#ClientToken) is the security token used to uniquely identify the client application.

## Client Token <a href="#clienttoken" id="clienttoken"></a>

A Client Token is a security token you use to authenticate your application when accessing the API. As such, you should keep this token secure and never share it. You will be provided with the Client Token by Mews during the partner on-boarding process.

Client Tokens are used across the Mews APIs, however there may be differences in detail between individual APIs so please consult the API documentation for the particular API you are using.

In the Connector API, most API endpoints require [Access Token](#AccessToken), Client Token and [Client](#Client) fields in the request data in order to authenticate the [Client](#Client) and to authorize access to the requested data and services. In the Channel Manager API, on the Mews side, most API endpoints similarly require [Connection Token](#ConnectionToken) and Client Token.

In the Channel Manager API, on the Channel Manager side, a Client Token is still required, but in this case the client application is the Mews application.

Note that you need a different Client Token to connect to different Mews environments, i.e. one token for the Production environment and a separate token for the Demo environment.

## Command <a href="#command" id="command"></a>

A Command is a command or instruction that the system sends to a physical [Device](#Device) such as an on-premise printer or on-premise key cutter.

## Companion <a href="#companion" id="companion"></a>

A Companion is a [Customer](#Customer) or [Guest](#Guest) linked to a [Reservation](#Reservation) who is not the primary Customer or [Owner](#Owner), but an additional Guest.

## Company <a href="#company" id="company"></a>

Company is a corporate entity linked to a booking or [Reservation](#Reservation), for example in the case of a corporate travel booking. Company records which store details about each company are called Company [Profiles](#Profile). Companies can be automatically to incoming [Reservations](#Reservation) using [Channel Manager](#ChannelManager) [Mapping Tables](#MappingTable).

[Travel Agencies](#TravelAgency) are a special type of Company and within the API they may be considered as separate entities.

## Complimentary Product Item <a href="#complimentaryproductitem" id="complimentaryproductitem"></a>

A Complimentary Product Item is a zero cost [Product Item.](#ProductItem) The system considers these as 'inactive' and therefore they do not appear in the Accounting Report nor on the [Customer](#Customer) Account under **Customer profile > Billing**. If it is a [Stay Product](#StayProduct), then it appears against **Reservation module > Items**. If it is a [Service Product](#ServiceProduct), it appears against **Customer profile > Dashboard > Orders**.

## Connection <a href="#connection" id="connection"></a>

A Connection represents a single interface instance between a given [Channel Manager](#ChannelManager) or other client application and the Channel Manager API (Mews side). The concept of a Connection is unique to the Channel Manager API. Each Connection has an associated [Connection Token](#ConnectionToken), which you need to access API data and services via that connection.

## Connection Token <a href="#connectiontoken" id="connectiontoken"></a>

A Connection Token is a unique security token for a given [Connection](#Connection) that a [Channel Manager](#ChannelManager) or other client application makes to the Mews side of the Channel Manager API. You need this in order to access a [Property](#Property)'s data through the API. A single client application can make one or more [Connections](#Connection), with each one having a unique Connection Token.

As an integration partner, you are sent the Connection Token by Mews when authorized by the [Property](#Property), alternatively the [Property](#Property) can obtain the Connection Token through Mews Operations, see for example the [Channel manager onboarding guide](https://help.mews.com/s/article/channel-manager-onboarding-guide?language=en_US) and [How to switch from one channel manager to another](https://help.mews.com/s/article/how-to-switch-from-one-channel-manager-to-another?language=en_US).

You only use the Connection Token when working with the Mews Channel Manager API, the [Access Token](#AccessToken) serves a similar function when working with the Connector API.

If your application supports the [getProperties](https://mews-systems.gitbook.io/channel-manager-api/mews-api#get-properties) API operation, this can be used to recover the Connection Tokens for all [Connections](#Connection) the [Property](#Property) supports for this [Client](#Client) application. In this case, an [Employee](#Employee) email address is used as an authorization token.

## Connector API <a href="#connectorapi" id="connectorapi"></a>

The **Mews Connector API** is one of the main APIs within the [Mews Open API](#OpenAPI-MewsOpenAPI). This should not be confused with Mews Connector, which is a separate system with a similar name. The Connector API is a general-purpose API that gives access to data and services in **Mews Operations** and supports numerous use cases.

## Counter <a href="#counter" id="counter"></a>

A Counter is a literal numerical count of something useful such as the number of [Bills](#Bill) closed, maintained in real time.

## Customer <a href="#customer" id="customer"></a>

The normal meaning of Customer within the [Mews Open API](#OpenAPI-MewsOpenAPI) is the end-customer or consumer of the services that the hospitality [Enterprise](#Enterprise) provides, typically a hotel [Guest](#Guest). If you substitute the word 'guest', you won't go far wrong. The details about a Customer are stored in their [Profile](#Profile). Note that Customer Profiles can exist independently of a [Reservation](#Reservation).

## Department <a href="#department" id="department"></a>

Department is an administrative or functional division of a [Property](#Property), e.g. Housekeeping or Front of House. An [Employee](#Employee) may be assigned to a Department, and [Tasks](#Task) may be assigned to [Employees](#Employee) or Departments.

## Deposit <a href="#deposit" id="deposit"></a>

A Deposit is a sum payed as a first instalment, e.g. against a [Reservation](#Reservation), with the intention to pay the balance at a later date, e.g. on [Check-out](#CheckOut).

## Device <a href="#device" id="device"></a>

The term Device refers to a physical hardware device or system that Mews connects to, such as an on-premise printer or an on-premise key cutter / key encoder.

## Distributor <a href="#distributor" id="distributor"></a>

Distributor is the old name for the Mews Booking Engine. As such, there may be references to Distributor in the Booking Engine Guide, especially in URLs, function names and the like. For Distributor, read Mews Booking Engine.

## Editable History Interval <a href="#editablehistoryinterval" id="editablehistoryinterval"></a>

Editable History Interval (EHI) is the shorter of the two Editable History Windows (EHW) used in Mews Operations. For a full explanation of these terms and how to interpret them, see [Editable History Window](#EditableHistoryWindow).

## Editable History Window <a href="#editablehistorywindow" id="editablehistorywindow"></a>

Editable History Window (EHW) refers to the historical time window within which amendments are permitted to certain data before they are considered fully closed to editing. It is expressed as a period of time, e.g. 2 days, this means that once the data is 2 days old it can no longer be changed and is considered a frozen historical record.

There are in fact two EHWs and they are separate configuration parameters in Mews Operations: one is the **Operational EHW** (concerned with [Reservations](#Reservation)) and the other is the **Accounting EHW** (concerned with accounting data).

For example, changes are permitted to [Bills](#Bill) and invoices after they are closed, for a period of time equal to the Accounting Editable History Window. After that time has elapsed, [Bills](#Bill) and invoices can no longer be edited. The same applies to historical [Reservations](#Reservation) data, these cannot be edited after the Operational Editable History Window time period has elapsed. If you try to post an [Accounting Item](#AccountingItem) or [Outlet](#Outlet) item with a 'consumption time' that falls outside of the permitted editable time period, you will not be permitted to do so and will receive an appropriate error response.

In the Mews Connector API, the *Get Configuration* operation returns **Editable History Interval**, which is the shorter of the two Editable History Windows. Any operation that you perform through the API on historical data will therefore be valid if it lies within this interval period, regardless of whether it is related to accounting data or reservation data.

For more information:

* [Set up your Editable History Windows](https://help.mews.com/s/article/set-up-your-editable-history-windows?language=en_US)
* [How to extend the Operational & Accounting editable history window](https://help.mews.com/s/article/how-to-extend-the-operational-accounting-editable-history-window?language=en_US)
* [The accounting configuration in Mews - an overview of the settings](https://help.mews.com/s/article/what-is-the-accounting-configuration?language=en_US)

## Employee <a href="#employee" id="employee"></a>

A member of staff at a [Property](#Property) or [Enterprise](#Enterprise). They may also be referred to as a [User](#User) of the Mews system, depending on context.

## Enterprise <a href="#enterprise" id="enterprise"></a>

The term Enterprise implies a single Mews customer, either an individual [Property](#Property) such as a hotel or hostel, or some other type of Mews customer which consists of multiple physical properties, such as a campus.

## Extra <a href="#extra" id="extra"></a>

Additional [Products](#Product) bundled with a [Reservation](#Reservation) may be described as Extras.

## Group <a href="#group" id="group"></a>

The term Group will rarely be used on its own except in a specific context, since the term Group could refer to a group of [Properties](#Property) (normally a [Chain](#Chain) or [Enterprise](#Enterprise)), a [Reservation Group](#ReservationGroup), a [Group Block](#GroupBlock), or a [Rate Group](#RateGroup).

## Group Block <a href="#groupblock" id="groupblock"></a>

See [Availability Blocks](#AvailabilityBlock).

## Guest <a href="#guest" id="guest"></a>

See [Customer](#Customer). The term Guest is used in some parts of the [Mews Open API](#OpenAPI-MewsOpenAPI), but it should be read as the more general term [Customer](#Customer).

## Hotel <a href="#hotel" id="hotel"></a>

See [Property](#Property). The term Hotel is used in some parts of the [Mews Open API](#OpenAPI-MewsOpenAPI), but it should be read as the more general term [Property](#Property).

## Integration <a href="#integration" id="integration"></a>

When a [Property](#Property) or [Enterprise](#Enterprise) in Mews makes a connection with a partner system, this connection is called an Integration. A [Property](#Property) or [Enterprise](#Enterprise) can have more than one instance of an Integration with a given partner system, but normally it would only have one.

## Inventory <a href="#inventory" id="inventory"></a>

The number of [Spaces](#Space) (e.g. guest rooms) available for sale, distributed across sales [Channels](#Channel).

## Item <a href="#item" id="item"></a>

Item could be a [Product Item](#ProductItem), [Order](#Order) Item, [Payment](#Payment) Item or [Accounting Item](#AccountingItem).

## Length of Stay <a href="#lengthofstay" id="lengthofstay"></a>

The period of a [Customer](#Customer)'s stay-over, expressed usually in number of nights.

## Mapping Table <a href="#mappingtable" id="mappingtable"></a>

Mapping Tables are used to map relationships between [Space Categories](#SpaceCategory), [Rates](#Rate), [Products](#Product) and [Companies](#Company), using abbreviated codes for the respective entities. For example, in the Channel Manager API, 'product mappings' map [Rate Plan](#RatePlan) codes such as "NR" to [Product](#Product) codes such as "AUR".

## Marketplace <a href="#marketplace" id="marketplace"></a>

Marketplace is the app store for Mews integration partners that Mews customers are able to see within their Mews account and from where they can purchase compatible products and services. Learn [how to connect and disconnect integrations available in the Mews Marketplace](https://help.mews.com/s/article/connect-and-disconnect-integrations?language=en_US\&Language=en_US).

## Message <a href="#message" id="message"></a>

The meaning of the term Message may depend on context, but generally it refers to customer messages (i.e. guest messages) within **Mews Operations**. The Mews [Connector API](#ConnectorAPI) permits API clients to integrate with the Mews customer messaging system and thus send and receive such messages.

## Message Thread <a href="#messagethread" id="messagethread"></a>

Message threads are conversations initiated by a customer (i.e. a guest), within the customer messaging system of **Mews Operations**. A message thread consists of one or more [Messages](#Message).

## Multi-property <a href="#multi-property" id="multi-property"></a>

**Mews Multi-Property** is an optional module of **Mews Operations** that supports above-property level functionality, such as central management of users, rates and vouchers, across a [Portfolio](#Portfolio) of multiple [Properties](#Property). This functionality is reflected in the [Mews Connector API](#ConnectorAPI) through the use of [Portfolio Access Tokens](#PortfolioAccessToken).

## Open API <a href="#openapi-mewsopenapi" id="openapi-mewsopenapi"></a>

The **Mews Open API** refers to the family of APIs provided by Mews to partners and customers for them to connect and access data and services in Mews. Currently it consists of three separate APIs: Mews Connector API, Mews Channel Manager API, and Mews Booking Engine API. The Mews Open API should not be confused with the term OpenAPI (without the space).

## OpenAPI <a href="#openapi-swagger" id="openapi-swagger"></a>

OpenAPI is a public standard for defining Web APIs. OpenAPI definitions may be available for some or all of the Mews Open API - see the current API documentation for details. The OpenAPI specification was formerly known as Swagger and may still be referred to by that name.

## Order <a href="#order" id="order"></a>

[Accounting Items](#AccountingItem) are split into [Order](#Order) items (consumed items, such as night stays or products) and [Payment](#Payment) items (such as cash, credit card payments or invoices). Thus an Order is a consumed [Service](#Service) or [Product](#Product) item.

## Outlet <a href="#outlet" id="outlet"></a>

An Outlet is a retail outlet or retail location in a [Property](#Property), such as a bar, restaurant or spa centre. Outlets are used to record revenue and payments that occur external to the Mews system.

While consumed items that are to be settled later by a guest or corporate account are posted to their respective [Customer](#Customer) [Profiles](#Profile) in Mews, items that have been consumed AND paid for should be posted to Outlets.

You can read more about [how properties use Outlets](https://help.mews.com/s/article/set-up-outlets?language=en_US) and how the figures appear on the [Mews Accounting Report](https://help.mews.com/s/article/accounting-report?language=en_US).

## Owner <a href="#owner" id="owner"></a>

The Owner of a [Reservation](#Reservation) is the primary [Customer](#Customer) linked to the Reservation, i.e. the primary [Guest](#Guest). Additional Guests are known as [Companions](#Companion).

## Package <a href="#package" id="package"></a>

Package implies a bundle of [Services](#Service) and service-related [Products](#Product), e.g. if a room-stay is booked together with a spa treatment, or a room-stay with breakfast.

Product rules can be used to create packages where [Products](#Product) are automatically added to a [Reservation](#Reservation) when it is made. See [Package products with accommodation](https://help.mews.com/s/article/package-products-with-accommodation?language=en_US).

## Paymaster <a href="#paymaster" id="paymaster"></a>

A Paymaster account is a type of financial account used to compile charges into a single [Bill](#Bill) and issue a single invoice. This could be used for issuing a [Bill](#Bill) to a non-resident customer who doesn't have a [Profile](#Profile) on the system (also known as a **Lobby Bar Paymaster**), or to a [Travel Agent](#TravelAgency) or other [Company](#Company) which wants to receive a regular invoice for all their bookings with multiple [Customers](#Customer) (also known as a **City Ledger Paymaster**).

## Payment <a href="#payment" id="payment"></a>

[Accounting Items](#AccountingItem) are split into [Order](#Order) items (consumed items, such as night stays or products) and Payment items (such as cash, credit card payments or invoices). Thus a Payment is a financial payment on an account.

## Payment Card <a href="#paymentcard" id="paymentcard"></a>

A Payment Card is a payment device in the form of a physical card or its electronic equivalent issued by a financial institution and which enables its owner to authorize payments from the owner's financial account. A Payment Card is associated with a [Customer](#Customer) or [Company](#Company). Multiple Payment Cards can be linked to a [Profile](#Profile), see [Adding a new payment card](https://help.mews.com/s/article/add-a-new-payment-card?language=en_US).

## Portfolio <a href="#portfolio" id="portfolio"></a>

A Portfolio is a collection of [Properties](#Property) or [Enterprises](#Enterprise) that form part of a single group, for the purposes of centralised management of that group when using **Mews Multi-Property**. See also [Multi-property](#Multi-property).

## Portfolio Access Token <a href="#portfolioaccesstoken" id="portfolioaccesstoken"></a>

Portfolio Access Tokens are special types of [Access Token](#AccessToken) that grant access to all [Properties](#Property) or [Enterprises](#Enterprise) within a [Portfolio](#Portfolio), rather than just a single [Property](#Property) or [Enterprise](#Enterprise). These are used to facilitate [Multi-property](#Multi-property) functionality through the **Mews Open API**. API operations that support Portfolio Access Tokens may work across all [Enterprises](#Enterprise) within scope of the token, or you may specify which individual [Enterprise](#Enterprise) from within the [Portfolio](#Portfolio) you wish the operation to work with.

## Preauthorization <a href="#preauthorization" id="preauthorization"></a>

Preauthorization or pre-authorization (often abbreviated 'pre-auth') is a [Payment Card](#PaymentCard) provider service which puts a time-limited hold on an amount authorized by the card owner, reducing the available funds, until the transaction is 'cleared' or 'settled' or cancelled.

You might use this for instance when a [Reservation](#Reservation) is made to ensure that the account holder has sufficient funds to settle the [Bill](#Bill), as the service fails if insufficient funds are available.

A Preauthorization does not take the funds immediately but puts a temporary hold on them. The length of time for the hold can vary.

## Price <a href="#price" id="price"></a>

Price is the amount of money expected in exchange for goods and services, its use depends on context but usually in the [Mews Open API](#OpenAPI-MewsOpenAPI) it refers to the price of a [Reservation](#Reservation). The system calculates this from the nightly rate and the number of nights of the [Stay](#Stay).

## Product <a href="#product" id="product"></a>

A Product is a purchasable item linked to a [Service](#Service). Although all Products are associated with [Services](#Service), those linked to [Stay](#Stay) [Services](#Service) are sometimes called [Stay Products](#StayProduct) (or Reservation Products) and those linked to other [Services](#Service) are sometimes called [Service Products](#ServiceProduct).

Products can be items that can be purchased in their own right, or they can be 'relative products', meaning that they are defined relative to another product, e.g. a discounted version of the original product is a relative product which can have a price expressed as a percentage.

Additional Products bundled with a [Reservation](#Reservation) may also be described as [Extras](#Extra).

## Product Item <a href="#productitem" id="productitem"></a>

Product Item is an instance of a [Product](#Product) added to a [Customer](#Customer)'s [Bill](#Bill).

## Product Rule <a href="#productrule" id="productrule"></a>

Product Rules are the rules that Mews uses for automatically creating [Packages](#Package), i.e. they are a set of rules that automatically add or remove [Products](#Product) from a [Reservation](#Reservation) when it is made. See [Packages](#Package). You configure Product Rules as part of setting up [Rates](#Rate).

## Product Service Order <a href="#productserviceorder" id="productserviceorder"></a>

Product Service Order is the name given to an [Order](#Order) made against an [Additional Service](#AdditionalServices) (e.g. breakfast or minibar), as opposed to a [Reservation](#Reservation). Some care is needed here, as this is strictly an Additional Service Order and not to be confused with [Products](#Product).

## Profile <a href="#profile" id="profile"></a>

In its general sense, a Profile is a 'record of details' about some entity, such as a [Customer](#Customer), stored on the system as a data record. Typically, the term Profile implies the encapsulated details about a [Customer](#Customer) (a Customer Profile or Guest Profile) or a [Company](#Customer) (a Company Profile). In some cases, the term may refer to the encapsulated details about a [User](#User) on the Mews system (a User Profile). Sometimes the term is used explicitly, but sometimes the term [Customer](#Customer), [Company](#Customer) or [User](#User), when used on their own, implies a Profile.

## Property <a href="#property" id="property"></a>

Property is a general hospitality industry term to refer to a single hotel, hostel, resort, apartment building, cruise ship or other similar entity providing lodgings and hospitality. Thus a Property is an individual hospitality business that is a user and customer of Mews.

## Rate <a href="#rate" id="rate"></a>

Rate is the term used to describe the price per night for a [Stay](#Stay) . It depends on a number of factors, including the type of [Space](#Space) and the date. Sometimes a Rate is a relative rate based on a 'base rate'.

## Rate Group <a href="#rategroup" id="rategroup"></a>

A Rate Group is a grouping of [Rates](#Rate) that all share the same cancellation policies. For example, all 'flexible rates' would be one Rate Group, all 'non-refundable rates' would be another Rate Group, and all 'corporate rates' would be another Rate Group.

## Rate Plan <a href="#rateplan" id="rateplan"></a>

Rate Plan is synonymous with [Rate](#Rate).

## Reservation <a href="#reservation" id="reservation"></a>

Reservation has the normal hospitality meaning, i.e. a contract between a [Property](#Property) and a named [Customer](#Customer) or agent to set aside a category of [Space](#Space) and/or provide some hospitality [Service](#Service) for a specified period of time, such as a guest bedroom for a specific date and duration (in this case a [Stay](#Stay) Reservation). The contract would also contain a [Price](#Price) and terms and conditions such as a cancellation policy.

## Reservation Group <a href="#reservationgroup" id="reservationgroup"></a>

A Reservation Group is a collection of associated [Reservations](#Reservation). They are collected together and given a group name for easy reference. A group would include all [Reservations](#Reservation) for a wedding party or corporate event, for example.

## Resource <a href="#resource" id="resource"></a>

A Resource is something that can be sold, reserved or used. This could be an object or even the services of a person, but normally in our context it refers to a physical accommodation-based resource such as a hotel room, for which we use the general term [Space](#Space). In simple terms, a hotel room is a type of [Space](#Space), and a [Space](#Space) is a type of Resource.

The [Mews SpaceTime project](https://developers.mews.com/project-spacetime/) has broadened the scope of reservable entities from [Rooms](#Room) to [Spaces](#Space) to Resources, and this remains an on-going project. As a result, within the [Mews Open API](#OpenAPI-MewsOpenAPI) you may see references to Resources and corresponding [Resource Categories](#ResourceCategory), but you may also see references to [Spaces](#Space) and corresponding [Space Categories](#SpaceCategory). In most cases you will probably find that they correspond to the same thing, i.e. hotel rooms.

## Resource Access Token <a href="#resourceaccesstoken" id="resourceaccesstoken"></a>

A Resource Access Token is a general term for a time-limited security token granting access to a specified resource. In practise within Mews this means a PIN code (Personal Identification Number) or RFID tag (Radio Frequency ID) which may be in the form of a physical card, tag, wristband or digital equivalent used to access services, doors or similar within a [Property](#Property).

Note a Resource Access Token is completely separate from and unrelated to the [Access Token](#AccessToken) used by [Client](#Client) applications to access the [Mews Open API](#OpenAPI-MewsOpenAPI); and the word 'resource' is used in the broadest sense and does not necessarily imply a [Space](#Space).

## Resource Block <a href="#resourceblock" id="resourceblock"></a>

Resource Blocks are groups of [Resources](#Resource) or [Spaces](#Space) that you take out of [Inventory](#Inventory) because they are temporarily out-of-service or being used for other purposes.

Do not confuse Resource Blocks with [Availability Blocks](#AvailabilityBlock), which are groups of [Spaces](#Space) taken out of [Inventory](#Inventory) because they are set aside for group sales.

## Resource Category <a href="#resourcecategory" id="resourcecategory"></a>

This is the category to which a [Resource](#Resource) belongs, analogous to [Space Category](#SpaceCategory) but at a higher level of abstraction. For the difference between these concepts, see [Resource](#Resource) and [Space](#Space).

## Restriction <a href="#restriction" id="restriction"></a>

Restrictions are specified limitations on [Space](#Space) [Availability](#Availability), for example the restriction that a [Space Category](#SpaceCategory) is only available if booked for a minimum [Length of Stay](#LengthOfStay) (LOS) or the restriction that a [Space Category](#SpaceCategory) is 'closed to arrival'.

## Room <a href="#room" id="room"></a>

The term Room implies a hotel room or a function room, however the term is rarely used within the [Mews Open API](#OpenAPI-MewsOpenAPI), instead the more general term [Space](#Space) is used, or in some cases the even more general term [Resource](#Resource). A room such as a guest bedroom or suite is a type of [Space](#Space), but a [Space](#Space) may also be a car parking bay or a function room.

## Rule <a href="#rule" id="rule"></a>

The meaning of Rule depends on context, but may be a [Product Rule](#ProductRule) or a [Charge Rule](#ChargeRule).

## Segment <a href="#segment" id="segment"></a>

See [Business Segment](#BusinessSegment).

## Service <a href="#service" id="service"></a>

A Service is any type of saleable hospitality service provided by a [Property](#Property), including an accommodation service or room-stay. The definition is quite broad, and could include a taxi service, room service or minibar service. All items that can be consumed by a [Customer](#Customer) are made against a Service.

These can be [Bookable Services](#BookableService) or [Additional Services](#AdditionalServices). [Bookable Services](#BookableService) are ones that can be purchased when a [Reservation](#Reservation) is made. [Additional Services](#AdditionalServices) cannot be purchased when a [Reservation](#Reservation) is made, but can be purchased on-site and manually added to a [Customer](#Customer) [Bill](#Bill).

The default [Bookable Service](#BookableService) is the [Stay](#Stay) Service, which Mews creates automatically and which cannot be deleted, so every [Property](#Property) has a [Stay](#Stay) Service.

Services can have a service fee, and can also have associated [Products](#Product). All [Products](#Product) are linked to Services. Some [Products](#Product) are bundled with a Service when the [Reservation](#Reservation) is made, according to configured [Product Rules](#ProductRule), this is called a [Package](#Package).

You can read more about the relationship between services and products in [Understanding services](https://help.mews.com/s/article/understanding-services?language=en_US).

## Service Order <a href="#serviceorder" id="serviceorder"></a>

A Service Order is an [Order](#Order) made against a [Service](#Service). An [Order](#Order) made against a [Bookable Service](#BookableService) is known as a [Reservation](#Reservation). Thus a [Reservation](#Reservation) is a type of Service Order.

When we think of [Reservation](#Reservation), we normally think of a [Stay](#Stay)  [Reservation](#Reservation) (i.e. booking one's stay at a property). This is simply an [Order](#Order) made against the default [Stay](#Stay) [Service](#Service) . But a [Reservation](#Reservation) in the broadest sense could be an [Order](#Order) made against any [Bookable Service](#BookableService), e.g. car parking or a tennis court.

An [Order](#Order) made against an [Additional Service](#AdditionalServices) (e.g. breakfast or minibar) is known as a [Product Service Order](#ProductServiceOrder). Some care is needed here, as this is strictly an Additional Service Order and not to be confused with [Products](#Product).

In summary, A Service Order is one of two types, either a [Reservation](#Reservation) (an [Order](#Order) against a [Bookable Service](#BookableService)) or a [Product Service Order](#ProductServiceOrder) (an [Order](#Order) against an [Additional Service](#AdditionalServices)).

## Service Product <a href="#serviceproduct" id="serviceproduct"></a>

A [Product](#Product) is a purchasable item linked to a [Service](#Service). Although all [Products](#Product) are associated with [Services](#Service), those linked to [Stay](#Stay) [Services](#Service) are sometimes called [Stay Products](#StayProduct) (or Reservation Products) and those linked to other [Services](#Service) are sometimes called Service Products.

Thus Service Products are [Products](#Product) which can be booked against a [Customer](#Customer) [Profile](#Profile) without being linked to a [Reservation](#Reservation).

## Space <a href="#space" id="space"></a>

A Space is a bookable, location-based [Resource](#Resource) such as a bed, guest room, dormitory, apartment, function room, tennis court or car parking bay which can be sold on the basis of a [Reservation](#Reservation) for a specified date/time and duration. It is used in preference to the more restricted definition of 'room'.

In practice, most spaces are accommodation-based resources such as beds, guest rooms and dormitories, booked on a nightly stay basis, and some parts of the [Mews Open API](#OpenAPI-MewsOpenAPI) and some partner [Integrations](#Integration) may make that assumption.

For more information about the Mews vision for space resources, see the [Mews Devs blog post about Project Spacetime](https://developers.mews.com/project-spacetime/).

## Space Category <a href="#spacecategory" id="spacecategory"></a>

Space Category is the named category of [Space](#Space) which Mews uses when calculating [Availability](#Availability) and when distributing ARI ([Availability](#Availability), [Rates](#Rate) and [Inventory](#Inventory)) to sales [Channels](#Channel). For example, a hotel might have a Space Category of "double room", "twin room" or "single room".

Space Category is different than [Space Type](#SpaceType), which is one of the parameters used within Mews Operations to define a Space Category. [Space Type](#SpaceType) defines what the type of [Space](#Space) is, e.g. room, dorm, car parking bay.

Confusion can arise because in traditional systems Space Category is equivalent to 'room type', this has led to it naturally being referred to as 'space type', in fact within the Channel Manager API, **SpaceTypeCode** is used in this way in Inventory mappings. SpaceTypeCode actually refers to a Space Category, despite the name.

Furthermore, to avoid confusion between the terms 'category' and 'type' within the Channel Manager API, actual [Space Types](#SpaceType) (as defined in this Glossary) are referred to instead as 'space classifications'.

In summary:

* Within the Channel Manager API, the terms 'space category', 'space type' and 'space type code' all refer to Space Category
* Within the Channel Manager API, the term 'space classification' refers to [Space Type](#SpaceType)

## Space Classification <a href="#spaceclassification" id="spaceclassification"></a>

Space Classification defines what the type of [Space](#Space) is, e.g. room, dorm, car parking bay. The term is used in the Channel Manager API and is synonymous with [Space Type](#SpaceType) within Mews Operations. The Channel Manager API avoids using the term 'space type' so as not to confuse it with [Space Category](#SpaceCategory).

## Space Type <a href="#spacetype" id="spacetype"></a>

Space Type defines what the type of [Space](#Space) is, e.g. room, dorm, car parking bay. Space Type is one of the parameters used to define a given [Space Category](#SpaceCategory), and the two are different. In order to avoid confusion, within the Channel Manager API Space Type is instead referred to as 'space classification'.

## State <a href="#state" id="state"></a>

State is a general term whose meaning depends on the context. In the [Mews Open API](#OpenAPI-MewsOpenAPI) it could refer to:

* [Bill](#Bill) state, e.g. open or closed
* [Preauthorization](#Preauthorization) state, e.g. chargeable, expired, cancelled, charged
* [Task](#Task) state, e.g. open or closed
* [Payment](#Payment) item state, e.g. charged, cancelled, pending, failed, verifying

## Stay <a href="#stay" id="stay"></a>

Stay is synonymous with [Accommodation](#Accommodation) and refers to room-stay based [Services](#Service) offered by a [Property](#Property). These are the main [Services](#Service) that [Properties](#Property) offer to their [Customers](#Customer), in fact Mews automatically creates a default Stay service and you cannot delete it. Stay services are [Bookable Services](#BookableService), i.e. they can be reserved prior to a [Customer](#Customer)'s arrival.

## Stay Product <a href="#stayproduct" id="stayproduct"></a>

A [Product](#Product) is a purchasable item linked to a [Service](#Service). Although all [Products](#Product) are associated with [Services](#Service), those linked to [Stay](#Stay) [Services](#Service) are sometimes called Stay Products (or Reservation Products) and those linked to other [Services](#Service) are sometimes called [Service Products](#ServiceProduct).

Thus Stay Products are bookable [Stay](#Stay) [Products](#Product) linked to a [Reservation](#Reservation).

## Swagger <a href="#swagger" id="swagger"></a>

Swagger is the old name for the [OpenAPI](#OpenAPI-Swagger) specification.

## Task <a href="#task" id="task"></a>

Tasks are pieces of work that need to be done within the [Property](#Property). Tasks can be created within Mews Operations and allocated to [Employees](#Employee) or [Departments](#Department) to complete them. An [Employee](#Employee) logging in to Mews Operations sees their pending tasks on the Dashboard.

## Travel Agency <a href="#travelagency" id="travelagency"></a>

A Travel Agency is a special type of [Company](#Company), representing a booking agent. Like other [Companies](#Company), Mews stores the details of the Travel Agency in a [Profile](#Profile), and like other [Companies](#Company) they can be attached to a booking or [Reservation](#Reservation). This can be set up automatically using [Channel Manager](#ChannelManager) [Mapping Tables](#MappingTable).

Since Travel Agencies are a special type of [Company](#Company), within the API they may be considered as separate entities.

## User <a href="#user" id="user"></a>

A User is an [Enterprise](#Enterprise) [Employee](#Employee) who has an account on the Mews system.

## Voucher <a href="#voucher" id="voucher"></a>

A Voucher is a coupon or token that gives [Customers](#Customer) or [Companies](#Company) access to special [Rates](#Rate). A Voucher is linked to a private [Rate](#Rate), i.e. a [Rate](#Rate) that is not distributed publicly. The Voucher may be in physical form, but may simply be a unique identifying code.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mews.com/getting-started/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.