Come to Paris is an online travel agency (OTA) for Paris, trading since 1999 and selling Seine cruises, cabaret shows such as Moulin Rouge, museum and monument admissions, Disneyland Paris passes and Loire Valley and Normandy day trips, in nine languages including Mandarin and Russian and priced in euros, US dollars and sterling. For operators, it brings inbound leisure visitors from Europe, the Americas and Asia planning a Paris stay, plus groups of more than ten and gift card buyers, with cruises, shows and museum tickets selling most.

Connecting Come to Paris to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Come to Paris, visit cometoparis.com.

Primary website	cometoparis.com
Tags	Cultural & Museum Tickets
Destination markets	🇫🇷 France
Source markets	🌎 Global
Specialties	Paris cruises, cabaret shows and museum tickets
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Ventrata Booked Suppliers (last 12 months)	5+
Developed by	Come to Paris (using Ventrata's OCTO API)

This reseller connection lets you sell your products through Come to Paris without managing availability, pricing and bookings by hand. Features of this connection include:

Availability Sync – Come to Paris checks your live availability in Ventrata.
Pricing Sync – Come to Paris gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Come to Paris are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the Come to Paris Connection

🔐 Required Role Permissions: See Connections, Modify Connections, See Connection Key

Before you begin:

You must have a commercial agreement with Come to Paris for them to sell your products. To inquire about partnering with them, contact them via cometoparis.com.
You must have Come to Paris created as a Reseller in Ventrata with their pricing (retail, wholesale/commission) defined correctly. Note that this API connection requires that the reseller is set to the "Bill to my account" settlement method.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Come to Paris from the list of partners.
Select Come to Paris Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's configuration like pricing, allowed destinations, products, etc.
(Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Come to Paris connections and would like to differentiate between them more easily in the future.
Press the Create Octo Connection button.

📗 TIP

If needed, you can also allow or disallow products or destinations on the connection level, in addition to what you have configured on the reseller.

Mapping Products to Come to Paris

Securely share the OCTO API key shown on the connection you've created with your Come to Paris contact and ask them to map your products using Ventrata's OCTO API, with pricing (octo/pricing) enabled. Typically, it takes no longer than a few business days for the Come to Paris team to complete this.

Your Ventrata configuration is complete. You do not need to take any further steps.

📗 TIP

Come to Paris can access all products enabled on the connection, but you can also provide the Product and Option IDs from the connection page when contacting them to specify what to map.

Managing the Come to Paris Connection

Allow or disallow products: limit which destinations, products and options Come to Paris can access. See how to allow or disallow products.
Rename the connection to tell several Come to Paris connections apart.

Connection Features Detailed

This section is for anyone who wants to know exactly how the Come to Paris connection works: which Ventrata OCTO API calls Come to Paris makes, when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

In short: Come to Paris pulls everything it needs from Ventrata. It reads your products, checks your availability and prices, and sends bookings and cancellations. Ventrata doesn't push changes to Come to Paris, so anything you change in Ventrata reaches Come to Paris the next time it checks.

Timings are typical for Come to Paris and rounded, and they can change if Come to Paris changes how it syncs.

Product Mapping	❌	You can't map products from Ventrata. Come to Paris maps them on its side, through your account manager or Come to Paris's portal. This works as follows: Get Products (`GET /products`) – when Come to Paris sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child). Get Product (`GET /products/{productId}`) – Come to Paris re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Come to Paris's side – Come to Paris links each Ventrata option and unit to its own listing and ticket types. Your Come to Paris account manager does this for you, or you do it in Come to Paris's own portal if Come to Paris offers one. You only share the connection's API key. Typically with Come to Paris: Come to Paris reads your full product list about every 12 hours. What this means for you: Come to Paris can only sell what it has mapped. When you add a product, option or unit in Ventrata, Come to Paris may see it on its next refresh, but it won't sell it until it's mapped. So tell your Come to Paris account manager whenever you add one.
Content Sync	✅ / ❌	Come to Paris can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Come to Paris adds it to the `Octo-Capabilities` header, Get Products (`GET /products`) and Get Product (`GET /products/{productId}`) also return your product content, such as descriptions, highlights, inclusions and images. Content changes in Ventrata reach Come to Paris on its next product refresh. Typically with Come to Paris: Come to Paris requests `octo/content`.
Availability Sync	✅	Come to Paris checks your live availability in Ventrata. Ventrata doesn't push availability changes to Come to Paris. This works as follows: Availability Check (`POST /availability`) – Come to Paris sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (`AVAILABLE`, `LIMITED`, `SOLD_OUT`, `CLOSED` or `FREESALE`), the remaining vacancies, the booking cutoff and an `availabilityId`, which Come to Paris needs to book that slot. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Come to Paris can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Come to Paris: Availability Check: Come to Paris checks your products throughout the day and re-checks the same product and dates about every 5 hours. Checks are busiest between 00:00 and 06:00 UTC, which suggests most checks are live, as customers browse Come to Paris. What this means for you: when you close a date, change capacity or sell out in Ventrata, Come to Paris shows it after its next check. For dates it checks regularly, that's within about 5 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once Come to Paris asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Come to Paris asks for prices by adding `octo/pricing` to the `Octo-Capabilities` header of its requests. Without it, Ventrata sends availability with no prices at all. Availability Check (`POST /availability`) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Come to Paris, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Come to Paris also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing. Booking Reservation (`POST /bookings`) and Booking Confirmation (`POST /bookings/{uuid}/confirm`) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at. Typically with Come to Paris: Come to Paris requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Come to Paris doesn't send the number of people per unit type, so prices come back per person, and group pricing such as Booking Size fares may not show correctly on Come to Paris. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Come to Paris to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Come to Paris's portal. Otherwise it may be off, and Come to Paris won't receive your Ventrata prices. 📗 TIP – If prices on Come to Paris look wrong, check the Come to Paris reseller's pricing in Ventrata first: that's what Come to Paris reads.
Promotions Sync	✅ / ❌	Your Ventrata promotions can apply to Come to Paris prices and bookings. This works as follows: `octo/offers` capability – with it, Ventrata applies your eligible promotions to availability prices and to bookings, and Come to Paris can also send a promo code (`offerCode`). Promotions work together with pricing, so they need `octo/pricing` as well. This covers promotions you create in Ventrata (supplier-initiated promotions). Typically with Come to Paris: Come to Paris requests `octo/offers`.
Bookings Sync	✅	Bookings and cancellations made on Come to Paris are created in Ventrata instantly, and customers get Ventrata tickets. This works as follows: Hold: Booking Reservation (`POST /bookings`) – when a customer starts checkout on Come to Paris, Come to Paris sends the product, option, chosen slot (`availabilityId`) and one unit item per person. Ventrata checks capacity again and creates an `ON_HOLD` booking, which holds the places while the customer pays. If there's no longer room, Ventrata rejects the hold. Confirm: Booking Confirmation (`POST /bookings/{uuid}/confirm`) – once payment goes through, Come to Paris confirms the hold, with its own booking reference and the customer's contact details. The booking becomes `CONFIRMED` in Ventrata, and Ventrata sends back your booking reference and the tickets (one per person) or a voucher (one per booking), depending on how your product is set up, each with a QR code and a PDF link. Come to Paris gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Come to Paris never confirms, and the hold expires on its own and frees the places. Cancel: Booking Cancellation (`POST /bookings/{uuid}/cancel`) – when a customer cancels on Come to Paris, Come to Paris cancels the booking in Ventrata. Ventrata accepts this only if the booking can still be cancelled and the option's cancellation cutoff hasn't passed. Otherwise it rejects the request, and Come to Paris has to contact you. Change: Come to Paris doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Come to Paris: Come to Paris doesn't set a hold time, so the default hold time applies. A typical Come to Paris booking is for about 2 people. It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire. Come to Paris also checks the bookings it has made, with Get Booking (`GET /bookings/{uuid}`) about once a day, for example to reconcile its records. ‼️ IMPORTANT – Bookings sync one way, from Come to Paris to Ventrata. If you cancel, change or rebook a booking from Come to Paris in Ventrata, for example in the Dashboard, Come to Paris isn't notified. Contact Come to Paris so the booking is cancelled or changed on their side too, or ask the customer to cancel through Come to Paris.
Pickups/Dropoff Sync	❌	Come to Paris doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Come to Paris how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Come to Paris doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Come to Paris how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Come to Paris. Customers can only book your main products and options on Come to Paris. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Come to Paris. Ventrata doesn't notify Come to Paris when a ticket is scanned or redeemed. Come to Paris only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Come to Paris pass holders can't be scanned at your entrance without a booking. Customers from Come to Paris need a booking made through Come to Paris before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Come to Paris. Gift cards bought in Ventrata can't be used on Come to Paris, and Come to Paris can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Come to Paris connection

Delays: availability and prices reach Come to Paris only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Come to Paris can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Come to Paris can see: only the destinations, products and options allowed on the reseller and the connection, and enabled for sale on the Direct API source. See how to allow or disallow products.
Tickets: Come to Paris issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Come to Paris can send test bookings while it sets up the connection. Test bookings don't use your availability and aren't invoiced.

FAQs

No products are displayed on the connection page.

Verify which destinations, products, and options are allowed on your reseller and connection. Next, confirm that your products and options are enabled for sale on the Direct API source. If the issue persists, contact our Technical Support.

My Ventrata products use Booking Size fares, and pricing isn't working correctly on Come to Paris.

After every fare change, update the product mapping to ensure the partner tier counts are synced with Ventrata. Ensure the fare is enabled for sale over Direct API.

📚 More about Ventrata connections

Partner Information

Come to Paris SAS

30 Cours Albert 1er, 75008 Paris

France

cometoparis.com

Ventrata Partner ID: 75af0d57-ae84-4553-b64e-96fd26b91980

Come to Paris: Reseller Connection