MeetPure Events

MeetPure Events connects your WordPress site to the MeetPure platform. It fetches your published events via the MeetPure API and displays them in a beautiful, responsive card grid. Individual events open in a full detail page — with cover image, date, location, description, speakers, agenda, and a CTA button — all without leaving your site.

Features

• Responsive event card grid with cover image, date badge, event type, and CTA button
• Full single event detail page: description, location, speakers, agenda
• Automatic page title and featured image taken from the event
• Configurable cards-per-row, event count, and section heading
• Support for past events toggle
• Flexible link routing: internal detail page or direct link to meetpure.events
• 5-minute transient cache to minimise API calls
• Theme-inheriting styles via CSS custom properties

Configuration

Go to Settings → MeetPure Events and fill in:

• API Token — Your MeetPure API token. For now, request one from support@meetpure.com and provide the exact Team ID configured in the plugin so the key is bound only to that team. The plugin rejects keys with write scope and validates team access via /auth/info.
• Team ID — The team whose events are displayed. The API key must be bound only to this Team ID.
• Events Per Page — Number of events requested per grid page (1–100, default 10).
• Single Event Page — Select the page that contains [meetpure_event] for individual event detail views.

Usage

Events Grid

Place the following shortcode on any page or post to display a grid of upcoming events:

[meetpure_events]

Available attributes:

• count — Override Events Per Page for this grid (1–100). Default: (from settings)
• title — Section heading. Pass title="" to hide it. Default: Events
• per_row — Cards per row on large screens (1–6). Default: 3
• include_past — Set to "true" to include past events. Default: false
• link_to — Where cards link: auto, internal, or external. Default: auto

• page_param — Query parameter used for pagination. Change only when multiple event grids appear on the same page. Default: meetpure_events_page

  link_to values:

• auto — Links to the Single Event Page if configured, otherwise to meetpure.events.

• internal — Always links to the local Single Event Page.
• external — Always links to meetpure.events.

Examples:

[meetpure_events]

[meetpure_events count="6" per_row="2" title="Upcoming Events"]

[meetpure_events include_past="true" title="All Events"]

[meetpure_events link_to="external"]

Single Event Detail

Add the following shortcode to a dedicated page to render a full event detail view:

[meetpure_event]

When accessed via ?meetpure_event=EVENT_ID in the URL (linked automatically from the grid), it displays the matching event. You can also hardcode a specific event:

[meetpure_event event_id="VoUfH"]

Available attributes:

• event_id — MeetPure event ID. Default: (read from URL query string)

Setting up Individual Event Pages

1. Create a new WordPress page (e.g. “Event”) and add [meetpure_event] to its content. Publish it.
2. In Settings → MeetPure Events, select that page under Single Event Page. Save.
3. Event cards in your grid will now link to yoursite.com/event/?meetpure_event=EVENT_ID.
4. The page title, featured image, and document title are automatically replaced with the event’s data.

External Services

This plugin connects to the MeetPure Events platform (https://meetpure.events) to fetch and display event information.

MeetPure Events API

What it is used for: The plugin retrieves your team’s published events and individual event details from the MeetPure Events platform API so they can be displayed on your WordPress site via the [meetpure_events] and [meetpure_event] shortcodes.

What data is sent and when:

• When the [meetpure_events] shortcode is rendered, the plugin sends an HTTP GET request to https://meetpure.events/api/v1/events containing: your API token (in the X-API-Key header), your team ID (in the X-Team-Id header), a requested page number and page size, a status filter (published), and optionally a start date to filter out past events. API responses are cached for 5 minutes using WordPress transients; no request is made while a valid cache entry exists.
• When the [meetpure_event] shortcode is rendered (or the single event detail page is loaded), the plugin sends an HTTP GET request to https://meetpure.events/api/v1/events/{event_id} containing your API token (in the X-API-Key header). This request is also cached for 5 minutes.
• No visitor/end-user data is collected or transmitted — only the site owner’s API credentials and the requested event identifiers are sent.

Service provider: MeetPure Events (https://meetpure.events)

• Terms of Service
• Privacy Policy