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 need help, contact your Journey CSM. - Seven Suite Front Desk (PMS) access
You’ll need an admin/owner user who can authorize integrations. - Connectivity basics
- Seven Suite is cloud-based (access from any device with internet), so Journey will connect server-to-server.
- Confirm you have the correct property/tenant identifiers inside Seven Suite (hotel(s), room types, rate plans, etc.).
Overview
Connecting Journey Rewards to Seven Suite lets Journey:- Identify Journey members at booking / pre-arrival
- Sync reservations (including rate + stay dates)
- Sync basic guest profile information to support recognition and rewards
Step 1 — Request Seven Suite API / Integration access
Because Seven Suite does not provide a public “create API key” flow on their front-desk page, the recommended path is to request integration enablement directly from their team. Email Seven Suite:- Send to: ventas@mysevensuite.com
- CC: alliance@journey.com
- (Optional) Include your Journey CSM on the thread.
- Subject: Request to enable Journey Rewards integration (API access)
- Body:
- Hotel / group name
- Seven Suite tenant / property identifier(s)
- Confirmation you authorize Journey Rewards to access reservation + guest profile data for loyalty/rewards purposes
- Request for:
- API credentials (or OAuth client, if applicable)
- Base URL / environment (prod + sandbox if available)
- API documentation (endpoints, auth method, rate limits)
- Webhook support (reservation created/updated/cancelled; check-in/out) if available
- IP allowlisting requirements (if they restrict inbound API traffic)
Step 2 — Provide required details to Journey
Once Seven Suite confirms what they support (API keys / OAuth / webhooks), share the following with Journey using this secure form:A) Credentials / Access
- Auth type (API key, OAuth, basic auth, etc.)
- Credential(s) (key/secret/token) and expiration behavior
- Base URL(s) for production (and sandbox if available)
B) Property Mapping
- Property / hotel ID(s) in Seven Suite
- Time zone per property
- Room types + rate plans mapping (if exposed)
- “BAR” rate identification logic (how Seven Suite labels Best Available Rate)
C) Data Scope
At minimum, Journey needs:- Reservation: confirmation number, status, arrival/departure, booked date, rate amount + currency, room type, channel/source
- Guest profile: first/last name, email, phone (if available), address/country (optional)
- Stay events (ideal): check-in and check-out timestamps
If Seven Suite supports webhooks, they are strongly preferred for real-time updates; otherwise Journey will fall back to scheduled polling.
Step 3 — Security & compliance recommendations (important)
Ask Seven Suite to implement (or confirm):- Least-privilege access (read-only where possible)
- Credential rotation policy (how to rotate without downtime)
- Audit logs (access + change history) if available
- PII handling: confirm what data fields are exposed and any redaction options
Step 4 — Validate the integration (Journey + property)
After Journey receives credentials, typical validation includes:- Pull a small set of reservations (last 7–30 days)
- Verify guest profile matching (email normalization, duplicates)
- Confirm rate + currency + taxes/fees behavior
- Validate updates (modifications, cancellations)
- Confirm any “BAR” logic for stay redemptions
Troubleshooting
If syncing appears incorrect, collect:- Property ID / tenant ID
- Example reservation confirmation numbers (1–3)
- Approx. timestamps of booking changes
- Any error messages returned by Seven Suite API
Next steps (post-connection)
- Invite front desk and revenue teams into Journey to view loyalty profiles
- Configure Campaigns and Offers (bonus points for direct bookings, etc.)
- Add loyalty messaging to booking engine + confirmation emails