How do I install the Accelevents API skill?

Run npx skillmds@latest add swyxio/accelevents-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Accelevents API safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Accelevents API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Accelevents API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Accelevents API?

swyxio (@swyxio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Accelevents API by swyxio — Agent Skill

Name: Accelevents API
Rating: 4.2 (5 reviews)
Author: swyxio

File contents

Accelevents API — Speaker Management

API Endpoints

Base URL: https://api.accelevents.com/rest/host/event/{eventUrl}/speaker
Event URL for Europe: ai-engineer-europe-2026
API Key: stored as ACCELEVENTS_API_KEY secret

Authentication

Read (GET): Use Authorization: Bearer {key} header
Write (PUT): Use Key: {key} header — the Authorization: Bearer header returns 401 on write operations. This is an undocumented quirk.

GET speakers list

GET /rest/host/event/{eventUrl}/speaker?page=0&size=500
Headers: Authorization: Bearer {api_key}

Returns {"data": [...], "recordsTotal": N}. Each speaker has fields: speakerId, firstName, lastName, email, company, linkedIn, twitter, instagram, bio, title, imageUrl, allowEditSessions, allowOverrideDetails, etc.

PUT (update) speaker

PUT /rest/host/event/{eventUrl}/speaker/{speakerId}
Headers: Key: {api_key}, Content-Type: application/json
Body: { full speaker DTO }

CRITICAL: The PUT endpoint replaces the entire speaker record. Any fields omitted from the request body will be reset to null/false. You MUST:

Fetch the current speaker data first (via GET)
Merge your updates into the complete existing data
Send the full merged payload in the PUT request

Required fields: speakerId, firstName, lastName, email

Fields to always preserve if they exist: company, linkedIn, twitter, instagram, bio, title, pronouns, imageUrl, allowEditSessions, allowOverrideDetails, allowAttendeeAccess, moderator, showModerator, position

Successful response: {"type": "Success", "message": "Speaker updated"}

Bidirectional Sync Workflow

The sync script (src/pages/europe/source/_scripts/sync_accelevents.py) pulls data FROM Accelevents. But schedule.json may have richer data (from prior scraping) that Accelevents lacks. The correct workflow is:

Pull latest data from Accelevents API
Compare schedule.json vs API data to find gaps in both directions
Push UP any data that schedule.json has but Accelevents doesn't (LinkedIn, Twitter, company)
Pull DOWN any data that Accelevents has but schedule.json doesn't
Save snapshot after all updates

This ensures both systems have the superset of all known data.

Known Issues

Corrupted Company Names

The Accelevents portal has a UI bug where company fields get overwritten with single characters (e.g., "i", "d", "N"). This appears to be a keystroke capture issue in the portal UI. The sync script has a safeguard that rejects single-character company values and logs a [WARN].

Data Source of Truth

schedule.json is the website's source of truth (at src/pages/europe/source/schedule.json)
accelevents_speakers_latest.json is a raw API snapshot for reference/debugging only — not consumed by the website build
After schedule.json changes, run: python3 _scripts/export_csv.py
After photo changes, run: pnpm europe:source:sync-public

---name: accelevents-apidescription: Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.---# Accelevents API — Speaker Management## API Endpoints- **Base URL:** `https://api.accelevents.com/rest/host/event/{eventUrl}/speaker`- **Event URL for Europe:** `ai-engineer-europe-2026`- **API Key:** stored as `ACCELEVENTS_API_KEY` secret### Authentication- **Read (GET):** Use `Authorization: Bearer {key}` header- **Write (PUT):** Use `Key: {key}` header — the `Authorization: Bearer` header returns 401 on write operations. This is an undocumented quirk.### GET speakers list```GET /rest/host/event/{eventUrl}/speaker?page=0&size=500Headers: Authorization: Bearer {api_key}```Returns `{"data": [...], "recordsTotal": N}`. Each speaker has fields: `speakerId`, `firstName`, `lastName`, `email`, `company`, `linkedIn`, `twitter`, `instagram`, `bio`, `title`, `imageUrl`, `allowEditSessions`, `allowOverrideDetails`, etc.### PUT (update) speaker```PUT /rest/host/event/{eventUrl}/speaker/{speakerId}Headers: Key: {api_key}, Content-Type: application/jsonBody: { full speaker DTO }```**CRITICAL: The PUT endpoint replaces the entire speaker record.** Any fields omitted from the request body will be reset to `null`/`false`. You MUST:1. Fetch the current speaker data first (via GET)2. Merge your updates into the complete existing data3. Send the full merged payload in the PUT requestRequired fields: `speakerId`, `firstName`, `lastName`, `email`Fields to always preserve if they exist: `company`, `linkedIn`, `twitter`, `instagram`, `bio`, `title`, `pronouns`, `imageUrl`, `allowEditSessions`, `allowOverrideDetails`, `allowAttendeeAccess`, `moderator`, `showModerator`, `position`Successful response: `{"type": "Success", "message": "Speaker updated"}`## Bidirectional Sync WorkflowThe sync script (`src/pages/europe/source/_scripts/sync_accelevents.py`) pulls data FROM Accelevents. But schedule.json may have richer data (from prior scraping) that Accelevents lacks. The correct workflow is:1. **Pull** latest data from Accelevents API2. **Compare** schedule.json vs API data to find gaps in both directions3. **Push UP** any data that schedule.json has but Accelevents doesn't (LinkedIn, Twitter, company)4. **Pull DOWN** any data that Accelevents has but schedule.json doesn't5. **Save snapshot** after all updatesThis ensures both systems have the superset of all known data.## Known Issues### Corrupted Company NamesThe Accelevents portal has a UI bug where company fields get overwritten with single characters (e.g., "i", "d", "N"). This appears to be a keystroke capture issue in the portal UI. The sync script has a safeguard that rejects single-character company values and logs a `[WARN]`.### Data Source of Truth- **schedule.json** is the website's source of truth (at `src/pages/europe/source/schedule.json`)- **accelevents_speakers_latest.json** is a raw API snapshot for reference/debugging only — not consumed by the website build- After schedule.json changes, run: `python3 _scripts/export_csv.py`- After photo changes, run: `pnpm europe:source:sync-public`

Frequently asked questions

Accelevents API