Planned maintenance: Tue Dec 8, 11:30pm–12:30am ET (8:30–9:30pm PT / Wed 5:30–6:30am CET). Brief downtime possible (up to 15 minutes).

Status page
Skip to main content

How can we help?

Need help? Check out our documentation or contact support

Search

Introductions to webhooks in Bevy

  • Updated

Bevy webhooks push near-real-time JSON to an HTTPS URL you configure when subscribed records change. Use this page to learn how they work, then configure your endpoint and design a reliable receiver.

A Bevy webhook is a push from Bevy to a system you control. When a subscribed record is created or updated, Bevy sends a JSON POST to the HTTPS URL configured for your community. Your endpoint acknowledges the request, then processes the change (sync a CRM, trigger automation, or queue follow-up work).

Webhooks are not the public API. If you are still choosing between pulling data on demand and receiving pushes, start with Choose the public API or webhooks.

What Bevy sends

For each subscribed update type you enable, Bevy posts a defined JSON payload to your URL. Common types include attendees, events, users, chapters, chapter members, event people, and event survey entries — depending on which update toggles you turn on.

  • Delivery is near real time after a subscribed change. It is not a fixed clock interval you schedule.
  • The payload describes the record Bevy is notifying you about. It does not replace looking up extra fields through the public API when you need them.
  • Hard deletes are not announced as a separate webhook event. Soft-deleted records that are saved can still produce an update payload when that type is enabled.

For which record changes produce a delivery, see When are webhook payloads sent?. For field-level shape, see Webhook payloads.

What you need before you start

To receive Bevy webhooks you need:

  • An HTTPS endpoint that can accept POST requests from Bevy.
  • Optional but recommended: a shared secret (header name + value) so your receiver can verify that a request came from Bevy.
  • A decision about which update types to enable (for example attendee and event updates).

Admins set the URL, secret, and update types in the Admin Dashboard under Settings → General → Webhooks. Step-by-step setup is in Configure webhooks.

Note: By default, Bevy sends one record per POST. Some communities use bulk delivery, where one POST includes more than one record. Bulk mode is not a control in the Webhooks settings panel. If you receive more than one record in a single POST, your community is on bulk delivery — or contact Bevy Support to confirm. Design your receiver to handle both shapes if Support enables bulk for you.

What your receiver should handle

Bevy delivers updates for subscribed saves. Filtering which of those updates matter for your business is your responsibility:

  • Older events or chapters can still produce a payload when someone saves them after your webhook is enabled.
  • Build your own rules (timestamps, a processed-ID ledger, or business filters) so you process, ignore, or re-check records as needed.
  • Acknowledge the POST quickly, verify the secret when configured, and make processing retry-safe. Details live in Webhooks best practices.

Tip: If a payload is missing a field you need, call the public API for that record. Webhooks notify you that something changed; they are not a full data export.

Next steps

  1. Confirm webhooks are the right tool in Choose the public API or webhooks if you have not already.
  2. Follow Configure webhooks to set your URL, secret, and update types.
  3. Use When are webhook payloads sent? and Webhook payloads while you implement the receiver.
  4. Apply Webhooks best practices for verification, acknowledgment, and retries.