Read events, tickets, and event details

Find an event ID and retrieve its tickets, agenda, venues, discounts, and reference data.

Start integrations by listing the events owned by the API key's organization. The returned event ID is the stable identifier used by the other event endpoints.

List events

GET /v1/events
Required scope: events:read

Optional query parameters:

Parameter	Meaning
`status`	`active`, `inactive`, `completed`, `cancelled`, or `unpublished`
`startsAfter`	Return events starting at or after this ISO 8601 date and time
`startsBefore`	Return events starting at or before this ISO 8601 date and time
`search`	Case-insensitive search within event titles
`limit`	Events per page, from 1 to 100; default 25
`cursor`	The previous response's `nextCursor` value

Example:

curl --request GET \
  'https://api.meraevents.com/v1/events?status=active&startsAfter=2026-09-01T00%3A00%3A00.000Z&limit=50' \
  --header 'x-api-key: YOUR_SECRET_TOKEN'

Events are returned newest first. Continue while hasMore is true by sending the supplied nextCursor value in the next request.

Get one event

GET /v1/events/{eventId}
Required scope: events:read

Use this endpoint for the event's title, description, status, mode, dates, timezone, venue summary, virtual link, media, category, availability, and public URLs.

Nullable values mean the organizer did not configure that information or that the field does not apply to the event. Do not convert null into an invented value.

Read tickets

GET /v1/events/{eventId}/tickets
Required scope: tickets:read

This returns active ticket types in display order. Important fields include:

id: stable ticket ID used by other endpoint relationships
name and description: attendee-facing ticket information
price and currencyId: current ticket price and currency identifier
quantity, soldQuantity, and remainingQuantity: availability counters
minOrderQuantity and maxOrderQuantity: purchase limits
saleStartAt and saleEndAt: nullable sales window
soldOut: whether the ticket is currently sold out

Availability can change after a response. Treat it as a snapshot rather than a reservation.

Read agenda and venues

Request	Scope	Returns
`GET /v1/events/{eventId}/sessions`	`events:read`	Agenda days with sessions ordered by start time
`GET /v1/events/{eventId}/venues`	`events:read`	Event venues, addresses, coordinates, capacity, and active dates

An event can have multiple venues. Use isPrimary when you need its primary venue, and retain the venue id when storing a relationship.

Read discounts

GET /v1/events/{eventId}/discounts
Required scope: tickets:read

This endpoint returns active, unexpired discounts. appliesToTicketIds identifies the tickets eligible for each discount. An empty array should be interpreted according to the discount configuration, not as a reason to apply the discount to an unrelated event.

Read reference data

These endpoints use events:read:

Request	Purpose
`GET /v1/categories`	Active event categories
`GET /v1/subcategories?categoryId={categoryId}`	Active subcategories, optionally filtered by category
`GET /v1/countries`	Countries used by event and venue locations
`GET /v1/cities?countryId={countryId}&search={name}&limit=50`	Cities filtered by country or name

Reference IDs should be retained when another API response points to them. Names can change and should be treated as display values.

Next, use registration field definitions to understand the questions configured for an event. Then use registration data to retrieve successful bookings and their attendees.