Skip to main content

Setting up registration webhooks

How to automatically send registration data to your external systems in real-time

LDT avatar
Written by LDT
Updated this week

Registration webhooks allow you to automatically receive registration data in your external systems the moment someone signs up for your event. Instead of manually exporting data or waiting for updates, webhooks instantly notify your chosen systems whenever a new registration occurs.

πŸ’‘ Note: Webhooks require a secure HTTPS endpoint to receive data. If you're not familiar with webhook setup, consider working with your technical team or using a service like Zapier to get started.

Why use registration webhooks?

  • Real-time Data: Get notified instantly when registrations happen, not hours later.

  • Automated Workflows: Automatically update your email marketing platforms, CRM systems, or custom databases.

  • Reliable Integration: Every registration is captured and sent to your systems, even during high-volume periods.

  • Reduced Manual Work: No more CSV exports or manual data entry - everything happens automatically.

Common use cases

Registration webhooks are perfect for:

  • Adding new participants to your Mailchimp or Klaviyo email lists

  • Updating your CRM with fresh customer data

  • Sending registration info to Google Sheets or other tracking systems

  • Connecting with Zapier for automated workflows

  • Updating real-time registration dashboards

Setting up your first webhook

In the sidebar of your organiser dashboard, click: Settings, then: Integrations.

Then navigate to: Registration Webhooks

Adding Your Webhook URL

Before adding a webhook, make sure you have a system ready to receive the data. This could be a Zapier webhook, your website's API endpoint, or any service that accepts webhooks. Click: + Add URL

Enter your webhook URL. It must start with `https://` for security.
​

πŸ’‘ Note: Your webhook endpoint must respond within 30 seconds and should handle duplicate notifications gracefully.

What data gets sent?

When someone registers for your event, we'll send comprehensive registration data to your webhook URL, including:

- Participant Details: Name, email, phone number, address

- Event Information: Event name, ticket type, registration date

- Payment Data: Amount paid, currency, payment status

- Custom Answers: Responses to any custom registration questions

- Add-ons: Any merchandise or extras purchased

- Emergency Contacts: If collected during registration

All data is sent in JSON format for easy processing by your systems. You can add several webhook URLs if you need to send data to different systems. Each URL will receive identical registration data.

Editing/Deleting webhooks

Find the webhook you want to modify and click the three-dot menu (β‹―) next to the URL. From here you can edit or delete your webhooks:

Troubleshooting Common Issues

Below are a common list of errors and solutions:

Error: "Please enter a valid HTTPS URL"

Issue: Your URL doesn't use a secure connection.

Solution: Make sure your webhook URL starts with `https://`. We don't accept HTTP URLs for security reasons.

Error: "Not Receiving Webhook Data

Possible causes:

- Your webhook endpoint might be down or responding too slowly

- Your webhook URL might be incorrect

- Your server could be blocking incoming requests

Steps to fix:

1. Test your webhook URL directly in a browser

2. Check your server logs for incoming requests

3. Make sure your endpoint responds within 30 seconds

4. Verify your server accepts POST requests with JSON data

Problem: Missing Some Registrations

Webhooks are NOT sent for:

- Imported registrations (CSV uploads)

- Test registrations

- Refunded or cancelled registrations

Webhooks ARE only sent for:

- New, completed registrations

- Successful payment confirmations


Security Best Practices

  • HTTPS Required: All webhook URLs must use HTTPS to encrypt data in transit.

  • Validate Incoming Data: Always check that incoming webhook data is properly formatted.

  • Handle High Volume: Make sure your endpoint can handle multiple simultaneous requests during busy registration periods.

  • Consider Authentication: Add authentication tokens to your webhook URLs for extra security

Need More Help?

If you didn't find the answer you were looking for here or something didn't make sense, use the 😞 emoji at the bottom of the page, and you'll be able to message our team with your question or problem. We'll get back to you as soon as we can!

Did this answer your question?