Skip to main content
Prerequisites — before you start:
  • Prerequisites — before you start
  • An active Journey Rewards partner account.
  • A Maestro PMS property (cloud or on-prem) with permission to enable third-party integrations.
  • Agreement to Maestro’s partner / API access process (Maestro provides integrations via HTNG/OTA standards, vendor-specific specs, and its own Maestro API (Genomi)).

Overview

Connecting Journey Rewards to Maestro PMS lets you sync reservations and guest profiles automatically so you can recognize loyal guests and power direct-booking rewards with zero manual effort. Maestro supports integrations through partner enablement and open APIs, including HTNG/OTA standards and Maestro’s Genomi API.

Enable the integration

  1. Request partner enablement with Maestro
    Send an email to [email protected] (or use Maestro’s “Become a Partner” form) with your property details and request activation of the Journey integration.
    Include: property name(s), property code(s) (if applicable), and an authorization statement for Journey to access the data exposed via the Maestro integration.
  • Partner & Open APIs info (Maestro): phone & email and partner application options are listed on Maestro’s Interfaces & Open APIs page. maestropms.com
  1. Authorize Journey access
    In your email, request:
“Please activate the Journey loyalty rewards integration (journey.com) for [HOTEL NAME/CHAIN NAME]. We authorize the Journey team and their integration to access our data available through Maestro’s supported interfaces / APIs.”
  1. Maestro issues or confirms interface access
    Maestro will confirm next steps for enabling the interface (e.g., via HTNG/OTA spec, a vendor-specific spec, or Maestro’s Genomi API) and provide or validate any connection details required at the property level. maestropms.com
  2. Journey connects & verifies sync
    Once access is granted, Journey completes the technical connection and verifies initial data synchronization (reservations & guest profiles).
No further setup on property staff is typically required beyond confirming the integration is enabled with Maestro and that Journey is authorized to connect.

What gets synced (typical)

  • Guest profiles: name, contact info, loyalty identifiers where available
  • Reservations: create/modify/cancel events, stay dates, room type, rate/folio references
    Exact payloads and event coverage depend on the specific interface Maestro enables for your property (HTNG/OTA, vendor-specific, or Genomi API). maestropms.com

Authentication & access

  • Credentialing is handled through Maestro’s partner process. Depending on the enabled path, credentials may be per-property or per-chain and scoped to the approved interface. Maestro controls provisioning and access policies for third-party integrations. maestropms.com

Security & compliance

  • Maestro advertises an extensive integrations program and responsible disclosure practices; access must follow Maestro’s policies for API/interface usage and the hotel’s data-sharing approvals. maestropms.com

Validation & go-live

  • Maestro will confirm following credentials:
    • Server End Points URL
    • Hotel Identifier
    • Agreed Upon Key
  • Partner will confirm:
    • Server to run integration on and provide remote access
    • External firewall rule is in place and Doman Name System (DNS) has been configured
  • Journey will confirm:
    • Successful connection to the enabled Maestro interface
    • Initial reservation and guest syncs are flowing
    • Ongoing events (new bookings, modifications, cancellations, check-in/out) appear in Journey within the expected SLA for the chosen interface
If anything looks off after ~30 minutes of activation, contact Journey Support with your property details so we can investigate quickly.

Need help?

Next steps

  • Invite staff to Journey so front-desk and revenue teams can view guest loyalty profiles.
  • Configure Campaigns and Offers (e.g., bonus points for direct bookings).
  • Promote loyalty on your booking engine and in confirmation emails.