Conversation API Launch Requirements

For additional technical information, please refer to the Developer Hub documentation.

To ensure a successful implementation and launch, partners must comply with the following launch requirements.

1. Two-Way Communication Capability

Partners must support two-way communication and ensure messages can be both received and responded to through their implementation.

Required Evidence:

• High-level overview of the communication workflow.
• Screenshots demonstrating the user experience for both message receipt and message response functionality.

2. Notifications API Adoption

Partners must implement and actively monitor the Notifications API associated with the Conversation API.

Required Evidence:

• Confirmation of Notification API implementation.
• The test and production endpoints that should be registered for notifications.

3. Message Attribution and Transparency

When a partner representative communicates through Conversation API on behalf of a traveler, the partner must clearly disclose that the communication is being sent by an agent acting on the traveler's behalf.

Example Disclosure:

"This message is being sent by [Partner Name] agent on behalf of the traveler."

“This message is being sent by agent on behalf of the traveler."

Required Evidence:

• Screenshot of the messaging experience demonstrating the required disclosure.

4. Message Integrity Requirements

Partners are strictly prohibited from modifying, altering, truncating, reformatting, repurposing, or otherwise changing the content of messages exchanged through the Conversation API.

All message content must be displayed and transmitted exactly as received.

This requirement aligns with Expedia Group contractual obligations, data privacy standards, and communication policies.

Required Evidence:

• Written acknowledgment of compliance.

5. 24/7 Operational Monitoring (Agent Model Only)

Partners operating under the Agent Model must maintain a monitored communication channel and an operational process to review and respond to supplier and traveler communications on a continuous basis.

Partners are responsible for facilitating communication between travelers and suppliers and ensuring messages, requests, and inquiries are handled in a timely manner, as communication between travelers and suppliers may be critical on day of check-in and during the trip.

Required Evidence:

• Written acknowledgment of the operational support model.
• Confirmation of the process used to monitor and manage conversations.

Required Launch Sign-Off

To proceed with launch approval, please provide the required evidence outlined above and confirm your acknowledgment of all 5 API Launch Requirements.

Once the requested information has been reviewed and approved via the Integration Ticket, the Launch Management team will provide guidance on the remaining launch activities and next steps toward production readiness.