Theme Data Formats

When an event is published to Ghost, Outpost injects structured data into the post’s code injection footer. Your Ghost theme can read this data to render event details, registration CTAs, countdowns, and more.

Code Injection JSON

Outpost adds a <script> tag with JSON data to every event post:

<script id="event" type="application/json">
{
  "date": "March 15, 2026",
  "event_day": "Sunday",
  "start_time": "10:00 am",
  "end_time": "11:00 am",
  "time_zone": "America/New_York",
  "time_zone_abbr": "EDT",
  "location": "Online",
  "platform_url": "",
  "registration_deadline": "March 14, 2026",
  "access": "anyone",
  "event_state": "registration_open",
  "outpost_ghost_event_id": "march-2026-webinar",
  "event_type": "webinar",
  "custom_fields": {
    "speaker_name": "Jane Smith",
    "session_type": "Workshop"
  }
}
</script>

The platform_url field is always empty. Everything in this payload is baked into the published Ghost post and is the same for every visitor, so a link meant only for registered members cannot go in it. Your theme cannot render a join link from this data. Outpost renders the join link itself, in the registration widget on the event post, and only for a member who has registered. Those members also receive the link in the event emails Outpost sends them.

Reading Data in Your Theme

JavaScript

document.addEventListener('DOMContentLoaded', function() {
  const eventScript = document.getElementById('event');
  if (!eventScript) return;

  try {
    const eventData = JSON.parse(eventScript.textContent);

    // Access standard fields
    console.log(eventData.date);           // "March 15, 2026"
    console.log(eventData.event_state);    // "registration_open"
    console.log(eventData.access);         // "anyone"

    // Access custom fields
    if (eventData.custom_fields) {
      console.log(eventData.custom_fields.speaker_name);  // "Jane Smith"
      console.log(eventData.custom_fields.session_type);  // "Workshop"
    }
  } catch (e) {
    console.error('Failed to parse event data', e);
  }
});

Handlebars (with inline script)

Since Handlebars templates run server-side and the JSON is in code injection (rendered client-side), you’ll typically use JavaScript to read the data and update the DOM:

{{!-- In your post.hbs or custom template --}}
<div class="event-details">
  <div class="event-date" data-event-field="date"></div>
  <div class="event-time" data-event-field="start_time"></div>
  <div class="event-location" data-event-field="location"></div>
  <div class="event-speaker" data-event-field="custom_fields.speaker_name"></div>
</div>

<script>
(function() {
  const eventScript = document.getElementById('event');
  if (!eventScript) return;

  const data = JSON.parse(eventScript.textContent);

  document.querySelectorAll('[data-event-field]').forEach(el => {
    const field = el.dataset.eventField;
    const value = field.split('.').reduce((obj, key) => obj?.[key], data);
    if (value) el.textContent = value;
  });
})();
</script>

Standard Field Reference

Field	Type	Example	Description
`date`	string	`"March 15, 2026"`	Formatted event date (uses site’s date format)
`event_day`	string	`"Sunday"`	Day of the week
`start_time`	string	`"10:00 am"`	Event start time
`end_time`	string	`"11:00 am"`	Event end time
`time_zone`	string	`"America/New_York"`	IANA timezone identifier
`time_zone_abbr`	string	`"EDT"`	Localized timezone abbreviation for the event date
`location`	string	`"Online"`	Event location/venue
`platform_url`	string	`""`	Always empty. The join link is not published in this payload. See Code Injection JSON.
`registration_deadline`	string	`"March 14, 2026"`	Registration cutoff date (or event date if not set)
`registration_deadline_iso`	string	`"2026-03-14T23:59:00-04:00"`	Registration cutoff as an ISO 8601 timestamp (empty when no explicit deadline is set)
`registration_end_time`	string	`"11:59 pm"`	Time the registration window closes (empty when not set)
`access`	string	`"anyone"`	Access level enum (see below)
`event_state`	string	`"registration_open"`	Current lifecycle state (see below)
`outpost_ghost_event_id`	string	`"march-2026-webinar"`	Unique event identifier (GUID/slug)
`event_type`	string	`"webinar"`	Event type key from manifest
`custom_fields`	object	`{...}`	Custom field values defined by manifest

Access Levels

The access field indicates who can register for the event:

Value	Description	Theme Behavior
`anyone`	All logged-in members (free and paid)	Show standard registration CTA
`free`	Free-tier members and above	Show registration CTA for logged-in users
`paid`	Only paid subscribers	Show upgrade CTA for free members

Example: Conditional Rendering by Access

const eventData = JSON.parse(document.getElementById('event').textContent);

if (eventData.access === 'paid') {
  // Show "Paid subscribers only" badge
  document.querySelector('.event-access-badge').textContent = 'Paid Subscribers Only';
  document.querySelector('.event-access-badge').classList.add('premium');
}

Event States

The event_state field reflects the event’s current lifecycle position:

Value	Description	Typical Theme Behavior
`registration_open`	Event is upcoming, registration is open	Show registration CTA
`registration_closed`	Deadline passed, event hasn’t happened	Show “Registration closed” message
`event_passed`	Event date/time has passed	Show “This event has ended” message

Example: State-Based UI

const eventData = JSON.parse(document.getElementById('event').textContent);
const ctaContainer = document.querySelector('.event-cta');

switch (eventData.event_state) {
  case 'registration_open':
    ctaContainer.innerHTML = '<button class="register-btn">Register Now</button>';
    break;
  case 'registration_closed':
    ctaContainer.innerHTML = '<p class="closed">Registration is closed</p>';
    break;
  case 'event_passed':
    ctaContainer.innerHTML = '<p class="past">This event has ended</p>';
    break;
}

Custom Fields

Custom fields defined in the manifest are nested under the custom_fields object. The keys match what you defined in your outpost-manifest.yaml:

# In your manifest
custom_fields:
  - key: speaker_name
    type: text
  - key: session_type
    type: select
    options: [Workshop, Keynote, Panel]

// In your theme JavaScript
const eventData = JSON.parse(document.getElementById('event').textContent);

if (eventData.custom_fields?.speaker_name) {
  document.querySelector('.speaker-name').textContent =
    eventData.custom_fields.speaker_name;
}

if (eventData.custom_fields?.session_type) {
  document.querySelector('.session-type').textContent =
    eventData.custom_fields.session_type;
}

Custom Field Value Types

Manifest Type	JSON Type	Example Value
`text`	string	`"Jane Smith"`
`textarea`	string	`"A longer description..."`
`number`	number	`60`
`select`	string	`"Workshop"`
`url`	string	`"https://example.com"`
`date`	string	`"2026-03-15"` (ISO format)
`toggle`	boolean	`true`
`image`	string	`"https://cdn.example.com/image.jpg"`

Event Defaults Partial

Outpost also injects messaging defaults and portal URLs via the outpost-event-defaults.hbs partial during theme processing:

<script id="outpost-event-defaults" type="application/json">
{
  "messaging": {
    "can_register": {
      "cta_text": "RSVP Now",
      "button_text": "Sign Up",
      "button_link": null,
      "show_signin": true
    },
    "registered": {
      "confirmation_text": "You're registered!",
      "link_pending_text": "The event link will be provided on this page before the event starts.",
      "show_calendar": true,
      "show_share": true,
      "show_cancel": true,
      "share_email_subject": "Join me at %EVENT_NAME%",
      "share_email_body": "I signed up for %EVENT_NAME% on %EVENT_DATE%, put on by %SITE_NAME%. Thought you might want to come too.\n\n%EVENT_DESCRIPTION%\n\n%EVENT_URL%",
      "cancel_text": "Cancel registration",
      "cancel_confirm_message": "Are you sure you want to cancel your registration?"
    },
    ...
  },
  "urls": {
    "signin": "#/portal/signin",
    "signup": "#/portal/signup",
    "upgrade": "#/portal/account"
  }
}
</script>

This provides:

Messaging: The site’s default text and display options for each registration state. There is one entry per state, and the states do not all use the same keys, so read the specific state you need rather than writing code that expects every state to look the same. The four sign-up states, can_register, login_required_free, login_required_paid and upgrade_required, each have cta_text, button_text, button_link and show_signin. The registered state has the confirmation and pending-link text plus the calendar, share and cancel options. The registration_closed state has a single message, and event_passed has a single hide_registration flag.
URLs: Ghost portal links for sign-in, sign-up, and account/upgrade

Reading Event Defaults

const defaultsScript = document.getElementById('outpost-event-defaults');
if (defaultsScript) {
  const defaults = JSON.parse(defaultsScript.textContent);

  // Access messaging for current state
  const messaging = defaults.messaging?.can_register;
  if (messaging) {
    document.querySelector('.cta-text').textContent = messaging.cta_text;
    document.querySelector('.cta-button').textContent = messaging.button_text;
  }

  // Access portal URLs
  const signInUrl = defaults.urls?.signin || '#/portal/signin';
}

Complete Theme Example

Here’s a complete example of rendering event data in a custom Ghost template:

{{!-- custom-webinar.hbs --}}
{{!< default}}

<article class="event-post">
  <header class="event-header">
    <h1>{{title}}</h1>
    {{#if feature_image}}
      <img src="{{feature_image}}" alt="{{title}}" class="event-image" />
    {{/if}}
  </header>

  <div class="event-meta" id="event-meta-container">
    <!-- Populated by JavaScript from code injection -->
  </div>

  <div class="event-content">
    {{content}}
  </div>

  <div class="event-registration">
    <!-- Outpost widget renders here -->
    <div class="outpost-ghost-event-container"></div>
  </div>
</article>

<script>
document.addEventListener('DOMContentLoaded', function() {
  const eventScript = document.getElementById('event');
  if (!eventScript) return;

  const event = JSON.parse(eventScript.textContent);
  const container = document.getElementById('event-meta-container');

  container.innerHTML = `
    <div class="event-datetime">
      <span class="event-date">${event.date}</span>
      <span class="event-time">${event.start_time} - ${event.end_time}</span>
      <span class="event-timezone">${event.time_zone}</span>
    </div>
    <div class="event-location">${event.location}</div>
    ${event.custom_fields?.speaker_name ? `
      <div class="event-speaker">
        <strong>Speaker:</strong> ${event.custom_fields.speaker_name}
      </div>
    ` : ''}
    ${event.event_state === 'event_passed' ? `
      <div class="event-status past">This event has ended</div>
    ` : ''}
  `;
});
</script>

Ghost Post Properties

In addition to code injection, Outpost sets these Ghost post properties:

Property	Value
`title`	Event name
`custom_excerpt`	Event description
`feature_image`	Event featured image (if uploaded)
`custom_template`	Template from manifest `post_template`
`tags`	Merged and deduplicated from three sources: the site’s Default Tags in Event Settings, the manifest’s `events.default_tags`, and the event type’s `tags`
`published_at`	Managed by Outpost: see Event Ordering

Tags are written once, when Outpost first creates the Ghost post for an event. Changing any of the three sources afterwards does not retag events that already have posts. These are accessible via standard Ghost Handlebars helpers:

<h1>{{title}}</h1>
<p class="excerpt">{{excerpt}}</p>
{{#if feature_image}}
  <img src="{{feature_image}}" />
{{/if}}

Event Ordering and Publish Dates

Ghost orders posts by publish date, so Outpost automatically adjusts event posts’ published_at values to keep publish-date order in sync with event-date order. The reorder runs every time an event is published or its date changes. Two consequences for theme authors:

Events listings need no special sorting. A collection or channel of event posts in Ghost’s default published_at desc order shows events in event-date order: the latest-dated event first, with past events sinking to the bottom. Don’t try to sort by event date yourself; the data isn’t available in listing context anyway.
Don’t display publish dates on event posts or event cards. Because Outpost manages these timestamps, {{date published_at}} on an event can show a date unrelated to when it was actually published. Hide the publication date in your event post template and on event cards, and show the event date from the code injection JSON instead:

{{!-- Event card: skip the usual {{date published_at}} line --}}
{{!-- Event post template: read the real date client-side --}}
<script>
  const meta = JSON.parse(document.getElementById('event').textContent);
  // meta.date, meta.start_time, meta.time_zone_abbr …
</script>

API Endpoint for Registration

The event widget uses Outpost’s plugin API for registration. If you’re building a custom registration UI:

// Register a member for an event
const response = await fetch(
  `/plugin-api/ghost-event/${apiKey}/${eventGuid}/subscribe/${memberUid}`,
  { method: 'POST' }
);

// Cancel registration
const response = await fetch(
  `/plugin-api/ghost-event/${apiKey}/${eventGuid}/unsubscribe/${memberUid}`,
  { method: 'POST' }
);

// Get calendar file
window.location.href = `/plugin-api/ghost-event/${apiKey}/${eventGuid}/calendar.ics`;

The apiKey is your site’s Outpost GUID (available in the outpost-api-key.hbs partial). The memberUid is the logged-in member’s Ghost UUID. Registration and cancellation requests are rate limited. One IP address can send 30 of these requests a minute to any one site, and a site can send 120 a minute in total, counted together with the contact form and the address form. Past either limit the request comes back with a 429 status and no registration is recorded, so a custom registration UI should check the response status and ask the reader to try again in a moment rather than assume the call worked. The calendar download, the call that reads an event’s registration state, and the %EVENT_CANCEL_LINK% cancel-registration link Outpost puts in event emails are not on this limit.

Getting Started

Autoresponder

Email Campaigns

Signup & Conversion

Members

Subscriptions & Pricing

Analytics & Reporting

Integrations

Advertising & Sponsorship

Events & Engagement

Settings

Developers

Code Injection JSON

Reading Data in Your Theme

JavaScript

Handlebars (with inline script)

Standard Field Reference

Access Levels

Example: Conditional Rendering by Access

Event States

Example: State-Based UI

Custom Fields

Custom Field Value Types

Event Defaults Partial

Reading Event Defaults

Complete Theme Example

Ghost Post Properties

Event Ordering and Publish Dates

API Endpoint for Registration

​Code Injection JSON

​Reading Data in Your Theme

​JavaScript

​Handlebars (with inline script)

​Standard Field Reference

​Access Levels

​Example: Conditional Rendering by Access

​Event States

​Example: State-Based UI

​Custom Fields

​Custom Field Value Types

​Event Defaults Partial

​Reading Event Defaults

​Complete Theme Example

​Ghost Post Properties

​Event Ordering and Publish Dates

​API Endpoint for Registration

Code Injection JSON

Reading Data in Your Theme

JavaScript

Handlebars (with inline script)

Standard Field Reference

Access Levels

Example: Conditional Rendering by Access

Event States

Example: State-Based UI

Custom Fields

Custom Field Value Types

Event Defaults Partial

Reading Event Defaults

Complete Theme Example

Ghost Post Properties

Event Ordering and Publish Dates

API Endpoint for Registration