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 (contact your Journey CSM if needed).
  • WebRezPro admin access (or someone at your property who can submit support tickets / authorize integrations).
  • Property identifiers handy (your WebRezPro account/company reference ID, property name(s), and time zone per property).
WebRezPro notes the best way to contact Support is by creating a support ticket from within your system.

​
Overview

Connecting Journey Rewards to WebRezPro enables Journey to:
  • Sync reservations (created/updated/cancelled, arrival/departure, status, rate, etc.)
  • Sync guest profile fields (name, email, phone where available)
  • Support loyalty recognition and rewards tied to stays (including BAR rate) and eligible add-on services
WebRezPro highlights a large integration partner ecosystem (150+ integrations) and describes third-party integrations accessing property data through the API when a property enables/installs the integration.

​
Option A (preferred): Submit a Support Ticket inside WebRezPro

Create a WebRezPro support ticket (inside your WebRezPro system) requesting that API access / integration credentials be enabled for Journey Rewards. WebRezPro explicitly directs customers to use in-system support tickets to contact Support.

​
Option B: Contact WebRezPro via their Contact page

If you can’t access the in-system ticketing, use WebRezPro’s published contact channels (phone numbers listed on their Contact page). What to ask WebRezPro for (in the ticket/email):
  1. Confirmation that your property is approved for third-party integration via API
  2. Your company/account reference identifier (often required by integrators)
  3. The required API credentials (API key / secret or other auth)
  4. Whether webhooks are available/enabled for reservations/guests updates
  5. Any rate limits and recommended polling cadence
WebRezPro’s Data Management Policies indicate that when a property adds an integration (via API), the third party may access and use information provided by the property.

​
Step 2 — Provide required details to Journey

Once WebRezPro confirms/returns credentials, share the following with Journey using this secure form:

​
A) Authentication details

  • API key / secret (or auth method WebRezPro specifies)
  • Account/company reference ID
  • Base URL / environment (prod and sandbox if offered)

​
B) Property mapping

  • Property name(s) and unique IDs
  • Time zone per property
  • Currency
  • Rate plan mapping (identify how BAR is represented in WebRezPro)

​
C) Data scope confirmation

At minimum, Journey needs the ability to retrieve:
  • Reservations: confirmation number, status, arrival/departure, booked date, rate (amount + currency), room/unit, channel/source (if available)
  • Guests: first/last name, email (critical), phone (if available)
Many WebRezPro integrations rely on webhooks for near real-time updates because WebRezPro can be “heavily restricted” on rate limits (making frequent polling unreliable). Recommended approach
  • Use webhooks for: reservation created/updated/cancelled, guest profile updated
  • Use periodic polling as a backstop (e.g., nightly reconciliation)
If WebRezPro does not enable webhooks for your account, Journey will configure conservative polling based on WebRezPro’s stated limits.

​
Step 4 — Validation checklist (go-live readiness)

Journey will validate (with your help) that:
  1. New reservations appear in Journey within expected timing (webhook/polling)
  2. Modifications + cancellations update correctly
  3. Guest matching works (email normalization, duplicates)
  4. Rate fields align with expectations (BAR and total amounts)
  5. Stay lifecycle events (check-in/out if available) behave correctly

​
Security & compliance considerations

WebRezPro describes security practices and data protection focus (e.g., PCI/EMV, best practices). This is relevant when approving access to guest/booking data.
Also note WebRezPro indicates PMS/reservation data is stored/processed on AWS and provides policy references. Best practices for the integration
  • Least-privilege credentials (read-only where possible)
  • Credential rotation process
  • Audit trail access (if WebRezPro provides it)
  • PII minimization (only required fields)

​
Troubleshooting

If data isn’t syncing correctly, gather:
  • WebRezPro account/company reference ID
  • A few reservation confirmation numbers
  • Affected timestamps (booking created/updated)
  • Any error payloads/logs from the integration
Then contact Journey Support: support@journey.com
(Include the property reference ID and example reservation IDs.)

​
Next steps after connection

  • Invite front desk / reservations staff to Journey to view member profiles
  • Configure campaigns/offers (bonus points, direct booking promotions)
  • Add loyalty messaging to booking flow and confirmation emails