Webhooks

Webhooks let your application receive events from RemyPass when members, memberships, events, donations, and scans change. Create an endpoint under Integrations → Webhooks or through the public API, select the event types you need, and verify each signed POST request before processing it.

Getting started

1. Create a webhook subscription with an HTTPS endpoint
2. Choose individual events or whole resource categories
3. Copy the signing secret shown on creation and configure your receiver
4. Send a test delivery and check its result in delivery history

Follow subscription management for setup, testing, secret rotation, and replay. Delivery and security explains payloads, signature verification, retries, and delivery guarantees.

Event reference

The full catalogue contains 63 event types, including the existing scan.created event.

Reference	Coverage
Members	Creation, profile updates, status changes, and deletion
Memberships	Membership lifecycle, renewals, payments, refunds, and membership types
Events and tickets	Event lifecycle, visibility, registrations, check-ins, orders, payments, and refunds
Donations	Donations, refunds, disputes, recurring subscriptions, and campaigns
Scans	Successful and failed pass scans

Understanding events

A created event can describe a pending checkout. Membership activation and event registration/order confirmation indicate completed fulfilment. Free registrations also emit confirmation events. Payments and fulfilment are separate events.

updated contains changed_fields and previous_values for public resource fields. A dedicated lifecycle event can accompany an update. Internal bookkeeping and credentials are excluded. Deletion events contain the last resource snapshot. Permanent organisation deletion removes subscriptions, events and deliveries without generating deletion webhooks. Money amounts are integer minor units accompanied by a currency code. A lifecycle change can produce multiple events; consumers should deduplicate by event ID and allow for events arriving out of order.

Fetching related records

Use the public API to retrieve current records after receiving a webhook. Give your API key the matching read permission; webhook permissions alone do not grant resource access.

Webhook resource	List endpoint	Get endpoint
member	/members	/members/{id}
membership	/memberships	/memberships/{id}
membership_type	/membership-types	/membership-types/{id}
event	/events	/event-records/{id}
event_registration	/event-registrations	/event-registrations/{id}
event_order	/event-orders	/event-orders/{id}
donation	/donations	/donations/{id}
donation_subscription	/donation-subscriptions	/donation-subscriptions/{id}
donation_campaign	/donation-campaigns	/donation-campaigns/{id}
scan	/scans	/scans/{id}

The event payload ID identifies the event; the resource ID inside data identifies the record. Deletion events contain the last snapshot and the corresponding get endpoint then returns 404. Current resource responses can be newer than the webhook snapshot. Event API amounts use major currency units while webhook event snapshots use minor units; see querying and incremental sync.