:material-hotel: Synixis Integration¶
Connect Sabre SynXis Central Reservation System (CRS) to Dxtra for automated hospitality privacy compliance, guest reservation tracking, and travel industry data protection.
Prerequisites¶
- Dxtra account with configured Data Controller and DID
- Sabre SynXis CRS subscription with API access
- API credentials (username, key, and endpoint URL)
- Appropriate permissions for hotel property data
How It Works¶
Unlike other Dxtra integrations that use webhooks, the SynXis integration uses a polling-based approach:
- Dxtra authenticates with the SynXis API using your configured credentials
- At configured intervals, Dxtra polls the SynXis Reservations API to retrieve recent reservation data
- Reservations from the last 7 days are retrieved with full detail
- Each reservation is processed individually with privacy-preserving hash generation
- Guest data is linked to data subjects for consent and rights management
Polling Schedule
The SynXis polling is triggered via scheduled events. Contact support to configure polling intervals for your deployment.
Setup¶
Step 1: Obtain SynXis API Access¶
- Contact your Sabre SynXis account manager to request API access
- Obtain the following credentials:
- API endpoint URL
- Authentication credentials (username and key)
- Hotel property codes you need access to
Step 2: Configure Dxtra Integration¶
- Log into the Dxtra dashboard
- Navigate to Processors > Add Integration > SynXis CRS
- Enter your SynXis credentials:
- API endpoint URL
- Authentication credentials
- Property codes
- Save the configuration
Step 3: Configure Hotel Properties¶
If you manage multiple properties, specify which hotel IDs to poll:
- Single property -- Provide the hotel ID in the configuration
- Multiple properties -- Configure separate polling schedules per property or poll all properties
Step 4: Test the Integration¶
- Create a test reservation in SynXis
- Wait for the next polling cycle (or trigger manually via the dashboard)
- Check the Dxtra dashboard Activity Log for captured reservation events
- Verify guest data is being properly linked
Data Captured¶
Dxtra extracts the following data from SynXis reservations:
Reservation Data¶
| SynXis Object | Data Captured | Privacy Purpose |
|---|---|---|
Reservation | Booking details, dates, room type, rates | Service delivery and billing |
Booker Profile | Guest name, contact details | Guest identification |
Itinerary | Itinerary number, travel dates | Reservation tracking |
Payment | Billing details, payment method | Financial transaction processing |
Guest Profile Data¶
| SynXis Object | Data Captured | Privacy Purpose |
|---|---|---|
Guest Profile | Name, contact info, preferences | Guest service delivery |
Loyalty Member | Membership details, tier status | Loyalty program management |
Special Requirements | Accessibility needs, dietary restrictions | Service customization |
Data Subject Rights¶
Guest Data Redaction¶
Guests can request deletion of their reservation data:
- Dxtra records -- All stored SynXis event data for the data subject is removed
- SynXis CRS -- You must separately manage guest data in your SynXis CRS following hospitality retention requirements
Hospitality Data Retention
Hotel reservation and guest registry data is subject to specific retention requirements that vary by jurisdiction (typically 3-7 years). Financial records from hotel stays are typically retained for 7 years for tax purposes.
Data Export¶
SynXis data is included in Dxtra's standard data subject export functionality, providing guest reservation and profile information.
Security¶
- Token-based authentication -- Bearer token obtained via credential exchange for all API calls
- Encrypted credentials -- API credentials stored encrypted at rest
- Error isolation -- Individual reservation processing failures do not affect other reservations
- Immediate response -- API returns 200 OK immediately to prevent timeout issues during batch processing
Troubleshooting¶
API Connectivity Issues¶
Connection timeouts or authentication failures:
- Verify SynXis API credentials and endpoint URLs
- Check network connectivity and firewall settings
- Confirm API access permissions for required hotel properties
Data sync delays or failures:
- Check SynXis system status and maintenance schedules
- Review API rate limiting and request throttling
- Verify data format compatibility between systems
Guest Data Matching¶
- Review guest identification criteria and matching logic
- Check for variations in guest name formatting across reservations
- Use email address as primary deduplication key
- Configure loyalty program number as secondary identifier
Related Documentation¶
- Integration Overview -- All available integrations
- Eventbrite Integration -- Event management integration
- Stripe Integration -- Payment processing integration
- Data Subject Rights -- Rights request processing
For support, contact support@dxtra.ai with "SynXis" in the subject line.