Garda Tours APIgardatours.com ↗
Fetch scheduled boat-tour departures from gardatours.com by date. Get departure times, durations, EUR prices, pier info, and booking links via one endpoint.
What is the Garda Tours API?
The gardatours.com API exposes 1 endpoint — list_scheduled_tours — that returns every scheduled boat-tour departure published for a given calendar day on Lake Garda. Each response includes up to 8 structured fields per departure row: tour name, departure time, duration in minutes, adult and child EUR prices, meeting pier, and a direct booking URL. The endpoint covers all tours listed for the requested date and supports optional name filtering.
curl -X GET 'https://api.parse.bot/scraper/ff271ff9-78cf-4eec-b828-9e8047f50064/list_scheduled_tours?date=2026-10-03&tour_name=Sirmione+Peninsula+Tour' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace gardatours-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: GardaTours SDK — look up scheduled boat-tour departures."""
from parse_apis.gardatours_com_api import GardaTours, InputFormatInvalid
client = GardaTours()
# Fetch the full day schedule for a future date.
day = client.day_schedules.get(date="2026-10-04")
print(f"{day.weekday} {day.date} currency={day.currency} available={day.available}")
# Walk each departure and print key details.
if day.departures:
for dep in day.departures:
print(
f" {dep.departure_time} {dep.tour_name} "
f"{dep.duration_minutes}min adult={dep.price_adult_eur}€ "
f"child={dep.price_child_eur}€ pier={dep.meeting_pier}"
)
# Narrow to a specific tour name using the optional filter.
filtered = client.day_schedules.get(date="2026-10-04", tour_name="Sirmione")
print(f"\nFiltered to '{filtered.tour_name_filter}': {filtered.departure_count} departure(s)")
# Demonstrate the typed error for a malformed date.
try:
client.day_schedules.get(date="not-a-date")
except InputFormatInvalid as exc:
print(f"\nExpected error for bad date: {exc.message}")
print("\nexercised: day_schedules.get / InputFormatInvalid")
Returns every scheduled boat-tour departure published for one calendar day (Europe/Rome), one row per departure, sorted by departure time. Each row carries the tour name, departure time (HH:MM), duration in minutes, adult and child prices in EUR (plus a reduced price when the site publishes one, otherwise null), the meeting pier and the exact booking page URL for that departure and day. An optional case-insensitive tour-name filter keeps only departures whose name contains the given text. A single round trip is made. A day with no published departures (including past days and days outside the published season) returns an empty departures array with available=false; it is not an error. Dates that are not ISO YYYY-MM-DD are rejected.
| Param | Type | Description |
|---|---|---|
| daterequired | string | Calendar day to list, ISO date YYYY-MM-DD, interpreted in the Europe/Rome timezone. |
| tour_name | string | Case-insensitive substring filter on the tour name (one shape: 'Sirmione Peninsula Tour'). Omitted = all tours of the day. |
{
"type": "object",
"fields": {
"date": "ISO date requested (YYYY-MM-DD)",
"weekday": "English weekday name of the requested date",
"currency": "currency of all price fields (EUR, as published by the site)",
"available": "true when at least one departure is listed for the day",
"departures": "array of departure rows: schedule_id (site schedule id, integer), tour_id (integer), tour_name, departure_time (HH:MM local), duration_minutes (integer), price_adult_eur (number), price_child_eur (number), price_reduced_eur (number or null), meeting_pier, booking_url (absolute URL to the booking page for this departure and day)",
"departure_count": "number of rows in departures",
"tour_name_filter": "the tour_name filter applied, or null"
},
"sample": {
"data": {
"date": "2026-10-03",
"weekday": "Saturday",
"currency": "EUR",
"available": true,
"departures": [
{
"tour_id": 1,
"tour_name": "Sirmione Peninsula Tour",
"booking_url": "https://gardatours.com/en/scheduled-tours/1-sirmione-peninsula-tour?scheduled=1143&day=1790978400000",
"schedule_id": 1143,
"meeting_pier": "Sirmione - Piazzale Porto",
"departure_time": "11:00",
"price_adult_eur": 12,
"price_child_eur": 6,
"duration_minutes": 25,
"price_reduced_eur": null
},
{
"tour_id": 1,
"tour_name": "Sirmione Peninsula Tour",
"booking_url": "https://gardatours.com/en/scheduled-tours/1-sirmione-peninsula-tour?scheduled=1133&day=1790978400000",
"schedule_id": 1133,
"meeting_pier": "Sirmione - Piazzale Porto",
"departure_time": "17:00",
"price_adult_eur": 12,
"price_child_eur": 6,
"duration_minutes": 25,
"price_reduced_eur": null
}
],
"departure_count": 2,
"tour_name_filter": "Sirmione Peninsula Tour"
},
"status": "success"
}
}About the Garda Tours API
What the API Returns
The list_scheduled_tours endpoint accepts a required date parameter (ISO format YYYY-MM-DD, interpreted in the Europe/Rome timezone) and returns a structured response scoped to that calendar day. The top-level response includes the date, weekday, currency (always EUR), an available boolean indicating whether any departures are listed, a departure_count, and the departures array.
Departure Row Fields
Each object in the departures array contains a schedule_id (integer), a tour_id (integer), the tour_name, departure_time in HH:MM local format, duration in minutes, adult price, child price, and a reduced price when applicable — all denominated in EUR as published on the site. Meeting pier and a direct booking page link are also included per row.
Filtering
The optional tour_name parameter accepts a case-insensitive substring (for example, 'Sirmione Peninsula Tour') to narrow results to a specific tour. When omitted, the endpoint returns all departures for that day across every tour. The tour_name_filter field in the response reflects whatever filter was applied, or null if none was used.
Coverage and Freshness
The API reflects the scheduled departures as published on gardatours.com for the requested date. Results are limited to tours with publicly listed schedules for that day — there is no multi-day range query or historical archive; each call targets a single date.
The Garda Tours API is a managed, monitored endpoint for gardatours.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when gardatours.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official gardatours.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display a daily departure board for Lake Garda boat tours with times and EUR prices.
- Check whether a specific tour (e.g. Sirmione Peninsula Tour) runs on a given date using the
tour_namefilter. - Compare adult vs. child pricing across all departures on a selected day.
- Surface meeting pier information alongside departure times in a travel itinerary app.
- Monitor which tours are available on weekends vs. weekdays using the
weekdayresponse field. - Aggregate booking links per departure to redirect users directly to the gardatours.com purchase page.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does gardatours.com have an official developer API?+
What does the `available` field tell me, and how is it different from `departure_count`?+
available is a boolean that is true when at least one departure row exists for the requested date. departure_count gives the exact integer count of those rows. If no tours run that day, available is false and departure_count is 0 with an empty departures array.Does the API cover multi-day ranges or historical departure data?+
list_scheduled_tours endpoint targets a single calendar day per request; there is no date-range parameter or archive of past schedules. You can fork this API on Parse and revise it to add a date-range looping endpoint if you need multi-day data.Is private charter or custom tour booking data included?+
How does the `tour_name` filter behave if I spell the tour name slightly differently?+
tour_name contains the supplied substring. So 'sirmione' would match 'Sirmione Peninsula Tour'. If the substring matches no tour names for that date, the departures array will be empty and available will be false.