Peatix Events Scraper

Scrape events from Peatix, 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.

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

Output

One dataset item per event:

{
  "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.

Speed, cost and timeouts

Requests to Peatix are paced at about one per second (its robots.txt crawl-delay), so a run delivers roughly 50 events per minute regardless of maxConcurrency: 100 events take about 2.5 minutes, 500 events about 10 minutes, 2,000 events about 40 minutes. Set the run timeout to at least 2 seconds per event you ask for. The actor runs in 1 GB of memory by default (peak use is about 320 MB at 500 events), so platform compute for a 500-event run is around 0.2 compute units.

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.