Skip to main content
After a guest pays, keep them on the hotel’s own domain instead of a generic confirmation screen. Fetch the full booking confirmation from the API and render it in your own branded page.

Prerequisites

  • A completed booking. Run the funnel through Accept a quote first, and keep the sessionId that confirmed it.
  • The Hotel Domain feature, enabled by D-EDGE.
  • The OAuth 1.0 signing setup from the Quick start.

How it works

The guest pays on a D-EDGE-hosted page, then is redirected back. With Hotel Domain enabled, that redirect lands on the hotel’s own website, so your site takes over. GET /v2/booking/{sessionId}/confirmation then returns the full confirmation: stay information, customer details, room descriptions, and the booking amounts (total, booking fees, deposit, and balance). This endpoint is for a hotel rendering its own confirmation.

Fetch the confirmation

The examples reuse the OAuth 1.0 signing setup from the Quick start. Replace {sessionId} with the session that confirmed the booking.
Render the returned fields in your own layout.

Tips

  • Treat customer data with care. The confirmation carries guest and customer details. Handle and store them in line with your privacy obligations.
  • Fetch on the redirect, do not poll. Use the post-payment redirect to your site as the trigger to fetch the confirmation, rather than calling the endpoint in a loop. The redirect is your signal that the payment went through: the confirmation body carries the booking details and amounts, not a payment result.

Get a booking confirmation

Full schema for the confirmation endpoint.

Create a booking access token

Time-limited token for the modification page.