Posh Events Scraper — Tickets, Venues & Organizers

Extract structured event data from posh.vip at scale. Give the actor a search keyword (event name, venue, or city) or paste direct event URLs, and it returns one clean row per event: title, description, dates, venue with full address and coordinates, organizer, lineup/artists, pricing, and ticket links.

Why use this Posh Events Scraper

Posh is a social-experience ticketing platform for parties, nightlife, and pop-up events. The site is a client-rendered SPA behind Cloudflare, so most scrapers see nothing. This actor talks to Posh's tRPC API directly (/api/web/v2/trpc) and returns normalized event records — no browser automation, no headless Chrome.

• Search by keyword — event name, venue, or city.
• Cursor pagination — walks every page of results, not just the first.
• Direct event URLs work too — paste posh.vip/e/<slug> links.
• Full venue data — name, address, city, state, zip, coordinates.
• Lineup + organizer + pricing + ticket links per event.
• Residential proxy built in — Posh blocks datacenter IPs.

Overview

Posh (posh.vip) is a ticketing platform for social experiences — parties, club nights, warehouse events, and pop-ups. This actor queries Posh's tRPC marketplace endpoint (events.fetchMarketplaceEvents) with cursor-based pagination and normalizes the response into one record per event. Direct event URLs go through the events.getEventByUrl procedure.

Supported inputs

You provide	Example
A search keyword	warehouse party Brooklyn · techno NYC
A direct event URL	https://posh.vip/e/the-underground-warehouse-party

Use cases

• Build a nightlife events dataset for a city or genre.
• Monitor ticket prices and availability for recurring events.
• Generate leads: organizer names, venues, and ticket links.
• Feed an event discovery or recommendation product.
• Track lineup changes across a promoter's events.

How it works

1. You supply a search keyword or event URLs.
2. The actor calls Posh's tRPC API (/api/web/v2/trpc/events.fetchMarketplaceEvents) with cursor pagination.
3. For direct event URLs, it calls events.getEventByUrl instead.
4. Each event is normalized into a clean record with venue, organizer, lineup, and pricing.
5. Results are written to the dataset as one row per event.

Input configuration

Field	Type	Default	Description
startUrls	array	—	Posh event URLs to scrape directly.
search	string	—	Free-text search — event name, venue, or city.
eventsPerSearch	integer	100	Max events per search query (cursor pagination).
maxItems	integer	1000	Maximum events to scrape.
maxConcurrency	integer	10	Parallel requests.
proxy	object	residential	Posh blocks datacenter IPs — residential proxy required.

Output overview

Each dataset item is a normalized event:

Field	Description
eventId	Posh event ID.
eventUrl	Canonical event page URL.
title	Event name.
description	Event description.
startDate / endDate	Event start and end timestamps.
venueName	Venue name.
venueAddress	Street address.
city / state / zipCode	Venue location.
latitude / longitude	Venue coordinates.
organizerName / organizerUrl	Event organizer.
artists	Lineup / performers.
priceMin / priceMax / currency	Ticket price range.
isFree / isSoldOut	Availability flags.
image	Cover image URL.
ticketUrl	Ticket purchase link.

Notes

• Residential proxy required. Posh is behind Cloudflare and blocks datacenter IPs with a 403. The actor uses the Apify residential proxy by default.
• The tRPC API returns JSON; the actor does not render JavaScript or parse HTML.
• The event field names are resolved defensively — Posh's API schema is not publicly documented and may change. Every field is optional in the output.