# Posh Events Scraper — Tickets, Venues & Organizers (`memo23/posh-events-scraper`) Actor

Scrape events from posh.vip — title, venue, address, coordinates, dates, organizer, lineup, pricing and ticket links. Search by keyword or paste event URLs. JSON or CSV out.

- **URL**: https://apify.com/memo23/posh-events-scraper.md
- **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community)
- **Categories:** Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 scraped items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

<p align="center"><img src="https://raw.githubusercontent.com/muhamed-didovic/muhamed-didovic.github.io/main/assets/posh-events-logo.png" width="140" alt="Posh Events Scraper"></p>

## 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.

![How the Posh Events Scraper works](https://raw.githubusercontent.com/muhamed-didovic/muhamed-didovic.github.io/main/assets/how-it-works-posh-events.png)

### 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.

# Actor input Schema

## `locations` (type: `array`):

Cities to search, or "lat,lng". Supported city names: New York, Brooklyn, Miami, Los Angeles, Washington DC, Boston, Atlanta, Chicago, Houston, Dallas, Austin, Philadelphia, San Francisco, Las Vegas, San Diego, Phoenix, Seattle, Denver, Nashville, New Orleans, Orlando, Tampa, Charlotte, Detroit, Baltimore. Leave empty to search all locations.

## `when` (type: `string`):

Limit to events starting today, this week or this month. Any date returns everything Posh lists.

## `maxPrice` (type: `integer`):

Only events whose cheapest ticket is at or under this price, in USD. 0 = free events only.

## `search` (type: `string`):

Keep only events whose title, venue, city, organizer or lineup contains every word, e.g. "halloween rooftop".

## `startUrls` (type: `array`):

Posh event pages to read directly, e.g. https://posh.vip/e/your-event.

## `fetchDetails` (type: `boolean`):

Open each event page for the full address, latitude/longitude, description and organizer link. One extra request per event.

## `maxItems` (type: `integer`):

Total number of events to return across all locations and URLs.

## `maxItemsPerLocation` (type: `integer`):

Cap per location when several are given. Defaults to Max events.

## `proxy` (type: `object`):

posh.vip is only available from the US. Paying users are routed through our own US residential pool automatically.

## Actor input object example

```json
{
  "locations": [
    "Miami"
  ],
  "when": "anytime",
  "fetchDetails": false,
  "maxItems": 40,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "locations": [
        "Miami"
    ],
    "maxItems": 40,
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "US"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("memo23/posh-events-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "locations": ["Miami"],
    "maxItems": 40,
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "US",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("memo23/posh-events-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "locations": [
    "Miami"
  ],
  "maxItems": 40,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}' |
apify call memo23/posh-events-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,memo23/posh-events-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/14JNRPHAAtE7a51WI/builds/8KHnVloNNLQoVVCDc/openapi.json