Posh APIposh.vip ↗
Access Posh.vip event listings, ticket pricing, attendee guestlists, and host profiles via API. Search by city, keyword, or event slug.
What is the Posh API?
The Posh.vip API exposes 7 endpoints covering event discovery, ticket availability, attendee guestlists, and host profiles from posh.vip. The explore_events endpoint lets you browse events across six US cities with time and sort filters, while get_event_tickets returns ticket group pricing and total tickets sold for any event ID. Each endpoint is designed to work together: discover events, then drill into details, attendees, or the host behind them.
curl -X GET 'https://api.parse.bot/scraper/105167c2-d1c6-49ae-ae1f-4a032902a459/explore_events?city=Los+Angeles&sort=Trending&when=This+Month&limit=5' \ -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 posh-vip-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: Posh Events SDK — discover events, explore hosts, check tickets."""
from parse_apis.posh_events_api import Posh, City_, TimeFilter, EventNotFound
client = Posh()
# Explore trending events in Los Angeles this month
for event in client.city("Los Angeles").explore(when=TimeFilter.THIS_MONTH, limit=3):
print(event.name, event.venue.name, event.start_utc)
# Search for events by keyword in Miami
event = client.city("Miami").search(query="party", limit=1).first()
if event:
# Drill into event details (fetches full info from the event page)
detail = event.details()
print(detail.title, detail.venue_name, detail.currency)
# List attendees for this event
for attendee in event.attendees.list(limit=3):
print(attendee.attendee_first_name, attendee.created_at)
# Check ticket availability
for tg in event.ticket_groups.list(limit=5):
for ticket in tg.tickets:
print(ticket.name, ticket.price, ticket.is_available)
# Discover host profiles in a city
for host in client.hosts.search_by_city(city=City_.NEW_YORK_CITY, limit=2):
print(host.name, host.contact_email, host.instagram)
# Handle a not-found event gracefully
try:
bad_event = client.city("Boston").search(query="nonexistent-xyz-99", limit=1).first()
if bad_event:
bad_event.details()
except EventNotFound as exc:
print(f"Event not found: {exc.slug}")
print("exercised: city.explore / city.search / event.details / attendees.list / ticket_groups.list / hosts.search_by_city")
Browse and discover events by city, time period, and sort order. Returns paginated results including event name, venue, tickets, flyer, and organizer info. Use nextCursor from the response to paginate through results.
| Param | Type | Description |
|---|---|---|
| city | string | City name to browse events in. |
| sort | string | Sort order for results. |
| when | string | Time filter for events. |
| limit | integer | Maximum number of events to return per page. |
| cursor | string | Pagination cursor from a previous response's nextCursor field. Integer encoded as string. |
{
"type": "object",
"fields": {
"events": "array of event objects with _id, name, url, tickets, flyer, venue, startUtc, groupName, groupUrl",
"nextCursor": "integer, pagination cursor for next page"
},
"sample": {
"data": {
"events": [
{
"_id": "6a0df6780d2341afff475dee",
"url": "santa-monica-block-fest-vol-iv-free-music-festival",
"name": "SANTA MONICA BLOCK FEST VOL IV",
"flyer": "https://images.posh.vip/originals/6a16420c1f4ebf9f22376a47",
"venue": {
"name": "THIRD STREET PROMENADE",
"address": "1400 3rd Street Promenade, Santa Monica, CA 90401, USA"
},
"endUtc": "2026-06-14T07:00:00.000Z",
"tickets": [
{
"id": "6a0df7dd934ec4cd08cc0734",
"name": "GA",
"price": 0,
"totalPrice": 0
}
],
"groupUrl": "yappy-studios",
"startUtc": "2026-06-14T00:00:00.000Z",
"timezone": "America/Los_Angeles",
"groupName": "YAPPY STUDIOS"
}
],
"nextCursor": 5
},
"status": "success"
}
}About the Posh API
Event Discovery and Search
The explore_events endpoint accepts a city parameter (Los Angeles, Miami, New York City, Washington DC, Boston, or Atlanta), an optional sort value of 'Trending', and a when filter for 'This Week' or 'This Month'. Results come back paginated with a nextCursor field you pass to the cursor parameter on subsequent calls. The search_events endpoint works similarly but requires a query keyword and scopes results to the same supported cities.
Event Details and Ticketing
get_event_details takes a URL slug (available as the url field in explore or search results) and returns structured fields: eventId (a MongoDB ObjectID), startUtc and endUtc timestamps in ISO 8601, timezone as an IANA identifier, location with lat/lng coordinates, flyer image URL, groupUrl (the host's username slug), and groupName. The get_event_tickets endpoint uses that eventId to return a ticketGroups array with pricing details and a totalTicketsSold integer. get_event_attendees similarly accepts event_id and returns a paginated guestlist array.
Host Profiles
get_host_profile accepts a username slug (pulled from any event's groupUrl field) and returns the host object with name, currency, contactEmail, socials, url, and numOfAttendees, plus an events array of that group's listings. The search_hosts_by_city endpoint automates discovery: given a city and optional limit, it surfaces host profiles with name, username, instagram, contact_email, and their associated events — useful for building a directory of active organizers in a market without manually chaining calls.
The Posh API is a managed, monitored endpoint for posh.vip — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when posh.vip 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 posh.vip 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?+
- Aggregate trending nightlife and social events across major US cities using
explore_eventswith theTrendingsort. - Monitor ticket pricing changes for specific events by polling
get_event_ticketsand trackingticketGroupsover time. - Build a contact directory of event organizers by running
search_hosts_by_cityand extractingcontact_emailandinstagramfields. - Enrich event calendar apps with venue coordinates using the
locationlat/lng returned byget_event_details. - Analyze guestlist size and attendee demand for events by paginating through
get_event_attendeesresults. - Find all events produced by a specific promoter by calling
get_host_profilewith their username slug. - Keyword-search for themed events (e.g., 'rooftop', 'networking') in a target city via
search_events.
| 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 | 100 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 posh.vip have an official developer API?+
What cities are supported for event discovery and host search?+
explore_events, search_events, and search_hosts_by_city endpoints currently accept six cities: Los Angeles, Miami, New York City, Washington DC, Boston, and Atlanta. Events in other cities are not currently filterable by location through these endpoints. You can fork the API on Parse and revise it to add support for additional cities if the underlying data is available.Does `get_event_attendees` return full attendee profiles, or just names?+
guestlist array. The exact fields per attendee entry depend on what the event host has collected, but the response does not expose private contact details for attendees. Detailed demographic or contact data per attendee is not currently part of the response shape. You can fork the API on Parse and revise it if you need to extend what attendee fields are captured.Can I retrieve historical or past events?+
when filter on explore_events supports 'This Week' and 'This Month', both of which target upcoming or current events. Querying for past or archived events is not currently supported by the explore or search endpoints. You can fork the API on Parse and revise it to add a past-events endpoint if that data is accessible on the source.How does pagination work across these endpoints?+
explore_events, search_events, get_event_attendees — include a nextCursor field in their response. Pass that value as the cursor parameter in your next request to retrieve the following page. When nextCursor is absent or null, you have reached the end of the result set.