Lan Party Publishing Standard (LPPS)
LPPS is entirely optional. Most organizers add and update events on lanlist by hand from their account page — that works perfectly and always will.
LPPS is an open JSON format for describing your organization, venues, and events on your own website. If you already maintain a calendar or API for your LAN series, LPPS gives lanlist a stable way to read it instead of retyping the same details.
Why use it?
- One source of truth — dates, venues, and ticket links stay on your site; lanlist can mirror them on a schedule.
- Less duplicate data entry — handy when you run many events or update often between parties.
- Community standard — the spec is public; other tools can consume the same feed.
How lanlist uses LPPS
- You host a version 2 JSON document that follows the published schema.
- In edit organizer, paste the feed URL into LPPS feed URL (if your account is linked to that organizer).
- When the site’s LPPS crawl job runs, lanlist imports matching venues and events (matched by stable IDs in the feed).
You can turn the feed off anytime by clearing the URL. Site moderators can also disable crawls for an organizer while keeping manual edits.
Manual listing is fine
Never used a JSON API? No problem. Use add event and add venue like everyone else. LPPS is a convenience for teams that already publish structured data — not a requirement to be listed on lanlist.
Related
- LPPS specification on GitHub
- Export to OrgaTalk LAN Party Database — archive past public LANs as TOML for a community PR (separate project)
- Account control panel