Sessionize Public Events Scraper

Sessionize Public Events Scraper

Scrape Sessionize public events, sessions, and speakers from any event ID, up to a million per run. Every row comes with the full session or speaker details, ready for CSV, JSON, Excel, or XML. No login or API key.

Sessionize's public API gives you event data, but you still need to write code, handle pagination, and shape the JSON. This reads the public event feed directly from an event ID and returns each session or speaker as one flat row. Filter by data type and cap the number of events per run.

Who uses it	What they scrape Sessionize for
Event organizers	Export their own event agenda and speaker list for a website or printed program
Conference attendees	Build a personal schedule from the sessions and speakers of an event they plan to attend
Developer relations teams	Monitor which topics and speakers appear across multiple Sessionize events
Market researchers	Analyze session titles and speaker bios to spot trends in a technical niche

What it does

This Actor collects sessions, speakers, or sessions enriched with speaker details from a Sessionize event ID and returns each one as a flat row.

• 📋 Sessions mode: one row per session with title, description, time, and room.
• 🎤 Speakers mode: one row per speaker with name, bio, and profile links.
• 🔗 Sessions with speakers: each session row includes the speaker details nested or flattened.
• 🔢 Max events cap: set a hard limit from 1 to 1,000,000 rows per run.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Sessionize data

📅 Build a conference agenda.

An event organizer enters their Sessionize event ID and exports all sessions with times and rooms to CSV for the event website.

🎤 Create a speaker directory.

A community manager scrapes the speakers dataset to list every speaker bio and profile link on a public page.

📊 Compare events over time.

A market researcher runs the Actor on several event IDs and compares session titles to see which topics are gaining traction.

🔔 Monitor speaker activity.

A developer advocate tracks when a known speaker appears in new Sessionize events by checking the enriched sessions dataset.

Why choose this scraper

	What you get
No API key	Reads the public Sessionize event feed without registration or OAuth
Flat rows	Every session or speaker becomes one row, ready for spreadsheets or databases
Three data types	Pick sessions, speakers, or sessions enriched with speaker details
Large runs	Collect up to a million events per run when you need the full agenda

How it compares

No other Store actor targets Sessionize the same way, so the honest comparison is with the alternatives teams actually weigh.

	Sessionize Public Events Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When Sessionize changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor with a Sessionize event ID and choose which data type to return. The max events cap stops the run after the number of rows you set. The Input tab lists every parameter.

A first run with the defaults:

{
 "eventId": "9otadjkk",
 "maxItems": 10
}

A larger pull:

{
 "eventId": "9otadjkk",
 "maxItems": 200
}

Pricing

Pay-per-result: $0.0085 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$0.85
1,000 results	$8.50
10,000 results	$85.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Sessionize Public Events Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Sessionize through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/sessionize-public-events-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check the event ID. It must be the public API ID, not the event slug or website URL. Also confirm the event is published and not private.

The run stops before collecting all sessions.

Increase the max events value. The default is 10, but you can set it up to 1,000,000.

I see speaker fields in sessions mode.

Switch the data type to sessions-with-speakers if you want speaker details. In sessions mode, only session fields are returned.

The dataset has nested JSON in some columns.

That is normal for fields like speaker list or custom properties. Use the JSON export or flatten the data in your own pipeline.

I get an error about invalid event ID.

Make sure the ID contains only letters and numbers, with no slashes or extra path segments. Copy it directly from the API URL.

FAQ

Question	Answer
Where do I find the Sessionize event ID?	Open the event's embed or API URL, for example https://sessionize.com/api/v2/9otadjkk/view/All. The ID is the part after /api/v2/ and before /view, here 9otadjkk.
Does this work for private or draft events?	No, the Actor reads only the public API endpoint. If the event is not published or is restricted, the run will return no data.
What is the difference between sessions and sessions-with-speakers?	Sessions returns one row per session with only session fields. Sessions-with-speakers returns the same rows but adds the speaker details for each session, either nested or flattened depending on the output.
Can I scrape multiple events in one run?	The input accepts one event ID per run. To collect multiple events, run the Actor once per ID or use a separate orchestrator.
What export formats are supported?	The dataset can be exported to CSV, JSON, Excel, or XML from the Apify platform.
Is there a rate limit?	The Actor reads the public Sessionize API, which does not publish strict rate limits for normal use. If you hit a limit, lower the max events or add a delay between runs.
Does the Actor handle pagination automatically?	Yes, it follows the API's pagination until it reaches the max events cap or the end of the data.
Can I get speaker social links?	The speakers dataset includes the profile links that Sessionize provides, such as Twitter, LinkedIn, or company website, when the speaker has filled them in.
What if the event has no sessions yet?	The run will finish with an empty dataset. Check the event ID and make sure the event is public and has published content.
Is this an official Sessionize integration?	No, this is an independent scraper that reads the public API. It is not affiliated with or endorsed by Sessionize.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Sessionize. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.