# Shotgun Scraper — Events, Venues & Lineups (`crawloop/shotgun-scraper`) Actor

Scrape Shotgun.live events, venues, and artists by city, genre, date, or URL. Ticket prices, sold-out flags, GPS, and lineups from public pages. HTTP only, no login.

- **URL**: https://apify.com/crawloop/shotgun-scraper.md
- **Developed by:** [Andrej Kiva](https://apify.com/crawloop) (community)
- **Categories:** Travel, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 event results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Shotgun Scraper — Events, Venues & Lineups

> **Disclaimer:** Unofficial tool — not affiliated with, sponsored by, or endorsed by Shotgun or its affiliates. Data is read from publicly accessible pages only. No login. You are responsible for complying with applicable law (including GDPR where personal data appears) and the site’s terms. No warranty on accuracy or availability. Provided for informational and research use.

**Shotgun scraper** for Apify — a **Shotgun.live events scraper** for **city calendars**, **venue pages**, and **artist profiles**. Built for **nightlife aggregation**, **ticket-price monitoring**, and **promoter lead lists**. Export dates, genres, display prices, sold-out flags, GPS, lineups, and ticket SKUs as JSON. A practical **Shotgun API alternative** for Python, Node.js, Sheets, and **MCP** / AI assistants. HTTP-only (no browser).

> **Crawloop Events suite** — ticketed nightlife, editorial club calendars, and general catalogs.

| Shotgun Scraper ◄── you are here | [Resident Advisor Scraper](https://apify.com/crawloop/resident-advisor-scraper) | [Eventbrite Scraper](https://apify.com/crawloop/eventbrite-scraper) |
| :--- | :--- | :--- |
| Ticketed club nights, prices, SKUs | Club lineups, RA clubs & DJs | Conferences, gigs, organizers |

### When to use this Actor

- **Shotgun events scraper** — city name or slug (`paris`, `new-york`), optional genre and date window
- **Venue / organizer scraper** — paste a `/venues/{slug}` URL (address + public socials)
- **Artist scraper** — paste a `/artists/{slug}` URL
- **Change monitor** — scheduled runs that emit only new or changed prices / sold-out flags
- **Shotgun API alternative** — structured dataset without an organizer API key

### When not to use this Actor

- **Orders, barcodes, guest lists, or sold-ticket PII** — organizer Tickets API, not public listings
- **Full-text search box** — city + genre + URLs; search pages are client-rendered
- **RA magazine blurbs or Eventbrite conferences** — use the suite siblings
- **Private or unlisted events** — public marketplace pages only

### Key features

- **HTTP listings** — city cards already include date, venue, price, and genres
- **Optional event details** — JSON-LD for description, door time, address, GPS, lineup, ticket SKUs
- **Start URLs** — city, genre, date-bounded city, event, venue, and artist pages auto-routed
- **Monitor mode** — remember ids between runs; emit only `new` or `changed`
- **Caps that save budget** — `maxItems` (default 50). Large cities can have thousands of upcoming nights
- **Residential proxy by default on Apify** — Shotgun (Vercel) returns HTTP 429 to datacenter IPs. Local home-IP runs can turn the proxy off

### Input Parameters

| Parameter | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| `mode` | String | `events` | `events`, `venues`, or `artists`. URLs are auto-routed either way |
| `cities` | Array | — | City name or slug (`paris`, `New York`) |
| `startUrls` | Array | — | City, event, venue, or artist URLs |
| `genres` | Array | — | Keep events tagged with these genre names/slugs |
| `dateFrom` / `dateTo` | String | — | `YYYY-MM-DD` window |
| `scrapeDetails` | Boolean | `false` | Extra request per event for SKUs, GPS, lineup |
| `maxItems` | Integer | `50` | Hard cap (`0` = unlimited) |
| `monitorMode` | Boolean | `false` | Emit only new & changed rows |
| `monitorKey` | String | `default` | Isolated monitor memory per saved search |
| `requestDelaySecs` | Number | `0.2` | Delay between HTTP requests |
| `proxyConfiguration` | Object | residential | Required on Apify cloud (Vercel 429 on datacenter IPs). Local HTTP often works without a proxy |

Provide **at least one** of: `cities`, `startUrls`.

#### Input example — city calendar

```json
{
  "mode": "events",
  "cities": ["paris"],
  "maxItems": 50
}
```

#### Input example — genre + dates

```json
{
  "mode": "events",
  "cities": ["new-york"],
  "genres": ["techno"],
  "dateFrom": "2026-09-18",
  "dateTo": "2026-09-30",
  "maxItems": 100
}
```

#### Input example — event URL + details

```json
{
  "startUrls": [
    { "url": "https://shotgun.live/en/events/example-event" }
  ],
  "scrapeDetails": true,
  "maxItems": 1
}
```

#### Input example — monitor a city

```json
{
  "mode": "events",
  "cities": ["lisbon"],
  "maxItems": 200,
  "monitorMode": true,
  "monitorKey": "lisbon-nights"
}
```

### Output

Each dataset item is one **event**, **venue**, or **artist** (`recordType`).

| Field | Type | Description |
| :--- | :--- | :--- |
| `recordType` | String | `event`, `venue`, or `artist` |
| `id` / `eventSlug` | String | Stable id and URL slug |
| `title` / `name` | String | Event title or profile name |
| `url` | String | Canonical event / profile page |
| `startDate` / `endDate` / `doorTime` | String | Schedule (details for end/door) |
| `venueName` / `city` / `country` | String | Where it happens |
| `venueAddress` / `latitude` / `longitude` | String / Number | Address + GPS on details |
| `genreNames` | Array | Listing genre chips |
| `priceAmount` / `priceCurrency` / `priceDisplay` | Number / String | Lowest public price |
| `isSoldOut` | Boolean | Listing or SKU sold-out flag |
| `artistNames` / `lineup` | Array | Performers (details) |
| `tickets` | Array | Ticket SKUs: name, price, availability (details) |
| `organizerName` | String | Promoter / organizer |
| `instagram` / `website` | String | Public socials on venue/artist rows |
| `monitorChange` | String | `new` or `changed` in monitor mode |
| `scrapedAt` | String | UTC timestamp |

City listing rows already include date, venue, display price, and genres. Turn on `scrapeDetails` (or pass event URLs) for description, GPS, lineup, and ticket SKUs.

#### Output example — listing event

```json
{
  "recordType": "event",
  "id": "576198",
  "eventSlug": "frappeirfane",
  "title": "Sacré X Frappé : Irfane, Basile De Suresnes & Ten Fingerz",
  "url": "https://shotgun.live/en/events/frappeirfane",
  "startDate": "2026-09-18T21:00:00.000Z",
  "venueName": "Sacré",
  "city": "Paris",
  "citySlug": "paris",
  "genreNames": ["House"],
  "priceAmount": 9.99,
  "priceCurrency": "EUR",
  "isSoldOut": false,
  "source": "city"
}
```

### Use cases

- Build a city nightlife feed with ticket prices and sold-out flags
- Track promoter calendars and SKU price changes on a schedule
- Collect venue Instagram / website leads from public profiles
- Compare Shotgun ticketed nights with RA editorial lineups
- Feed MCP / AI assistants a structured Shotgun dataset instead of HTML

### Integration examples

#### Node.js

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });

const run = await client.actor('crawloop/shotgun-scraper').call({
  cities: ['paris'],
  maxItems: 50,
  scrapeDetails: false,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.slice(0, 5));
```

#### Python

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("crawloop/shotgun-scraper").call(
    run_input={
        "cities": ["paris"],
        "maxItems": 50,
        "scrapeDetails": False,
    }
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items[:5])
```

#### cURL

```bash
curl "https://api.apify.com/v2/acts/crawloop~shotgun-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"cities":["paris"],"maxItems":20}'
```

### MCP and AI assistants

Use this Actor from AI tools via [Apify MCP](https://docs.apify.com/platform/integrations/mcp).
Connect your Apify account, then call this Actor by its Store ID `crawloop/shotgun-scraper`.

Example prompts:

- "Run Shotgun Scraper for cities paris, max 30 events, and return title, date, venue, price, and URL as JSON"
- "Scrape Shotgun techno nights in new-york this month and summarize sold-out vs on-sale"
- "Chain Shotgun Scraper then Resident Advisor Scraper for Paris this weekend — ticket SKUs plus club lineups"

### FAQ

**Does this use the official Shotgun organizer API?**
No. The organizer Events/Tickets API needs an organizer token for **your** events. This Actor reads public city and event pages.

**Why is search not an input?**
The public search UI is client-rendered. Use a city slug, a genre, dates, or a direct event/venue/artist URL.

**Do listing rows include prices without scrapeDetails?**
Yes. City cards publish a display price and genre chips. SKUs, GPS, and lineup need `scrapeDetails` or an event URL.

**Do I need a proxy?**
On the Apify platform, yes — Shotgun (Vercel) returns HTTP 429 to datacenter IPs. The input default is Apify Residential. Local runs from a home IP usually work with the proxy off.

**Can Paris return thousands of rows?**
Yes. Set `maxItems` (default 50). Unlimited (`0`) will walk cumulative city pages and can be a large run.

**Does monitor mode charge for unchanged events?**
No. Unchanged rows are skipped and not written to the dataset.

**Can I scrape Shotgun with Python or Node.js?**
Yes. Call `crawloop/shotgun-scraper` from the Apify client (examples above) or via **MCP**. The dataset is JSON.

**Is this a Shotgun API alternative?**
Yes, for **public** city calendars, event pages, venues, and artists. It is not a substitute for the organizer API (orders, barcodes, your own listings).

### What to run next

After a Shotgun city dump, run [Resident Advisor Scraper](https://apify.com/crawloop/resident-advisor-scraper) for the same city when you need editorial club calendars, DJ lineups, or public booking blurbs. Use [Eventbrite Scraper](https://apify.com/crawloop/eventbrite-scraper) for conferences and general catalogs.

### Related Actors

- [Resident Advisor Scraper](https://apify.com/crawloop/resident-advisor-scraper) — RA events, clubs, DJs, booking contacts
- [Eventbrite Scraper](https://apify.com/crawloop/eventbrite-scraper) — Eventbrite search, events, organizers

# Actor input Schema

## `mode` (type: `string`):

What to scrape. Start URLs are auto-routed regardless of mode.

## `cities` (type: `array`):

City name or slug (paris, New York, sao-paulo). Used in events mode.

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

City (/cities/paris), genre (/cities/paris/techno), date (/cities/paris/-/2026-09-20), event, venue, or artist pages. Auto-detected.

## `genres` (type: `array`):

Keep events tagged with at least one of these Shotgun genre names or slugs (techno, house, afro). Empty = all. A single slug is also applied as a city URL filter.

## `dateFrom` (type: `string`):

Keep events on or after this date. Also anchors the city URL when set.

## `dateTo` (type: `string`):

Keep events on or before this date.

## `scrapeDetails` (type: `boolean`):

Fetch each event page for description, door time, address, GPS, lineup, and ticket SKUs. Extra request per event. Event URLs always include details.

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

Hard cap across all inputs. 0 = no cap (large cities can be thousands of events).

## `monitorMode` (type: `boolean`):

Remember ids between runs and emit only NEW or CHANGED rows (dates, prices, sold-out).

## `monitorKey` (type: `string`):

Distinct key per saved search so monitors do not share state.

## `requestDelaySecs` (type: `number`):

Throttle between HTTP requests.

## `proxyConfiguration` (type: `object`):

Apify cloud IPs get HTTP 429 from Shotgun (Vercel). Residential is the working default. Local runs can turn the proxy off.

## Actor input object example

```json
{
  "mode": "events",
  "cities": [
    "paris"
  ],
  "startUrls": [],
  "genres": [],
  "dateFrom": "",
  "dateTo": "",
  "scrapeDetails": false,
  "maxItems": 50,
  "monitorMode": false,
  "monitorKey": "default",
  "requestDelaySecs": 0.2,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

Default dataset items.

# 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 = {
    "cities": [
        "paris"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawloop/shotgun-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 = { "cities": ["paris"] }

# Run the Actor and wait for it to finish
run = client.actor("crawloop/shotgun-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 '{
  "cities": [
    "paris"
  ]
}' |
apify call crawloop/shotgun-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawloop/shotgun-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/jU0oMTeauImdiJnkC/builds/TWWqMbhkgEuhKudl5/openapi.json