Notifications API

Send automated messages for booking events to simplify your operations and scale effectively

The Notifications API lets you integrate with the Rapid API more closely than ever. When booking changes occur that can impact your business or operations, the Notifications API will push details of the change directly to all affected parties. Messages can be initiated by agents, vendors, and the Rapid API itself. That means if a call center agent makes a change or a vendor cancels a booking, you'll be notified. Likewise, if the API successfully creates a new booking, you will receive a notification you can use to maintain alignment with your internal systems.

Note: In the Lodging API, we already support messages from agents, vendors, and the Rapid API. In the Car and Activities APIs, we currently support agent-initiated booking changes, and will soon support changes initiated within Rapid API and by our vendors.

The Notifications API enables a seamless integration with your business and complements other partner and customer support services. As we add features and functionality to Rapid API, we'll also add new notification event types to improve your experience.

Event schema and details

All POST notification event adhere to the schema outlined below. As new event types are added for different events the schema may vary.

Object	Description
`event_id`	Unique identifier for each event.
`event_type`	An indication of what event caused the notification. This value can be used for message handling and routing. Refer to the list of event types for more information.
`event_time`	Timestamp of the event notification given in UTC.
`itinerary_id`	The Itinerary ID of the affected booking.
`email`	The customer email address associated with the affected itinerary.
`message`	Information about the notification event. For events of type `itinerary.message.received`, this will contain the actual text of the vendor message. In all other event types, this will be a static human friendly description of the event in English.
`affiliate_reference_id`	The Affiliate Reference ID of the affected booking.
`topic_tags`	The topic tags of the event. These will only be provided on events of type `itinerary.message.received`. This will be a list of tags that our analysis has determined might be present in the text of the message. >> Learn more about property message tags
`line_of_business`	The line of business the event falls into. Possible values: `cars`, `flights`, `activities`, and `packages` (`properties` is coming soon). This field does not apply to all event types. Note: This field is currently available for Rapid Car, Flight, and Activities APIs; the Rapid Lodging API has not yet incorporated it.

Each notification is an HTTPS POST request with a JSON message body.

Note: You’ll need to be enabled for each event type individually to be able to receive those kinds of notifications. If you would like to enable a new Notifications event type, please reach out to support.

Supported event types

The Rapid Notifications service provides proactive messages for the following events. Supported events differ between Rapid lines of business.

Lodging API

Supported events for the Lodging API

The Rapid Lodging API supports all of the following events:

event_type value	Source	Event	Details
`itinerary.agent.create`	Customer support agent or Affiliate Voyager	Booking creation	A new booking was created by a Rapid customer support agent or Affiliate Voyager.
`itinerary.agent.change`	Customer support agent or Affiliate Voyager	Booking update	An existing booking was updated by a Rapid customer support agent or Affiliate Voyager.
`itinerary.agent.cancel`	Customer support agent or Affiliate Voyager	Booking cancellation	An existing booking was canceled by a Rapid customer support agent or Affiliate Voyager.
`itinerary.api.create`	Rapid API	Itinerary created via API	A Rapid API call successfully created a new booking. Note: Originating calls via the API helps you maintain a single source of truth across systems to reduce issues like “ghost bookings.”
`itinerary.api.create_failed`	Rapid API	Itinerary creation via AP failed	A Rapid API attempt to create a booking definitively failed.
`itinerary.api.change`	Rapid API	Itinerary update via API	A Rapid API call changed an existing booking——either a hard change (such as room, dates, payment) or a soft change (like guest details).
`itinerary.api.cancel`	Rapid API	Itinerary cancelled via API	A Rapid API call cancelled the booking.
`itinerary.fraud.cancel`	Expedia	Booking cancellation	An existing booking was canceled by Expedia because the booking did not comply with the terms and/or conditions applicable to the transaction. The customer will need to contact transactionprocessing@travelscape.com with their telephone number and the best time to discuss the cancellation.
`itinerary.message.received`	Property	New Property Message Center message	The property has sent a new message via the Property Message Center (PMC). This event will contain the full property message text as well as the general topic(s) of the message. In addition to notification, messages will also be accessible via email and the PMC tool. Please note: You need to be integrated with Property Message Center to receive these kinds of notifications. >> Learn more about the Property Message Center
`itinerary.payment_verification.failure`	Property	Credit card payment change link	The payment card provided by the traveler at time of booking has been marked as invalid by Expedia after pre-authorization. >> Learn more about the Credit Card Recapture feature
`itinerary.supplier.cancel`	Property	Booking cancellation	An existing booking was canceled by the property. The customer should contact your business' customer support.
`itinerary.supplier.confirm`	Property	Booking update	The property has updated the property confirmation ID for the booking.
`itinerary.supplier.change`	Property	Booking update	An existing booking is changed by the property due to delayed arrival or early check out by the traveler.
`itinerary.supplier.refund`	Property	Booking update	For Expedia Collect bookings, property is providing traveler requested refunds. It is the duty of partner to ensure traveler receives the refunds.
`itinerary.traveler.noshow`	Property	Traveler no show	The traveler didn't show up; hence, the property marked the booking as No show.
`itinerary.traveler.checked_in`	Property	Traveler checks in at property	The traveler checked in at the property, as recorded by the supplier.
`itinerary.unspecified.cancel`	Expedia	Booking cancelled by an unspecified party	This notification is sent when a booking is cancelled but the system is unable to identify whether the cancellation was initiated by the traveler, the property/host, or an agent. It is primarily used for Vrbo bookings on Rapid API where the cancelling party cannot be determined, as well as for flight itinerary cancellations where the party is unknown. Because the source of the cancellation is indeterminate, partners cannot distinguish who initiated the cancellation from the notification alone.
`itinerary.unspecified.change`	Expedia	Booking changed by an unspecified party	This notification is sent when an existing booking is changed (a "hard change") but the system cannot identify whether the change was initiated by the traveler, the property/host, or an agent. It is primarily used for Vrbo bookings on Rapid API. Upon receiving this notification, partners should perform a Booking Retrieve call to determine what was changed and see the updated booking details.
`itinerary.message.received`	Property	New message sent	The property has sent a new message via either Property Message Center (PMC) or Conversation API.
`itinerary.message.rejected`	Demand partner / Traveler	Fraud or phishing detected	A message sent by a traveler or demand partner agent is suppressed because it is identified as fraudulent or phishing in nature. The message is blocked and not delivered.
`itinerary.conversation.attachment.success`	Demand partner / Traveler	Attachment upload successful	An attachment sent by a traveler or demand partner agent as part of a conversation has been successfully uploaded and added to the conversation.
`itinerary.conversation.attachment.failure`	Demand partner / Traveler	Attachment upload failed	An attachment sent by a traveler or demand partner agent as part of a conversation was uploaded to the S3 Bucket, but failed to upload to the conversation.

Example for itinerary.agent.create

{
     "event_id": "dbacce6c-afcb-4b23-ae66-48050757551c",
     "event_type": "itinerary.agent.create",
     "event_time": "2026-08-09T16:47:32.039Z",
     "itinerary_id": "8091234567890",
     "email": "customer@example.com",
     "message": "An agent created a new itinerary.",
     "affiliate_reference_id": "b086d299-2f1f-4134-a23c-f4a1c9286fac"
 }

Example for itinerary.supplier.confirm

{
    "event_id": "e02d6f41-4708-476f-915d-8a7032942e94",
    "event_type": "itinerary.supplier.confirm",
    "event_time": "2027-04-28T20:31:03.423Z",
    "itinerary_id": "8999989898988",
    "email": "alice@example.com",
    "message": "The supplier confirmed one or more rooms on this itinerary.",
    "affiliate_reference_id": "R194193582",
    "rooms": [
        {
            "confirmation_id": {
                "expedia": "926784314",
                "property": "BEF23123AA"
            }
        },
        {
            "confirmation_id": {
                "expedia": "926784315"
            }
        }
    ]
}

Example for itinerary.message.received

{
  "event_id": "1aed5641-7285-4c42-b079-f5f2f139d148",
  "event_type": "itinerary.message.received",
  "event_time": "2027-11-14T02:33:18.860105363Z",
  "itinerary_id": "9025254271673",
  "email": "john@email.com",
  "message": " We accept your request for a river view room. You will be able to check in at 11:00 AM. Please also note that the pool will be closed for scheduled maintenance on the day of your arrival, it will be open normal hours (9 AM to 10 PM) for the remainder of your stay. Looking forward to your visit.",
  "topic_tags": "Check-in, Property/Amenity Closure",
  "affiliate_reference_id": "b086d299-2f1f-4134-a23c-f4a1c9286fac"
}

Car API

Supported events for the Car API

At this time, the Rapid Car API only supports one notification event, a booking cancellation. Additional events are in the process of being added. We'll list them here when they're available.

event_type value	Source	Event	Details
`itinerary.agent.cancel`	Customer support agent or Affiliate Voyager	Booking cancellation	An existing booking was canceled by a Rapid customer support agent or Affiliate Voyager.

Activities API

Supported events for the Activities API

At this time, the Rapid Activities API supports two notification events. Additional events are in the process of being added. We'll list them here when they're available.

event_type value	Source	Event	Details
`itinerary.agent.cancel`	Customer support agent or Affiliate Voyager	Booking cancellation	An existing booking was canceled by a Rapid customer support agent or Affiliate Voyager.
`itinerary.supplier.cancel`	Supplier	Booking cancellation	An existing booking was canceled by the supplier. The customer should contact your business' customer support.

API details

Explore the notification-related endpoint definitions on this page, then use the API Explorer or another testing software to get an understanding of how the examples and schema definitions compare to the actual output. We also have a Notification Tester that you can use to test your integration with our Notifications API.