# Peatix Events Scraper (`ardent_fork/peatix-events`) Actor

Events from Peatix (peatix.com), Japan's biggest community-event and ticketing platform: search by keyword or fetch by URL — dates, venue, ticket tiers with prices, organizer, group, tags, full description. No login, no API key.

- **URL**: https://apify.com/ardent\_fork/peatix-events.md
- **Developed by:** [KF P](https://apify.com/ardent_fork) (community)
- **Categories:** Social media, Lead generation
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 events

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Peatix Events Scraper

Scrape events from [Peatix](https://peatix.com), Japan's biggest community-event and ticketing platform (also active in Singapore, Malaysia and the US): tech meetups, seminars, workshops, community gatherings.

Search by keyword and/or fetch specific events by URL. Every result is one complete event record: dates with timezone, venue or online flag, every ticket tier with price and seats sold, organizer, hosting group, tags, cover image and the full description (HTML + plain text). No login, no API key, pay per event.

### Input

| Field | Type | Description |
|---|---|---|
| `searchKeywords` | array | Keywords to search for (max 20), any language. Results are de-duplicated across keywords. |
| `eventUrls` | array | Direct `https://peatix.com/event/<id>` URLs or bare numeric ids (max 2000). |
| `maxItems` | integer | Stop after this many events (default 100, max 10000). You pay only for pushed events. |
| `maxConcurrency` | integer | Parallel requests (default 5, max 10). Requests to each host are spaced ~1 s apart, matching Peatix's requested crawl-delay. |
| `proxyConfiguration` | object | Optional proxy settings; normally not needed. |

At least one of `searchKeywords` / `eventUrls` is required. Vanity `<name>.peatix.com` URLs are not accepted — open one in a browser and copy the `peatix.com/event/...` URL it leads to.

```json
{
  "searchKeywords": ["python", "スタートアップ"],
  "maxItems": 200
}
```

### Output

One dataset item per event:

```json
{
  "id": "5145560",
  "url": "https://peatix.com/event/5145560",
  "name": "はじめてのPython！ガチャ作りでプログラミング入門",
  "status": "open",
  "locationType": "online",
  "online": true,
  "startUtc": "2026-09-06T01:00:00Z",
  "endUtc": "2026-09-06T12:30:00Z",
  "timezone": "Asia/Tokyo",
  "venue": null,
  "organizer": { "id": "7225391", "name": "まなび梯" },
  "group": { "id": "8844805", "name": "praxiSpace", "url": "https://peatix.com/group/8844805" },
  "tickets": [
    { "id": "6605791", "name": "参加チケット", "type": "free", "status": "on_sale", "price": 0, "currency": "JPY", "currencyPrecision": 0, "seatsMax": 15, "seatsSold": 0, "salesStartUtc": null, "salesEndUtc": null }
  ],
  "isFree": true,
  "tags": ["ファミリー／キッズ", "プログラミング言語"],
  "cover": "https://cdn.peatix.com/event/5145560/cover-....png",
  "description": "<h2>動くガチャを自分でプログラミング！...</h2>...",
  "descriptionText": "動くガチャを自分でプログラミング！ ...",
  "publishedUtc": "2026-08-20T06:43:23Z",
  "createdUtc": "2026-08-20T04:53:18Z",
  "keyword": "python"
}
```

Ticket `price` is the raw number Peatix reports in the ticket's currency (`currencyPrecision` 0 for JPY means whole yen). `seatsSold` vs `seatsMax` shows how full an event is.

### Notes

- Keyword search covers what Peatix's own search finds; there is no country filter (the upstream endpoint ignores one).
- `venue` is null for online events; check `online` / `locationType` instead.
- Deleted or unpublished events are skipped, not billed.
- The scraper honours Peatix's `robots.txt` (which explicitly welcomes well-behaved bots) including its `Crawl-delay: 1`.

### Use cases

Event marketing and competitor tracking, lead generation for sponsors and vendors, market research on the Japanese events scene, monitoring your own community's ticket sales across groups.

# Actor input Schema

## `searchKeywords` (type: `array`):

Keywords to search Peatix for (max 20). Each keyword is searched separately; results are de-duplicated by event id. Japanese, English or any language Peatix hosts events in.

## `eventUrls` (type: `array`):

Specific events to fetch: full https://peatix.com/event/<id> URLs or bare numeric ids (max 2000). Vanity <name>.peatix.com URLs are not accepted — open one in a browser and copy the peatix.com/event/... URL it leads to.

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

Stop after this many events have been pushed (1–10000). You are only charged for pushed events.

## `maxConcurrency` (type: `integer`):

Parallel requests (1–10). Requests to each host are additionally spaced ~1 s apart to respect Peatix's crawl-delay.

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

Proxy settings. Peatix answers datacenter IPs fine; leave empty unless you see blocks.

## Actor input object example

```json
{
  "searchKeywords": [
    "python",
    "スタートアップ"
  ],
  "eventUrls": [
    "https://peatix.com/event/5145560",
    "5145560"
  ],
  "maxItems": 100,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `events` (type: `string`):

Dataset items, one per Peatix event (name, dates, venue, tickets with prices, organizer, group, tags, 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 = {
    "searchKeywords": [
        "AI"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ardent_fork/peatix-events").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 = { "searchKeywords": ["AI"] }

# Run the Actor and wait for it to finish
run = client.actor("ardent_fork/peatix-events").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 '{
  "searchKeywords": [
    "AI"
  ]
}' |
apify call ardent_fork/peatix-events --silent --output-dataset

```

## MCP server setup

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

```

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/VpercK824h3pdF4Jy/builds/usDgvMlocbxtQZozO/openapi.json