# Time Out Events & Things-To-Do Scraper (`parsing_machine/timeout-events-scraper`) Actor

Scrape Time Out (timeout.com) city events and things to do. Get title, venue, address, start/end datetime, price, ticket link, category, image and editorial summary. Pay per result. No login or proxy key needed.

- **URL**: https://apify.com/parsing\_machine/timeout-events-scraper.md
- **Developed by:** [Iakov Iudin](https://apify.com/parsing_machine) (community)
- **Categories:** Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

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

## Time Out Events & Things-To-Do Scraper

Collect publicly available **Time Out (timeout.com)** city listings — "things to do",
events, theatre, music, art and more — as clean, structured records. Point it at a
city and section; it reads the hub and enriches every card from its detail page so
you get the full event, not just a headline.

### What you get (one record per event)

| field | description |
|---|---|
| `event_id` | stable slug id from the event URL |
| `title` | event / listing title |
| `event_url` | Time Out detail-page URL |
| `location_name` | venue name |
| `address` | full venue address (street, locality, postcode) |
| `start_datetime` / `end_datetime` | ISO datetimes (from the page's structured data) |
| `price_range` | price / price range with currency |
| `ticket_booking_url` | booking / ticket link when present |
| `description` | editorial summary |
| `category` | event type (TheaterEvent, MusicEvent, …) or section |
| `image_url` | lead image |
| `rating_text` | Time Out star rating when shown |

### Input

| field | default | description |
|---|---|---|
| `location` | `london` | city slug as in the URL (e.g. `newyork`, `paris`, `chicago`, `tokyo`) |
| `section` | `things-to-do` | hub section (`things-to-do`, `theatre`, `music`, `art`, `attractions`, `comedy`) |
| `search_query` | — | optional keyword filter on title/summary |
| `maxItems` | `50` | cap on events (`0` = whole section) |
| `proxyConfiguration` | RESIDENTIAL | uses Apify Residential by default — **no external proxy key needed** |

### How it works

The listing hubs are server-rendered, so the scraper parses each card by stable
structural attributes (resistant to cosmetic markup changes) and pulls the
structured per-event data (datetimes, venue, address, price, tickets) from each
detail page's schema.org JSON-LD. Requests use a residential proxy for reliable
access; you only supply the city and section.

### Pricing

Pay per result — you are charged once per event record written to the dataset.
Compute runs on your own Apify account.

### Notes

Use the city/section slugs exactly as they appear in the timeout.com URL after the
domain (e.g. `https://www.timeout.com/london/things-to-do` → `location=london`,
`section=things-to-do`). This tool collects publicly available listing data for
research and aggregation.

# Actor input Schema

## `location` (type: `string`):

City slug as it appears in the timeout.com URL — e.g. london, newyork, paris, chicago, losangeles, sydney, tokyo. Default: london.

## `section` (type: `string`):

Time Out hub section to scrape — e.g. things-to-do (default), theatre, music, art, attractions, comedy. Must match the URL path segment after the city.

## `search_query` (type: `string`):

Optional case-insensitive keyword. Only cards whose title or summary contains it are returned. Leave empty to return the whole section.

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

Maximum number of events to return. Default 50. Set 0 for no limit (the whole section hub).

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

Proxy used to reach timeout.com. Apify RESIDENTIAL is recommended and used by default — no external proxy key required.

## Actor input object example

```json
{
  "location": "london",
  "section": "things-to-do",
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

Dataset of event records (event\_id, title, event\_url, location\_name, address, start\_datetime, end\_datetime, price\_range, ticket\_booking\_url, description, category, image\_url).

# 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 = {
    "location": "london",
    "section": "things-to-do",
    "maxItems": 50,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("parsing_machine/timeout-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 = {
    "location": "london",
    "section": "things-to-do",
    "maxItems": 50,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("parsing_machine/timeout-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 '{
  "location": "london",
  "section": "things-to-do",
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call parsing_machine/timeout-events-scraper --silent --output-dataset

```

## MCP server setup

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