Use up-to-date Eguide data on your own website
Retrieve your tours, events, contact information, availability, and prices from Eguide. Let visitors make their selection and then securely redirect them to the Eguide booking flow.
Showcase your Eguide offerings on your own website
Do you want visitors to your website to be able to browse guided tours and events? If so, you don't want to have to re-enter the same titles, locations, languages, and prices into a separate management system.
With the API, your website retrieves that data directly from Eguide. This allows you to build your own listing page, search function, or selection experience based on the information your organization already manages.
The API is a standard feature of every Eguide environment. It is intended for external websites and applications that want to display listings and guide visitors to a valid booking page.
If you don't need your own integration, you can use a direct link to more easily refer to a specific tour or event.
Create a selection that suits your visitors
The API provides access to the data that allows your visitors to search your offerings in a targeted manner.
Your website can use cities, locations, languages, tag categories, and tags, among other things. You can use these to create, for example, a list of Dutch-language guided tours in a single city or a selection of activities centered around a specific theme.
Information such as duration, meeting place, final destination, group limits, and publication status may also be available for a guided tour.
The cities, locations, and classifications used are taken from the central reference data that you maintain within Eguide. This ensures that your website uses the same terminology as your internal listings.
Use translations where your website needs them
Various API responses contain translated data. This allows a multilingual website to display the appropriate title, location, or description without having to build a separate product database.
The API does not perform automatic translation on its own. Your website uses the language versions that were previously configured in Eguide. You can read more about this in the section on managing multiple client and working languages within the same environment.
See what your website can do with Eguide
We'll discuss your preferred selection and booking process.
Show available times and corresponding prices
A nice listing page alone isn't enough. Visitors also want to know when they can book and what the price is for their selection.
For private tours, the website can display booking options, times, prices, and valid group sizes. For events, it can show in real time whether they are still bookable and how many spots are available.
This way, visitors can select a tour, event, date, or time right on your own website.
The API uses the availability and prices configured in Eguide. This means you don't have to maintain the same rules in the website code.
Please securely submit the selected option
As soon as the visitor makes a valid selection, your website requests a signed link.
That link takes the selected tour or event, along with the selected date and time, to the Eguide booking flow. The customer does not need to make their selection again there and can immediately proceed to fill in the remaining information.
The signed transfer prevents the website itself from having to process a complete booking or checkout.
Keep customer data and checkout in Eguide
The API does not create a complete booking. It also does not send customer, group, ticket, billing, or payment information.
After the transfer, the customer enters that information within [Eguide's online booking flow]. If online payment is enabled, the payment is then processed through Mollie.
This keeps the responsibilities related to your own website straightforward. Your integration displays the offerings, assists with the selection process, and securely transmits the customer’s choice. Eguide then processes the request and handles any follow-up.
Do not use the API as an external management environment
API v1 does not include any functions for managing bookings, customers, proposals, payments, invoices, guides, or reports externally.
There are also no documented public webhooks or callbacks that allow your website to automatically receive any subsequent changes from Eguide.
The API is therefore best suited to a "read and forward" model: you use up-to-date data to let visitors make their selections, but the actual booking and operational processing remain within Eguide.
Frequently Asked Questions About the API
Practical answers about your integration.
Among other things, the API publishes cities, locations, languages, tag categories, tags, private tours, and events.
Depending on the type of offer, information such as prices, group limits, available times, and remaining event spots is also available.
No. The API supports the selection of products, date, and time, but it is not a full headless checkout.
Further data entry and checkout take place in the Eguide Booking Flow. Any online payments are processed through Mollie.
No. The booking request endpoints return a signed URL that directs the customer to the correct Eguide Booking Flow will be forwarded.
The actual booking is not created until the customer has entered the required information and completed the process.
No. The API does not include functions for managing bookings, customers, proposals, payments, invoices, guides, or reports.
This follow-up takes place in the central Eguide environment.
No. The API is designed to retrieve data and securely pass a selected option to the Eguide booking flow.
Yes. The API is a standard feature of every Eguide environment.
A custom integration must be developed by your website developer or integration partner. A Fully integrated Eguide website remains a separate service.
Can't find your question here? Please contact us. We'd be happy to see what your website can do using the Public API.