Hellenic Heritage Tickets is the official ticketing platform of the Hellenic Ministry of Culture and ODAP, covering a network of more than 350 archaeological sites, museums and monuments across Greece, including twenty UNESCO World Heritage sites. Its unified e-ticket brings 108 venues onto one system with timed entry, mobile QR admission and regional and thematic passes.
Connecting Hellenic Heritage to Ventrata lets you resell products from operators that use Hellenic Heritage as their booking system. Ventrata reads their live availability from Hellenic Heritage, and every booking you take is created directly in the operator's Hellenic Heritage account.
To learn more about Hellenic Heritage, visit tickets.hh.gr.
📗 TIP
Make a test booking after mapping and ask Hellenic Heritage Tickets to confirm it arrived in their system.
Primary website | |
Tags | Booking / Ticketing System |
Connection features | Availability Sync · Bookings Sync |
Developed by | Ventrata (using Hellenic Heritage Tickets API) |
This operator connection (also called a backend) lets you resell products from operators that use Hellenic Heritage as their primary booking system, with every booking created directly in Hellenic Heritage. Features of this connection include:
Availability Sync – live availability comes from the operator's Hellenic Heritage account.
Bookings Sync – bookings post from Ventrata to Hellenic Heritage, and Hellenic Heritage issues the tickets or vouchers.
Hellenic Heritage's external API used for this connection is a custom API that does not follow the OCTO API standard, which may limit certain functionality and capabilities.
Creating the Hellenic Heritage Connection
🔐 Required Role Permissions: See Operators, Modify Operators, See Products, Modify Products
Before you begin:
You must have a commercial agreement with the operator for their rates and terms.
You must have the API credentials from Hellenic Heritage Tickets (the article does not name the individual fields) for the operator. See the steps below.
You must recreate the operator's products in Ventrata. See how to create products. The connection syncs availability, pricing and bookings, but doesn't create products in Ventrata.
Step 1: Request API credentials
Contact Hellenic Heritage Tickets and request the API credentials for you to resell their products through Ventrata.
Step 2: Configure the Operator in Ventrata
Contact Hellenic Heritage Tickets and request the API credentials so you can resell their products through Ventrata.
In the Ventrata Dashboard, go to Products → Operators and open the operator. If they don't exist yet, create them as an operator first.
In the Backend Partner section, select Hellenic Heritage and enter the API credentials from Hellenic Heritage Tickets (the article does not name the individual fields).
Press Update Operator.
Step 3: Connect Each Product
Open the operator's product in Products → Products and edit it. Check that Operator is set to this operator.
Tick Backend Connected. Tick Backend Availability to use availability from Hellenic Heritage.
Press Update Product.
Make sure the Operator on the product is set to Hellenic Heritage Tickets.
Check Backend Connected. To pull availability from Hellenic Heritage Tickets, also check Backend Availability; to pull pricing, check Backend Pricing.
Without Backend Availability and Backend Pricing, the product uses the availability and pricing configured in Ventrata but still sends bookings to Hellenic Heritage Tickets.
Mapping Products to Hellenic Heritage
‼️ IMPORTANT
Mapping tells Ventrata which Hellenic Heritage product, option and units to check availability for and book. If a backend-connected product isn't mapped correctly, its bookings fail. A red highlight across the product row shows an incorrectly mapped product.
In the Ventrata Dashboard, go to Products → Products and open the product.
Open the Mappings tab. It appears once the product is set to Backend Connected.
For each Ventrata option and unit, select the matching Hellenic Heritage product, option and units from the dropdowns, which Ventrata loads from Hellenic Heritage. Don't leave any field empty.
Press Save Changes.
📗 TIP
Make a test booking after mapping, and ask the operator to confirm it arrived in their Hellenic Heritage account.
Managing the Hellenic Heritage Connection
Update the mapping when the operator changes products, options or units in Hellenic Heritage.
Replace the key on the operator if Hellenic Heritage or the operator issues a new one.
Switch Backend Availability or Backend Pricing off on a product to use Ventrata's own availability or prices instead. Bookings still post to Hellenic Heritage.
Connection Features Detailed
This section is for anyone who wants to know exactly how the Hellenic Heritage connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Hellenic Heritage, using Hellenic Heritage Tickets API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks Hellenic Heritage for availability whenever someone looks at a backend-connected product, and creates every booking in the operator's Hellenic Heritage account. Hellenic Heritage doesn't send changes back to Ventrata.
Timings are typical for Hellenic Heritage and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's Hellenic Heritage product in the Ventrata Dashboard. This works as follows:
What this means for you: if something is missing from the dropdown, the operator hasn't made it available to you in Hellenic Heritage. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from Hellenic Heritage. Ventrata doesn't import product content from Hellenic Heritage. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in Hellenic Heritage. This works as follows:
What this means for you: customers book against the operator's live Hellenic Heritage availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ❌ |
Ventrata doesn't read prices from Hellenic Heritage. Ventrata doesn't read prices from Hellenic Heritage. Products use the prices you set in Ventrata, and bookings still post to Hellenic Heritage. |
Promotions Sync | ❌ |
Promotions aren't sent to Hellenic Heritage. Promotions aren't sent to Hellenic Heritage. Your Ventrata promotions still apply to the price your customer pays in Ventrata. |
Bookings Sync | ✅ |
Bookings made in Ventrata for a backend-connected product are created in the operator's Hellenic Heritage account. This works as follows:
Sends bookings, updates and cancellations from Ventrata to Hellenic Heritage Tickets.
‼️ IMPORTANT – Bookings sync one way, from Ventrata to Hellenic Heritage. If the operator changes or cancels a booking in Hellenic Heritage, Ventrata isn't notified. Ask the operator to tell you about any changes they make. |
Pickups/Dropoff Sync | ❌ |
Pickup and drop-off details aren't passed to Hellenic Heritage. Pickup and drop-off details aren't passed to Hellenic Heritage. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to Hellenic Heritage. Answers to your booking questions aren't passed to Hellenic Heritage. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in Hellenic Heritage. Extras and add-ons aren't booked in Hellenic Heritage. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in Hellenic Heritage aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in Hellenic Heritage aren't sent back to Ventrata after a booking is confirmed. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with Hellenic Heritage. Pass walk-up scanning isn't available with Hellenic Heritage. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to Hellenic Heritage. Ventrata gift cards aren't passed to Hellenic Heritage. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the Hellenic Heritage connection
Good to know: limits and details of the Hellenic Heritage connection
Live availability: availability comes from Hellenic Heritage as people browse.
One-way bookings: changes the operator makes in Hellenic Heritage don't reach Ventrata.
Custom API: Hellenic Heritage's API isn't OCTO, so some features may be limited compared with OCTO backends.
The connection does not create products automatically; recreate them in Ventrata first.
About the partner (from the article intro): official ticketing platform of the Hellenic Ministry of Culture and ODAP covering more than 350 archaeological sites, museums and monuments, including twenty UNESCO World Heritage sites. A unified e-ticket rollout in 2026 brought 108 venues onto one system with timed entry, mobile QR admission, and regional and thematic passes.
FAQs
I get an error when I save the operator's backend configuration.
I get an error when I save the operator's backend configuration.
The API credentials from Hellenic Heritage Tickets (the article does not name the individual fields) or endpoint is most likely incorrect. Check them with your operator. If the issue persists, contact our Technical Support.
There's no Backend Connected box in the product settings.
There's no Backend Connected box in the product settings.
The operator set on the product most likely doesn't have a backend configured. Check the operator's Backend Partner settings and try again. If the issue persists, contact our Technical Support.
The product, option or unit I want to map isn't in the dropdown.
The product, option or unit I want to map isn't in the dropdown.
The dropdowns list what the operator has made available to you in Hellenic Heritage. Ask the operator. If the issue persists, contact our Technical Support.
Bookings fail for a backend-connected product.
Bookings fail for a backend-connected product.
Check the product's mapping first: every option and unit must be mapped. Then check that the slot is still available in Hellenic Heritage. If the issue persists, contact our Technical Support.
I get an error when saving the operator's backend configuration.
I get an error when saving the operator's backend configuration.
The credentials are most likely incorrect. Double-check them with Hellenic Heritage Tickets. If the issue persists, contact Technical Support.
There is no Backend Connected checkbox in the product settings.
There is no Backend Connected checkbox in the product settings.
The operator selected on the product most likely has no backend configured. Check the operator's backend configuration and try again.
Useful Resources
📚 More about Ventrata connections
Partner Information
Hellenic Heritage Tickets
Eleftheriou Venizelou 57
105 64 Athens, Greece
Ventrata Partner ID: 086db963-6786-4ca6-b86f-e01408d945c4