Skip to Content
WebhooksQuickstart

Webhooks

Receive signed HTTPS notifications when supported changes occur in your organization. Use them to update an event website, membership system or other approved integration.

Quickstart

  1. Open Utviklere (Developers) in the organization dashboard as an admin.
  2. Create an endpoint using a public HTTPS URL you control. Each organization can have up to five endpoints. Private address literals and redirects are refused.
  3. Copy the signing secret when it is shown and store it on your server.
  4. Choose event types or whole families, then optionally restrict delivery to selected events or memberships.
  5. Send a test event, verify the signature and return a successful response.
  6. Enable the endpoint. New endpoints start disabled.

A lost signing secret must be rotated. Keep it separate from API bearer keys. Webhook availability has its own organization feature setting and requires an organization outside sandbox mode.

By configuring, enabling or using the integration, you accept the webhook terms of use.

Event catalogue

Choose the occurrences your integration needs, such as an event update or membership purchase. Whole-family subscriptions also receive new types added within that family. Entirely new families require a new subscription.

Browse event types and sample payloads.

The envelope

A notification wraps the affected resource in data.object. Use its occurrence ID for deduplication and its version to understand the contract.

Read the envelope reference.

Resource objects

Event, order, membership-pass and person objects each have their own reference. Nested fields are documented within their containing object.

Choose a resource reference.

Verify signatures

Verify the original request body before parsing JSON. Check the timestamp and compare signatures in constant time.

Implement signature verification and rotation.

Delivery and retries

Notifications can arrive more than once and out of order. Acknowledge durable receipt within 10 seconds and process slow work from a queue.

Read response rules, retries and recovery.

Test the integration

The dashboard’s Send testhendelse action sends webhook.test. It exercises reachability and signature handling.

Run through testing and troubleshooting.

Combine notifications and reads

Webhooks describe state when a change occurs. The Events API retrieves current event data. Use notifications to schedule a fresh read where appropriate and refresh listings periodically because time and inventory can change between notifications.

Build an event listing with the API.

Contract and changelog

The event catalogue, fields, samples and changelog are rendered from @stello/webhooks, the package used by the emitter. The webhook’s date-based version and the API’s /v1 path identify their respective contracts.

Read the webhook changelog.