← Back to all apps

On the Beach Holidays

Travelby On the Beach Limited
Open in ChatGPTWebsite
Launched Jun 6, 2026 on ChatGPT

Search for holidays like you're texting your mate.

"Somewhere hot in Feb." "All Inclusive with a waterpark, early flights and good reviews." "A city break with great history and delish food."

Whatever vibe you're after, On the Beach serves up package holidays that match - flights and hotel included, every package ATOL and ABTA protected, with flexible payment plans to spread the cost.

Found one you love? Tap through to On the Beach to see full details and book.

1ChatGPT Tools
On the Beach LimitedDeveloper
TravelCategory

Available Tools

Search for holidays

search_holidays
Full Description

Use this when a customer wants to search for or book a package holiday. IMPORTANT

  • RE-CALL THIS TOOL when the user:
    • Asks for different/closer/farther locations
    • Wants to change dates, guests, price range, or amenities
  • Asks for "more options", "cheaper", "better rated" ALWAYS USE humanReadable FIELD TO GET PACKAGE PRICE. ATOL and ABTA-protected package holidays with return flights from UK airports and hotel accommodation — covering a wide range of beach, sun, city break, and long-haul destinations. Always search to check availability for any destination rather than assuming whether it is or isn't offered. Do not use for flight-only or hotel-only bookings. Holidays cannot be booked directly through this tool. DESTINATION GUIDANCE:
    • Always search to validate availability — never assume a destination is or isn't available without searching first. If results come back empty, that means no availability was found for those parameters, not that On the Beach doesn't offer that destination
    • When a customer is open to suggestions, use your knowledge of destinations to identify 2–3 that genuinely fit their brief (see VIBE AND HOTEL MATCHING in the system prompt). Search those — do not default to the same popular destinations every time.
    • When the customer asks for a "city break", search urban/cultural destinations only (e.g. Amsterdam, Barcelona, Berlin, Prague, Krakow, Rome, Lisbon, Budapest, Marrakech). Do NOT search for or return beach or sun resorts for city break requests.
    • If a customer excludes a destination (e.g. "not Turkey", "not mainland Spain"), build a positive list of permitted destinations and pass those into the search. Never include an excluded destination in results or suggestions, even as an example.
  • Always present results across at least 2 different destinations unless the customer has specified one exactly. DATE DEFAULTS:
    • When a customer mentions a "weekend break", "short weekend getaway", or similar, do not use mid-week departures unless the customer explicitly asks for them.
    • Interpret "next weekend" as departures on Friday or Saturday of the next calendar weekend in the user's local timezone. Do not use Sunday or Monday departures by default. Prioritise Friday departure for 2–3 nights, Saturday departure for 2 nights.
    • Prioritise the above departure patterns first. Widen beyond them only if needed to provide suitable, available, or better-value options
  • When a customer requests a specific day of week for departure (e.g. "Sunday flights"), calculate all dates falling on that day within their travel window and run a separate search per date using a single-day date range. Combine results across all searches before presenting. FLIGHT TIME PARAMETERS:
    • When a customer specifies a preferred departure or return time, always populate the outbound_departure_time_start_range, outbound_departure_time_end_range, inbound_departure_time_start_range, and inbound_departure_time_end_range fields.
    • Use these mappings: morning = 06:00–12:00, afternoon = 12:00–18:00, evening/night = 18:00–23:59.
    • Before presenting results, check the departureTime values returned and exclude any that do not match the customer's stated preference. If the user asks about a specific facility, use the facilities filter. Available options: 4 (Air Conditioning), 9 (Aqua Park), 19 (By the Beach), 22 (Spa), 35 (Disabled Friendly), 39 (Entertainment), 43 (Golf), 44 (Gym), 54 (Kids Club), 95 (Swimming Pool).
Parameters (19 required, 3 optional)
Required
board_basisarray

An array board basis to include. For Bed and Breakfast, provide BB. For All Inclusive, provide AI. For Full Board, provide FB. For Half Board, provide HB. For Room Only provide RO. For Self Catered, provide SC. Provide an empty array if not provided.

child_agesarray

An array of ages for each of the children going on the holiday. The array length should be the same as the number of children going on holiday. Must be the child ages upon return to provide accurate prices. This can be assumed or guessed but make it clear that you are making an assumption and ask for clarification if the user does not provide ages or if the ages provided do not match the number of children requested.

departure_airportarray

Airport IATA code. Use empty array if user is open to any departure airport.

departure_date_end_rangestring

The departure date end range in YYYY-MM-DD format. Use departure_date_start_range plus three days if not provided. If user wants a full month, use the last day of the month. Must not be in the past. Must not be more than 31 days since departure_date_start_range.

departure_date_start_rangestring

The departure date start range in YYYY-MM-DD format. Use today plus 7 days if not provided. Must not be in the past. When 'next' is used (for example, next April), use the current year plus 1

destinationsarray

An array of destinations. Use an empty array to search all holidays. If the user has provided some indication of where they'd like to travel to, be proactive in helping the customer find suitable destinations by asking questions before searching.

facilitiesarray

An array of hotel facility IDs to filter by. Available facilities: 4 (Air Conditioning), 9 (Aqua Park), 19 (By the Beach), 22 (Spa), 35 (Disabled Friendly), 39 (Entertainment), 43 (Golf), 44 (Gym), 54 (Kids Club), 95 (Swimming Pool), 107 (Wifi). Provide an empty array if not requested.

inbound_departure_time_end_rangestring

The inbound departure time end range in format HH:MM. Used for providing a preference on inbound departure flight time. Should not be provided without inbound_departure_time_start_range.

inbound_departure_time_start_rangestring

The inbound departure time start range in format HH:MM. Used for providing a preference on inbound departure flight time. Should not be provided without inbound_departure_time_end_range.

number_of_adultsnumber

The number of adults going on the holiday. Use 2 if not provided.

number_of_bagsnumber

The number of checked bags requested. Use 0 if not explicitly provided.

number_of_childrennumber

The number of children going on the holiday. A child is between 2 and 15 years old on return date. Use 0 if not provided.

number_of_infantsnumber

The number of infants going on the holiday. An infant is between 0 and 23 months old on return date. Use 0 if not provided.

number_of_nightsnumber

The number of nights the user wants to go on holiday for. Use 7 if not provided.

number_of_roomsnumber

The number of rooms requested. Make an assumption based on number of adults, children and infants requested.

outbound_departure_time_end_rangestring

The outbound departure time end range in format HH:MM. Used for providing a preference on outbound departure flight time. Should not be provided without outbound_departure_time_start_range.

outbound_departure_time_start_rangestring

The outbound departure time start range in format HH:MM. Used for providing a preference on outbound departure flight time. Should not be provided without outbound_departure_time_end_range.

sort_methodstring

The sort method used to return results. Must be one of POPULARITY, PRICE_HIGH_LOW, PRICE_LOW_HIGH, or STAR_RATING. Use POPULARITY by default. Choose intentionally based on what the customer is searching for, for example, if they are looking for the best hotels, use STAR_RATING. When a customer has not specified a star rating or board basis and provides a budget, use PRICE_HIGH_LOW to surface better quality options closer to their budget rather than the cheapest available.

Options:POPULARITYPRICE_HIGH_LOWPRICE_LOW_HIGHSTAR_RATING
star_ratingarray

An array of star ratings to include. For example, 1, 2, 3, 4 or 5. Provide an empty array if not requested.

Optional
maximum_total_pricenumber

The upper limit for the whole holiday for all passengers. A number in cents Where £1 is 100.

min_trip_advisor_scorestring

The minimum TripAdvisor score to filter hotels by. Valid values are 2.0, 2.5, 3.0, 3.5, 4.0, 4.5, 5.0. Leave empty if not requested.

Options:2.02.53.03.54.04.55.0
user_querystring

A natural language summary of the user's full multi-turn intent, generated by the model. This field semantically compresses the conversation into a single structured query written from the user's perspective, using their original language and tone. It must reflect only explicitly stated requirements — no inferred constraints, defaulted values, PII, or street-level addresses.

Links

WebsitePrivacy PolicyTerms of Service