Connector API
  • Mews Connector API
  • Getting started
  • Usage guidelines
    • Authentication
    • Requests
    • Responses
    • Environments
    • Serialization
    • Pagination
    • Best practices
  • Concepts
    • Multi-property
    • Restrictions
    • Taxation
    • Time units
  • Use cases
    • 'How to' use cases
    • Accounting
    • Customer loyalty
    • Customer management
    • Customer messaging
    • Data export
    • Device integration
    • Events
    • Guest technology
    • Housekeeping
    • Kiosk
    • Mews Payment Terminals
    • Payment automation
    • Point of sale
    • Reputation management
    • Revenue management
    • Upsell
  • API Operations
    • Common objects
    • Accounting categories
    • Accounting items
    • Accounts
    • Account notes
    • Addresses
    • Age categories
    • Availability adjustments
    • Availability blocks
    • Bills
    • Business segments
    • Cancellation policies
    • Cashiers
    • Cashier transactions
    • Commands
    • Companies
    • Companionships
    • Company contracts
    • Configuration
    • Counters
    • Countries
    • Credit cards
    • Currencies
    • Customers
    • Departments
    • Devices
    • Enterprises
    • Exchange rates
    • Exports
    • Identity documents
    • Images
    • Languages
    • Loyalty memberships
    • Loyalty programs
    • Loyalty tiers
    • Messages
    • Message threads
    • Order items
    • Orders
    • Outlet bills
    • Outlet items
    • Outlets
    • Payments
    • Payment requests
    • Preauthorizations
    • Product categories
    • Product service orders
    • Products
    • Rates
    • Rate groups
    • Reservations
    • Reservation groups
    • Resource access tokens
    • Resource blocks
    • Resources
    • Resource categories
    • Resource features
    • Restrictions
    • Routing rules
    • Rules
    • Service order notes
    • Service overbooking limits
    • Services
    • Source assignments
    • Sources
    • Tasks
    • Tax environments
    • Taxations
    • Vouchers
    • Voucher codes
  • API Events
    • Ways to communicate
    • General Webhooks
    • Integration Webhooks
    • Webhooks FAQ
    • WebSockets
  • Your integration journey
    • Certification
  • Deprecations
    • Migration guide: Get all reservations
  • Changelog
    • Changelog 2024
    • Changelog 2023
    • Changelog 2022
    • Changelog 2021
    • Changelog 2020
    • Changelog 2019
    • Changelog 2018
    • Changelog 2017
    • Changelog 2016
Powered by GitBook
On this page
  • Setup
  • Checked-in status
  • Charging checked-in customers
  • Testing your integration
  • Additional help for working with the demo environment

Was this helpful?

  1. Use cases

Guest technology

PreviousEventsNextHousekeeping

Last updated 1 month ago

Was this helpful?

Guest technology covers a range of use cases related to guest technology, especially in-room technology, such as telephones, TV and entertainment systems, room controls and internet access. A typical use case involves posting charges for in-room telephone usage.

Setup

Firstly, use to retrieve all services the property has configured in Mews. Once all services are retrieved, you can select the service against which you would like charges to be posted. To retrieve the list of configured accounting categories or accounting codes, use . This is important because a hotel may, for example, prefer to have charges for international phone calls reported with a different accounting category than for domestic phone calls.

'How to' use case

API Operations

How to get the list of property services

How to get the list of accounting categories

Checked-in status

Guest technology integrations typically require information on changes to , especially when a reservation is checked-in and checked-out. Rather than polling the API for state changes, it is better to subscribe to notification events using or . Both methods support changes to reservations. Don't know which one to use? See . Once a reservation update event is received, use the reservation ID in a request to retrieve information about the reservation and customer.

No Post: The customer classification Cashlist is used when charges cannot be sent to the customer bill. This is commonly known as ‘No Post’.

'How to' use case

API Operations

How to listen for changes to reservations

How to get reservation and customer details

Charging checked-in customers

Once the unique identifier of the customer to be charged is obtained, the items can be posted onto their billing tab using the operation. When using , specify parameter LinkedReservationId in order to link the order to a guest reservation. This will greatly assist the property when using billing automation.

'How to' use case

API Operations

How to post an order item to a guest profile

How to link an order to a reservation

Testing your integration

Additional help for working with the demo environment

Help Guides:

(ServiceOrderUpdated event) or (Reservation event)

(use LinkedReservationId)

Please ensure you follow our general for testing integrations. To confirm you are relating any product that is not configured in Mews with the correct accounting category, you can review the . If done correctly, the product you've posted will appear under the relevant accounting category in the Revenue section of the report.

Usage guidelines
Accounting Report
Understanding services
Create or delete a product
Creating an accounting category
General Webhooks
WebSockets
Webhooks
WebSockets
Ways to communicate
Get all accounting categories
Get all accounting categories
Add order
Add order
Add order
Add order
Get all reservations
reservation state
Get all reservations
Get all services
Get all services