AgendaForge AgendaForge mark

Public API integration

AgendaForge + Embed feeds

Put your live AgendaForge agenda and speaker lineup on your own event website — fed straight from the source.

AgendaForge embed feeds publish your event's sessions, speakers, and agenda as public JSON that you render on your own website or CMS — so the lineup on your marketing site is the same lineup you're building in the dashboard, not a copy you keep forgetting to update. Change a session time, swap a keynote, or confirm a new speaker inside AgendaForge, and the feed reflects it on the next fetch; your site reads from one source of truth instead of a stale HTML table someone pasted in three weeks ago. There are three feeds — sessions, speakers, and the full agenda — each scoped to a single event by a per-event embed token, so a feed only ever exposes the event you intend to publish. The embed wizard walks you through picking what to show and hands you a snippet to drop in. It's genuinely live today: real public endpoints, real tokens, real data your developer or your CMS can fetch on every page load.

Capabilities

What the Embed feeds integration does.

  • Publishes three public JSON feeds per event — sessions, speakers, and the full agenda — so your website can render your real lineup instead of a hand-maintained copy.
  • Scopes every feed to a single event with a per-event embed token, so a published feed only ever exposes the event you chose to make public.
  • Reflects your dashboard changes at the source: reschedule a session or confirm a speaker, and the feed serves the updated data on the next fetch.
  • Walks you through setup with an embed wizard that lets you pick which feed to expose and generates a ready-to-paste snippet.
  • Works with any stack — your developer fetches the JSON directly, or you drop the wizard's snippet into your CMS or page template.

Triggers

What fires, and what happens.

Sessions feed

Serves the event's sessions as JSON — titles, times, tracks, rooms, and types — for rendering a live schedule on your own site.

Speakers feed

Serves the event's speaker lineup as JSON — names, bios, and details — so your speakers page stays in sync with the dashboard.

Agenda feed

Serves the full agenda as JSON, combining sessions across tracks and rooms into the structure your front end needs to render a run sheet.

Setup

Connect it in minutes.

  1. Open the embed wizard for your event

    In your event, head to the embeds area and launch the wizard. It shows the available feeds — sessions, speakers, and agenda — and lets you choose which one you want to expose on your site.

  2. Generate the feed and its embed token

    Pick a feed and the wizard produces a public, per-event endpoint backed by an embed token scoped to that single event, plus a snippet you can copy. The token keeps the feed tied to the one event you're publishing.

  3. Render the JSON on your site or CMS

    Paste the wizard snippet into your page or template, or hand the feed URL to your developer to fetch and render directly. From then on, the page reads live data from AgendaForge on each load.

Good to know

Today the feeds are JSON only. That means you render them yourself — your developer fetches the JSON, or you use the wizard's snippet — rather than dropping in a fully styled, ready-made widget. An iCal calendar feed and styled drop-in HTML embeds are on the way, but they are not shipped yet, so don't plan around them. If you want a pixel-perfect schedule on your site right now, you (or your CMS) own the markup; AgendaForge owns the data.

Questions

Embed feeds, answered.

Q.01 What can I actually embed on my own website?
Three public JSON feeds for the event you choose: sessions, speakers, and the full agenda. You fetch the JSON and render it on your own site or CMS, so your published schedule and speaker list stay in sync with what you build in the AgendaForge dashboard.
Q.02 Are these styled HTML embeds I can just paste in?
Not yet. The feeds are JSON today, so you render the markup yourself — directly via your developer, or using the snippet the embed wizard generates. Styled drop-in HTML embeds and an iCal feed are on the way but are not shipped, so plan to render the JSON for now.
Q.03 How is each feed kept to one event?
Every feed is scoped by a per-event embed token. The endpoint only ever returns data for the single event that token belongs to, so publishing a feed for one event never exposes another event's sessions or speakers.
Q.04 Does the feed update when I change my schedule?
Yes. The feeds read from your live event data, so when you reschedule a session, change a room, or confirm a speaker in AgendaForge, the feed serves the updated JSON on the next fetch — no manual re-publishing of your website's schedule required.
Q.05 Do I need a developer to use embed feeds?
It helps but isn't strictly required. The embed wizard generates a snippet you can paste into many CMS setups, but because the feeds are JSON, anything beyond the basics — custom styling or layout — is rendered by you, so a developer makes richer, branded schedules much easier.

Integration reviewed July 2026. See the API reference for webhook and Zapier details.

Run your event with Embed feeds wired in.

Invite-only while we onboard early partners. Tell us about your event and we'll bring you in — white-glove, no training course required.

Access request · Backstage

Get on the list.

We onboard a few teams at a time and reply personally. Tell us about your show.

We reply from the booth · No spam, ever