Skip to content
MapleGatherMapleGather Help

Webhook event catalog reference

This page lists the M1 webhook event types published by MapleGather, when each fires, and a summary of the payload shape.

M1 event types

Section titled “M1 event types”

The following three event types are available at M1. Subscribe to them when creating a webhook endpoint.

Event type Fires when Primary payload entity
member.created A new member record is created in your organization (by application, bulk import, or API) Member
payment.succeeded A payment is successfully processed (membership payment, event registration, or manual payment) Payment
event_registration.confirmed A member’s registration for an event is confirmed EventRegistration

Payload shape

Section titled “Payload shape”

Every delivery is a POST with Content-Type: application/json. The envelope shape (WebhookEventPayload):

{
  "id": "evt_01J…",
  "type": "member.created",
  "apiVersion": "v1",
  "createdAt": "2026-06-20T14:32:00Z",
  "data": { ... }
}
Field Description
id Unique event id. Equals the X-Webhook-Delivery-Id header — deduplicate on this field.
type Event type string (e.g., member.created). Switch on this field to route events.
apiVersion API major version the payload is rendered against (e.g., "v1"). Matches the apiVersion you set on the endpoint.
createdAt When the event occurred. ISO 8601 UTC.
data Event-type-specific payload (the primary entity). Shape varies by type.

The data field contains the primary entity for the event type. Refer to the interactive API docs for the full schema of each entity.

Note: The admin delivery log (WebhookDelivery records) has its own eventType field — that is the log record’s field name, not the wire envelope field. The outbound envelope always uses type.

Test event type

Section titled “Test event type”

When you select Send a test event on a new endpoint, MapleGather dispatches a synthetic ping delivery. ping deliveries are excluded from production delivery metrics and do not appear in event-type filter counts.

Subscribing to events

Section titled “Subscribing to events”

Select the event types for an endpoint when you create it. To change subscriptions on an existing endpoint, use PATCH on the endpoint (webhook_endpoints_update) — you can update the event set, URL, or status without recreating the endpoint or losing your signing secret.

Section titled “Related”