Travel Gay APIfr.travelgay.com ↗
Search LGBTQ+ venues, events, editorials, and pride festivals from Travel Gay (fr.travelgay.com) via 2 structured JSON endpoints.
What is the Travel Gay API?
The Travel Gay API exposes 2 endpoints for querying LGBTQ+-focused travel data from fr.travelgay.com, covering venues, events, editorials, and group trips. The search endpoint returns results across all four content types in a single response, while list_events delivers paginated upcoming events alongside a dedicated featured_prides array with date, location, and image fields.
curl -X GET 'https://api.parse.bot/scraper/8043a5f4-c0f3-4b78-b77b-bd74636c750a/search?query=London' \ -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 fr-travelgay-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: Travel Gay SDK — browse events, prides, and search results."""
from parse_apis.fr_travelgay_com_api import TravelGay, InputFormatInvalid
client = TravelGay()
# List upcoming LGBTQ+ events with date and location details.
for event in client.events.list(limit=5):
dates_info = ""
if event.dates:
d = event.dates[0]
dates_info = f" ({d.start_date} to {d.end_date})"
print(f"{event.name} — {event.city_name}, {event.country_name}{dates_info}")
# Browse featured pride festivals.
pride = client.prides.list(limit=3).first()
if pride is not None:
print(f"Featured pride: {pride.name} — {pride.sub_title}")
# Search for venues, events, and editorials by keyword.
try:
for result in client.search_results.search(query="pride", limit=5):
print(f"[{result.type}] {result.name} (rating: {result.average_rating})")
except InputFormatInvalid as e:
print(f"Invalid search input: {e.message}")
print("exercised: events.list / prides.list / search_results.search")
Search Travel Gay for events, venues, editorials, and group trips by keyword. Returns all matching results in a single list with a type field distinguishing Venue, Event, Editorial, and GroupTrip entries. For Venue results, an additional request is made per venue to retrieve the venue_type (e.g. bar, hotel, sauna, restaurant); this field is null for non-Venue results or when unavailable. The upstream returns all results in one response without pagination.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g. a city name, venue name, or event topic). |
{
"type": "object",
"fields": {
"total": "integer count of results returned",
"results": "array of search result objects, each with id, name, slug, type (Venue/Event/Editorial/GroupTrip), venue_type (venue category such as Bar, Hotel, Sauna, Restaurant — populated for Venue results, null otherwise), address, city_id, content, url, average_rating, total_ratings, tg_approved, image_url"
},
"sample": {
"data": {
"total": 29,
"results": [
{
"id": 1799,
"url": "https://www.travelgay.com/venue/eating-london-twilight-soho-food-tour?token=0UnIY",
"name": "Eating London - SOHO Food Tour",
"slug": "eating-london-twilight-soho-food-tour",
"type": "Venue",
"address": "around Soho",
"city_id": 1,
"content": "<p>Finding your way around the Soho gay scene is easy...</p>",
"image_url": "https://static.travelgay.com/media/8408/Eating-London-Tour-gay-service-provider-.jpg",
"tg_approved": null,
"total_ratings": 3,
"average_rating": 4.3
}
]
},
"status": "success"
}
}About the Travel Gay API
What the API covers
The Travel Gay API surfaces structured data from fr.travelgay.com across four content categories: Venue, Event, Editorial, and GroupTrip. Each result includes an id, name, slug, type, address, city_id, content, and url. The type field is the primary way to distinguish between a bar or hotel listing (Venue), a scheduled event (Event), a published article (Editorial), or an organized trip (GroupTrip).
search endpoint
The search endpoint accepts a single required query string — a city name, venue name, or topic keyword — and returns all matching results in one response with a total count. No pagination parameters are supported; the full result set is returned in a single call. This makes it straightforward to filter client-side by type or city_id when the result set is manageable.
list_events endpoint
The list_events endpoint returns upcoming LGBTQ+ events with full pagination metadata: current_page, last_page, per_page, and total. Each event object includes id, name, slug, sub_title, address, venue_name, city_name, city_slug, country_name, country_code, and date. Omitting the optional page parameter returns the first page, capped at 21 events. Alongside paginated events, the response includes a separate featured_prides array with id, name, slug, sub_title, dates, month, and image_url — useful for building pride calendar features independently of the main event list.
The Travel Gay API is a managed, monitored endpoint for fr.travelgay.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when fr.travelgay.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 fr.travelgay.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?+
- Build a city-specific LGBTQ+ venue directory by searching with a city name and filtering results by type=Venue.
- Display an upcoming pride calendar by reading featured_prides entries with their month, dates, and image_url fields.
- Aggregate LGBTQ+ travel articles by filtering search results where type=Editorial.
- Power a destination page showing nearby events by combining search results filtered to type=Event with list_events data.
- List organized group trips by filtering search results where type=GroupTrip.
- Build a paginated event feed using list_events with the page parameter and pagination.last_page for navigation control.
- Show country-level event coverage by grouping list_events results by country_name or country_code.
| 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 Travel Gay have an official developer API?+
How does the search endpoint distinguish between venues, events, articles, and trips?+
results array includes a type field set to one of four values: Venue, Event, Editorial, or GroupTrip. You can filter this array client-side to isolate the content category you need.