Mews Integration

TripRescue integrates directly with Mews, a leading Property Management System (PMS), to provide a seamless experience for hotels and guests.

Supported Use Cases

  • Reservation Retrieval: Securely fetch active reservations from Mews.

  • Ownership Validation: Confirm that a user is the rightful owner of a reservation before listing.

  • Transfer Orchestration: Handle the end-to-end flow of transferring a reservation to a new guest.

  • Customer Sync: Link TripRescue accounts with Mews customer profiles for accuracy.

Benefits for Hotels

  • Reduce chargebacks and cancellations.

  • Recover revenue from non-refundable bookings.

  • Provide a trusted alternative to grey-market resales.

We integrate only with the documented, supported Mews APIs and follow their best practices for certification and compliance.

Endpoints we use

We call a minimal set of Mews Connector API endpoints. No request/response bodies, tokens, headers, or internal code are disclosed below.

Endpoint (Connector API v1)
Method
Purpose (one line)

/api/connector/v1/reservations/getAll

POST

Look up reservation(s) to validate eligibility and status.

/api/connector/v1/customers/getAll

POST

Retrieve customer info for ownership/identity checks.

/api/connector/v1/customers/add

POST

Create a customer profile if the buyer doesn't exist yet.

/api/connector/v1/services/getAll

POST

Fetch basic property/service context tied to a reservation.

/api/connector/v1/reservations/addCompanion

POST

Add buyer as companion prior to ownership transfer when required.

/api/connector/v1/reservations/deleteCompanion

POST

Clean up companions during/after transfer when needed.

/api/connector/v1/reservations/updateCustomer

POST

Perform the ownership transfer to the new guest.

/api/connector/v1/bills/getAll

POST

Retrieve bills linked to a customer/reservation for handover checks.

/api/connector/v1/bills/update

POST

Reassign bill ownership to align with the transferred reservation.

Notes (kept high-level):

  • We use on-demand, event-driven calls tied to user actions and hotel approval (no high-frequency polling).

  • We apply least-privilege scopes and only the fields required for each step.

  • We follow Mews' certification guidance for rate limiting and request filtering.

Last updated