# Event Agenda Sessions: Conference Schedule Export (iCal) (`lepidata/event-agenda-sessions`) Actor

Export the public session agenda of a conference from its public iCal export: titles, times, tracks, rooms and session links. Sessions only, no attendees, no speaker names. Works with public Sched event agendas; not affiliated with Sched.

- **URL**: https://apify.com/lepidata/event-agenda-sessions.md
- **Developed by:** [Lepi Data](https://apify.com/lepidata) (community)
- **Categories:** Marketing, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.10 / 1,000 session returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## 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.

# Actor input Schema

## `events` (type: `array`):

Event agenda addresses or event names, e.g. https://ossna2025.sched.com or ossna2025. Up to 50 per run. Unknown or private events get a free not-found row.

## `date` (type: `string`):

Only sessions starting on this UTC date (YYYY-MM-DD).

## `category` (type: `string`):

Only sessions in this track, as the organizer names it (case-insensitive), e.g. Keynote Sessions.

## `query` (type: `string`):

Only sessions whose title contains this text.

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

Stop after this many sessions per event.

## Actor input object example

```json
{
  "events": [
    "ossna2025"
  ],
  "maxItems": 1000
}
```

# Actor output Schema

## `items` (type: `string`):

All rows from this run.

# 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 = {
    "events": [
        "ossna2025"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lepidata/event-agenda-sessions").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 = { "events": ["ossna2025"] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lepidata/event-agenda-sessions"
        }
    }
}
```

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/8mpP4kiUnO2YNHgzr/builds/6r0lKsgwsc0KkBngQ/openapi.json