ticketswap.nl APIticketswap.nl ↗
Access TicketSwap event details, ticket listings, prices, artist pages, and trending events via 6 structured endpoints. Search, browse, and retrieve sold transaction data.
curl -X GET 'https://api.parse.bot/scraper/ce18a647-b0e2-4a1f-a4a4-61773779bffa/search_events' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for events, artists, venues, and cities by keyword.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g., 'coldplay', 'amsterdam') |
{
"type": "object",
"fields": {
"initialQuery": "string",
"initialApolloState": "object (normalized Apollo cache with entities)"
},
"sample": {
"initialQuery": "coldplay"
}
}About the ticketswap.nl API
The TicketSwap.nl API provides 6 endpoints covering event search, event detail pages, individual ticket listings, artist profiles, city or category browsing, and homepage trending events. The get_listing_details endpoint, for example, returns a full listing's ticket count, price, and availability status by accepting a hash, slug, and listing ID pulled directly from any TicketSwap listing URL.
What the API Covers
The API surfaces structured data from TicketSwap's event and ticket marketplace. Six endpoints map to the main content types on the site: event search results, individual event pages, ticket listing detail pages, artist profiles, city/category browse pages, and the homepage trending feed. Every response includes an initialApolloState object — a normalized entity graph keyed by type and ID — containing fields for events, venues, artists, listings, and ticket metadata.
Searching and Browsing Events
search_events accepts a query string (artist name, city, keyword) and returns initialQuery plus a full initialApolloState containing matched Event, Artist, Venue, and City entities. browse_events lets you narrow by city_slug (e.g., amsterdam/3) or category_slug (e.g., concerts) to retrieve curated event lists without a keyword. get_trending_events takes no inputs and returns the same normalized state shape populated with whatever events TicketSwap is currently surfacing on its homepage.
Event, Artist, and Listing Detail
get_event_details takes a full event slug and returns an initialApolloState containing the Event object along with linked Artist and Venue data. get_artist_details works similarly using an artist_slug and returns Artist info alongside that artist's upcoming events. For individual listings, get_listing_details requires three identifiers — hash, slug, and listing_id — all derivable from a standard TicketSwap listing URL, and returns Listing and Ticket details including price and availability.
Data Shape Notes
All endpoints return the same outer envelope (initialApolloState), so response parsing is consistent across calls. Entity references inside the Apollo cache use normalized keys, meaning related objects (e.g., the Venue attached to an Event) are stored once and referenced by ID. Consumers should expect to resolve these cross-references when flattening the response for downstream use.
- Monitor resale ticket prices for specific events using
get_listing_detailsprice fields - Build an event discovery feed filtered by city using
browse_eventswithcity_slug - Track which events an artist has upcoming by polling
get_artist_details - Aggregate trending events data from
get_trending_eventsto surface popular shows in a region - Index TicketSwap venue and event metadata for a concert guide using
get_event_details - Alert users when new listings appear for an event by periodically calling
search_eventswith an artist name - Compare face-value versus resale prices by pairing event data with listing prices from
get_listing_details
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does TicketSwap have an official developer API?+
What does `get_listing_details` return beyond the ticket price?+
initialApolloState containing Listing and Ticket entities. This includes availability status, the listing hash, and associated event slug in addition to price. All three identifiers — hash, slug, and listing_id — must be supplied; they are all present in a standard TicketSwap listing URL.Does the API return sold transaction history or only active listings?+
get_listing_details, while historical sold data surfaces within the initialApolloState on event detail pages via get_event_details.Does the API support pagination for search results or browse pages?+
search_events or browse_events. The API covers first-page results for those endpoints. You can fork it on Parse and revise to add offset or cursor parameters if deeper pagination is needed.