Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.journey.com/llms.txt

Use this file to discover all available pages before exploring further.

Prerequisites — before you start:
  • Active Journey Rewards partner account
    If you’re not set up yet, contact your Journey CSM.
  • Admin Access to Mews Operations
    You need permissions to add integrations and generate tokens.
  • Technical readiness
    A developer or engineering resource who can work with APIs/webhooks.

​
Overview

Connecting Journey Rewards to Mews gives you automatic access to:
  • Reservation data – confirmations, status, dates, rates, etc.
  • Guest profiles – name, email, phone (where available).
  • Real-time event updates using webhooks where supported.
This enables Journey to:
  • Recognize loyalty members at booking/reception,
  • Power loyalty offers/points tied to stays (including BAR),
  • Reduce manual data entry and errors.
Mews’s open API is designed to support reservations, profile sync, payments, POS, CRM integrations and more.

​
Step 1 — Request API Credentials from Mews

Mews doesn’t have a self-serve API key generator from the PMS dashboard; credentials are issued via their developer/partner process. The two things you’ll need:
  • ClientToken – identifies your application.
  • AccessToken(s) – identifies the property (or portfolio) you’re connecting to.
Email Mews Partner Support: Suggested request text:
Please enable the Mews Open API integration for our property [PROPERTY NAME] and provide us with the production ClientToken_ and AccessToken. We authorize Journey Rewards (journey.com) to access reservation, guest profile, and stay data for loyalty purposes._
Be clear whether you need:
  • Demo credentials (for initial testing),
  • Production credentials,
  • Webhook support (for event-driven updates),
  • Multi-property/enterprise access if applicable.
Mews issues separate tokens per environment (demo and production).

​
Step 2 — Provide Mews Credentials to Journey

Once Mews issues:
  • ClientToken
  • AccessToken(s)
  • API Endpoint information
Share the credentials with Journey using this secure form. Also provide:
  • Property unique identifier(s) in Mews,
  • Time zone and currency per property,
  • Rate plan mappings (to support BAR and other loyalty paybacks).

​
Authentication & Environments

Mews uses token based authentication:
  • ClientToken — identifies your application.
  • AccessToken — identifies the property/enterprise you are connecting to.
  • Client — a string naming your integration.
Requests send these tokens in the request body or headers per Mews guidelines. Mews supports:
  • Demo/Test environments — for initial development and verification.
  • Production environments — after approval/certification.
Each environment requires separate tokens.

​
Step 3 — Integration Method

​
A) Webhooks (Preferred for Real-Time Sync)

Where possible, register webhook endpoints in Mews for reservation/guest updates:
  • Reservation created
  • Reservation updated
  • Reservation canceled
  • Guest profile updated
Webhooks ensure Journey gets updates instantly without frequent polling.

​
B) API Polling

If webhooks are not available:
  • Periodically fetch reservations/guest profiles via the Connector API.
  • Use the most recent timestamps or incremental sync where supported.

​
Step 4 — Validation & Testing

Before going live:
  1. Verify authentication with a test API call (e.g., configuration endpoint).
  2. Pull a sample of past reservations and match with expected fields.
  3. Test guest profile sync (email matching, duplicates).
  4. Confirm rate fields and stay dates meet loyalty requirements.
  5. Test event flows via webhooks (if supported).
  6. Ensure BAR identification logic is consistent.

​
Data Scope & Requirements

Journey typically needs:
  • Reservations: reservation ID, status, arrival/departure, total rate + BAR rate, currency, source/channel.
  • Guest Profiles: first/last name, email, phone (if available).
  • Company/Group info (if applicable).
  • Stay lifecycle events (check-in/out if available via API/webhook).
For richer loyalty capabilities, additional fields like spend, payment info, and add-ons can be useful but are optional.

​
Troubleshooting

If data isn’t syncing or errors occur:
  • Check the provided ClientToken/AccessToken and environment.
  • Provide sample request/response logs to Journey Support.
  • Confirm property time zone + currency settings.
  • Check webhook delivery and retry backoff logic.
Contact Journey Support: support@journey.com
Include property name, Mews tenant ID, and example reservation IDs.

​
Post-Connection Next Steps

Once connected:
  • Invite teams into Journey to see loyalty profiles at check-in and booking.
  • Configure campaigns and offers (e.g., bonus points for direct bookings).
  • Add loyalty messaging to your booking engine and confirmation emails.
  • Monitor sync health and regularly audit field mappings.

​
Additional Notes

  • Mews’s API platform is well-documented and supports multiple use cases (Connector, Channel Manager, Booking Engine) — you should use the Connector API for PMS data sync.
  • Mews supports multi-property access via portfolio tokens, simplifying integration at scale.
Need help? If the integration fails to connect or data isn’t syncing after 30 minutes, contact Journey Support support@journey.com with your property code and Access Token reference.