> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abrahospitality.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MEWS

> Connect ABRA to MEWS Operations Cloud

# MEWS Integration

<Tip>
  **New Integration** - MEWS is our newest PMS integration, featuring a streamlined webhook-only sync architecture.
</Tip>

ABRA integrates with MEWS Operations Cloud to provide real-time synchronization of guest and reservation data.

## What Data Syncs

The following data is automatically synchronized from MEWS to ABRA:

* **Reservations** - Booking details including confirmation number, check-in/check-out dates, and status
* **Guest Profiles** - Name, contact information, address, and preferences
* **Room Assignments** - Current room (resource) assignments and room types
* **Loyalty Program** - Membership status and tier information
* **Account Notes** - Historical notes attached to guest accounts
* **Rate Information** - Room rates broken down by date

## How Sync Works

ABRA uses real-time webhooks to stay synchronized with MEWS:

### Real-Time Webhooks

<Info>
  MEWS integration uses webhooks exclusively with no scheduled polling jobs. This is the cleanest and most efficient sync architecture.
</Info>

MEWS sends event notifications to ABRA when changes occur. These updates are processed within moments of occurring in MEWS.

**Reservation Events:**

| Event                                                                        | Description                          |
| ---------------------------------------------------------------------------- | ------------------------------------ |
| [Service Order Updated](/integrations/pms/mews/events/service-order-updated) | A reservation is created or modified |
| [Message Added](/integrations/pms/mews/events/message-added)                 | A note is added to a reservation     |
| [Payment Updated](/integrations/pms/mews/events/payment-updated)             | Payment information changes          |

**Guest Events:**

| Event                                                              | Description                    |
| ------------------------------------------------------------------ | ------------------------------ |
| [Customer Added](/integrations/pms/mews/events/customer-added)     | A new guest profile is created |
| [Customer Updated](/integrations/pms/mews/events/customer-updated) | Guest information is modified  |

**Room Events:**

| Event                                                                          | Description                        |
| ------------------------------------------------------------------------------ | ---------------------------------- |
| [Resource Updated](/integrations/pms/mews/events/resource-updated)             | Room information changes           |
| [Resource Block Updated](/integrations/pms/mews/events/resource-block-updated) | Room blocking/availability changes |

## Reservation status mapping

For a full explanation of ABRA reservation statuses (including display-only “Arrivals” and “Departures”), see [Reservation Statuses](/concepts/reservation-statuses).

MEWS calls reservations **Service Orders**. ABRA primarily updates reservation status when it receives:

* [`ServiceOrderUpdated`](/integrations/pms/mews/events/service-order-updated) (reservation created/updated)

### MEWS reservation state → ABRA status

ABRA maps the MEWS reservation `State` into ABRA’s stored status roughly as follows:

| MEWS State                            | ABRA Status   | Notes                                       |
| ------------------------------------- | ------------- | ------------------------------------------- |
| `Confirmed`                           | **Upcoming**  | Reservation exists but guest not checked in |
| `Started`                             | **In-House**  | Guest checked in                            |
| `Processed`                           | **Past**      | Guest checked out                           |
| `Canceled`                            | **Cancelled** | Reservation cancelled                       |
| `Optional` / `Requested` / `Inquired` | **Tentative** | PMS-specific “not fully confirmed” states   |

<Note>
  MEWS can emit `ServiceOrderUpdated` for non-accommodation service orders (spa/restaurant/etc.). ABRA only persists accommodation reservations.
</Note>

### Initial Setup Sync

During initial setup, ABRA imports your historical reservation data to ensure you have a complete picture from day one.

## Initial Setup

To connect ABRA to MEWS, you'll need the following from your MEWS Commander console:

* **Client Token** - Your public API identifier
* **Access Token** - Your secret API credential
* **Service ID** - Your accommodation service identifier

Your ABRA implementation team will work with your MEWS administrator to obtain these credentials and configure the connection.

## Sync Status

Once connected, you can verify data is syncing correctly by checking that recent reservations and guest updates from MEWS appear in ABRA. Contact ABRA support if you notice any discrepancies.