Event Agenda Sessions: Conference Schedule Export (iCal)

What it does. Give it one or more public event agenda addresses (for example https://ossna2025.sched.com, or just ossna2025) and get every session on the published agenda as a clean table: title, start and end time, track, room and a link to the session page. Works with public Sched event agendas. Good for building conference calendars, event discovery apps, or planning which sessions to attend.

Input (from .actor/input_schema.json)

• events: agenda addresses or event names, up to 50 per run
• date: only sessions on one UTC day (YYYY-MM-DD)
• category: only one track or session type, as the organizer names it
• query: keyword in the session title
• maxItems: max sessions per event (default 1,000)

Output fields event, eventName, sessionId, title, start, end (ISO 8601 UTC), category, location, url.

Free status rows (not charged): invalid-input, not-found, not-available, no-results, api-error, free-plan-limit, charge-limit-reached.

Example (the build's prefill) Input: {"events":["ossna2025"]} returns about 376 sessions from Open Source Summit North America 2025.

What is not included

• No attendee data of any kind. Sessions only.
• No speaker names. Names printed in session titles are removed before anything is stored or returned; open the session link to see who is speaking.
• No session descriptions (they are the speakers' and organizers' own writing).
• Any email or phone number found in a field is removed.

Data source and compliance

• Not affiliated with, endorsed or sponsored by Sched LLC or any event organizer.
• Reads only the public iCal export (/all.ics) a published agenda offers without login. It is an unofficial export: it can change or stop without notice, and this Actor may stop working for some or all events as a result. Private or unpublished events return a free not-found row.
• Gentle on the source: one feed at a time, at least 10 seconds apart, a 60-second pause after any rate-limit or server error, and an identifying User-Agent. Large agendas can take 20 to 30 seconds per event.
• Each event feed is fetched at most once every 12 hours per Apify account: results are kept for 12 hours in a key-value store named event-agenda-sessions-cache in your account, and later runs inside that window reuse it. Delete that store to clear it.
• Organizer opt-out: an organizer can ask for their event to be excluded; it is then blocked permanently and returns a free not-available row. Removal requests are handled within 30 days.
• Free-plan accounts get up to 100 sessions per run.
• Removal requests: support@lepidata.com

Pricing. Pay per session returned, flat on every plan, no start fee. Free status rows are never charged.