Public API quickstart

The MeraEvents Public API is a read-only API for approved partner and client integrations. Use it to read an organization's events, tickets, event details, registration fields, and successful registrations.

It does not create or update bookings, change attendee data, or perform check-in. Continue to use the MeraEvents dashboard for those actions.

Before you start

You need:

• An active MeraEvents organization
• Organization owner or admin access
• An API key with the scopes required by your integration
• A secure server or backend where the key can be stored

Keep API keys server-side. Do not place a MeraEvents API key in browser JavaScript, a mobile application, a public repository, screenshots, or client-visible logs.

Base URL

Production requests use:

https://api.meraevents.com/v1

If MeraEvents Support gives your integration a different environment URL, use that URL instead.

1. Create an API key

Open the API Keys page, choose New key, and select only the scopes your integration needs.

The complete secret is shown once. Copy it into your secret manager before closing the dialog.

2. List your organization's events

Replace YOUR_SECRET_TOKEN with your key:

curl --request GET \
  'https://api.meraevents.com/v1/events?status=active&limit=25' \
  --header 'x-api-key: YOUR_SECRET_TOKEN'

A successful response contains event records plus pagination information. This shortened example omits other event properties for readability:

{
  "data": [
    {
      "id": 501,
      "title": "Client Annual Conference",
      "status": "active",
      "startAt": "2026-09-10T03:30:00.000Z",
      "endAt": "2026-09-10T12:30:00.000Z"
    }
  ],
  "nextCursor": null,
  "hasMore": false
}

The real event response contains additional location, availability, media, category, and booking fields. Use the returned event id in event-specific endpoints.

3. Choose the next request

For event 501, common requests are:

Understand the two registration endpoints

The endpoints answer different questions:

• /custom-fields describes what the organizer configured: stable field IDs, labels, field types, choices, groups, requirements, and ticket applicability.
• /registrations returns what attendees submitted. Each answer includes a fieldId that can be matched to the field definition.

Always use fieldId for matching. Field names are useful for display but are not guaranteed to be unique.

Exact API reference

Use the interactive OpenAPI reference for the complete request parameters and response schemas, or download the OpenAPI JSON document. These guides explain the integration workflow; the OpenAPI reference is the field-level contract.