The API behind the Gomry dashboard.

REST over HTTPS, resource-specific API keys and webhook notifications for supported Gomry activity.

Build an integration that reads your events or contacts, or creates records within the permissions you grant. Your team develops that connection to Gomry’s existing platform; the API is not a commissioned ticketing-development service.

Get API keys Read the docs

events.tswebhooks.ts

// List your events. Same endpoint the dashboard uses.
const res = await fetch(
  "https://www.gomry.com/api/v1/events?page=1&page_size=20",
  { headers: { "X-API-KEY": process.env.GOMRY_API_KEY } }
);
const { data, pagination } = await res.json();

// Attendees for the first event.
const attendees = await fetch(
  `https://www.gomry.com/api/v1/events/${data[0].id}/attendees`,
  { headers: { "X-API-KEY": process.env.GOMRY_API_KEY } }
).then(r => r.json());

Why it matters

One API, the dashboard included.

The API covers spaces, events, experiences, recurrences, ticket classes, attendees, contacts, lists, forms, applications, payments and custom fields. Keys are created in Organization Settings → API Keys.

Auth and scopes

API keys sent in the X-API-KEY header. Each key carries a scope map: none, read or write per resource. Any language over HTTPS.

Webhook delivery choices

Use signed webhook subscriptions with retries for supported registration and form-response events, or legacy organization webhook URLs with a different payload and delivery behavior.

Pagination and limits

Paginated list endpoints return page information. Check each endpoint’s response limits. The rate limit is 60 requests per 10 seconds per API key, with the same budget per IP address. Responses carry RateLimit headers, and a 429 includes Retry-After.

Choose how your systems receive updates.

Configure notifications around the Gomry activity your integration needs. The webhook subscription API and the legacy dashboard URL settings have different event types, payloads and delivery rules.

Signed webhook subscriptions

Create subscriptions through the API, or let Zapier create them for its instant triggers. Choose registrations through checkout or form-response events, with an event or form filter where supported.

Payloads include a stable event ID. Delivery headers carry an HMAC-SHA256 signature. Timeouts, network errors, and 429 or 5xx responses trigger retries with backoff. Other 4xx responses do not. Events can arrive more than once or out of order.

Legacy organization webhook URLs

For existing setups, add HTTPS URLs in Organization Settings → API Keys → Webhooks. Each URL receives the organization’s supported legacy payment, subscription and form events.

This path uses legacy payloads without signatures or retries. Before acting on sensitive payment data, your receiver confirms the payment against the API.

Send registrations to your existing CRM

If you want attendees who register through checkout added to your CRM, your developer provides an HTTPS receiver, verifies subscription signatures and maps attendee fields to the CRM’s API. The integration must handle repeated deliveries and define which records to create or update. Setting a webhook destination does not itself create a continuous synchronization.

Webhook delivery and setup

Reference

A few of the calls you'll use.

Method	Endpoint	Purpose
GET	/api/v1/events	List your events, paginated.
POST	/api/v1/events	Create an event.
GET	/api/v1/events/:id/attendees	Attendees for an event, with ticket status.
GET	/api/v1/events/:id/ticket-classes	Ticket classes with price and capacity.
GET	/api/v1/payments	Payments across the organization.
POST	/api/v1/contacts	Create a contact.