The Booking.com app was one of OpenAI’s seven initial ChatGPT app partners. It is intended to bring accommodation discovery into a conversation, while account connection, booking completion, regional inventory and provider terms remain controlled by Booking.com and the current ChatGPT listing.
Key takeaways
- OpenAI identified Booking.com as an initial app partner in October 2025.
- Travel results are discovery inputs and should be rechecked on the provider site.
- Prices, taxes, availability, cancellation and loyalty treatment can change.
What does the Booking.com app do in ChatGPT?
Interactive travel app named by OpenAI as a launch partner for discovering accommodation options from a ChatGPT conversation. The app extends a conversation with provider data or an interactive provider experience. It does not give ChatGPT broader access than the connected account, approved workspace controls and permissions allow.
Which capabilities are documented?
- Use conversational destination, date and accommodation criteria for discovery.
- Surface supported Booking.com options in the ChatGPT experience.
- Refine travel requirements across a conversation.
- Continue into Booking.com for current details and any transaction flow.
Capabilities are not a promise that every account can use every action. OpenAI says app availability varies by plan, region, workspace, role, model and interface. Provider subscriptions and administrator settings can add further restrictions.
What is a useful first task?
Search for three refundable properties in a named city for fixed dates, with a maximum total budget and accessibility requirement. Open each Booking.com result and verify the final price, taxes, room type, accessibility details and cancellation deadline before deciding.
Start with a narrow, reversible request. Confirm the account and source selected by the app, inspect citations or previews, and require a separate approval before any supported action changes external data.
What data can move between ChatGPT and Booking.com?
The app can receive destination, dates, party details, preferences and relevant conversation context. If an account is connected, provider-side personalization or loyalty context may apply according to the live authorization. Booking and payment information should be reviewed in the provider flow.
OpenAI’s general guidance says an enabled app may receive relevant conversation context, and can also receive basic connection information such as IP-derived approximate location, browser or device type, language and region. Exact handling remains subject to both OpenAI’s controls and the provider’s terms.
What should you review before connecting it?
- Whether traveler names, children’s ages, accessibility needs or loyalty data are required.
- Total price including taxes, fees and currency conversion.
- Cancellation, payment and property terms on the live Booking.com page.
Use the least-privileged provider account that still supports the task. Workspace approval and personal authorization are separate controls; installing a plugin does not bypass the underlying app’s account permissions.
What are the main limitations?
- OpenAI’s launch announcement does not enumerate every current action.
- Inventory and price can change between the chat result and provider checkout.
- Availability depends on region, plan and current directory or plugin listing.
This is a documented profile, not a hands-on Anavem test. Product behavior, action support and regional availability can change after the verification date. Check the live connection screen before relying on the app for operational work.
How do you disconnect it?
Open Settings > Plugins, open the relevant plugin or app, find Connected accounts or Connection, and choose Disconnect. Disconnecting stops future access through that account, but it does not automatically delete existing conversations, saved files, memories or a separate administrator-managed source. Review those stores independently.