Publish Your Events

You publish on your own website — we copy it

You don't publish events on this site. Instead, you publish them on your own website, and we automatically copy (or "scrape") them from there on a regular schedule. If an event isn't on your website, it can't appear here.

What we need

Because we copy your events from your own website, each event on your site should clearly show:

  • the event's title
  • the date and time (start, and end if you have one)
  • where it takes place
  • what it costs (or that it's free)
  • a short description
  • a link to the event's page that we can send people to
  • an image, if you have one

If you want the exact field-by-field details, see How to Consume Our Data. The methods below are different ways of making sure your website shows this information in a form we can read reliably.

Choose a publishing method

Ordered easiest-adoption-first. Each method is labeled Works today if it already runs against real partner data with no new code, or Proposed — not yet built if it's part of the multi-pronged strategy but doesn't exist yet. Picking a proposed method today gives you nothing to act on immediately — see the "what you can do now" note in each of those entries.

C. iCalendar feed

Works today

Harmonizes with: the registered ical adapter (partner_scrape/adapters/ical.py).

If you already publish an .ics calendar feed (RFC 5545 — many calendar plugins, including The Events Calendar, expose one at a URL like ?ical=1), give us the feed URL and we can start ingesting it unchanged. This costs us nothing new to build — it's the lowest-friction option on this page. Recurring events (an RRULE) are expanded into individual occurrences automatically, bounded to 180 days or 52 instances so an unbounded rule can't produce unbounded output.

What you can do now: send us your .ics URL via the contact form.

A. .well-known discovery pointer

Proposed — not yet built

Would join: a new discovery step reading a small pointer file at a .well-known path (the same pattern as security.txt or llms.txt) that names the URL of your real feed — your .ics, your JSON-LD sitemap, or a schema-E JSON file below — and hands it to whichever existing adapter matches. Not a new event format; a discovery pointer to one of the formats above.

No code reads a .well-known pointer today. This method is not yet available to act on — it's listed here so you know it's part of the plan.

D. OpenActive feed

Proposed — not yet built

Would join: a new openactive adapter type (not yet registered).

OpenActive is a real, purpose-built open-data standard for "opportunity data" — the same term we use — built on schema.org with the RPDE (Realtime Paged Data Exchange) feed format. It's the most domain-appropriate standard here, but the heaviest to adopt, and no adapter reads it yet. Flagged as a stretch goal for a partner who already publishes an OpenActive feed elsewhere.

E. Our own JSON in our schema (universal fallback)

Proposed — not yet built

Would join: a new, small adapter type reading a partner-hosted JSON file directly (not yet registered).

For an organization with no calendar feed and no CMS plugin: host a JSON file at a documented path in the same schema documented on /data-access, and reference it from the .well-known pointer above (A) once that exists. This guarantees every partner has at least one option, even with the simplest possible site. No adapter reads this today.

Not sure which to pick?

If you want something we can start using immediately: already have a calendar feed? Send us the .ics URL (C). Building or updating event pages? Add Event JSON-LD and list those pages in your sitemap (B) — the same extraction we already run today, at our highest trust tier. Everything else on this page (A, D, E) is part of the roadmap, not something to build against yet. Questions, or ready to get started? Reach out via the contact form.