Setting up Webhooks in PheedLoop

If you are looking for information on PheedLoop's API, please visit: https://develop.pheedloop.com/

PheedLoop provides built-in support for webhooks, allowing event organizers to send real-time event data to external systems as events occur. Webhook functionality is available out of the box and is not restricted behind additional pricing tiers. Customers are responsible for creating and maintaining their own webhook endpoints and ensuring they function correctly.

Please note, PheedLoop's customer support team is unable to assist with endpoint configuration or troubleshooting outside of the PheedLoop platform.

What is a Webhook?

A webhook is a method that allows one system to automatically send data to another system in real time when a specific event occurs. Webhooks are commonly used to keep systems in sync without requiring manual exports or repeated data requests.

Instead of repeatedly polling an API for updates, a webhook sends information only when an event occurs. In PheedLoop, this means that when a supported resource (such as registrations, attendees, or check-ins) is created, updated, or deleted, a notification is sent to a customer-defined endpoint (URL). Webhooks are well suited for customers who integrate PheedLoop with external systems and want to automate workflows or keep data synchronized without manual intervention.

Setting up Webhooks in PheedLoop

Before creating webhooks in PheedLoop, your organization will need to pull the Event Code, Organization Code, and Webhook Secret from the Event Dashboard. Event Code and Webhook Secrets are unique across events, while the organization code is consistent. Once retrieved, this information must be set up on your endpoint to retrieve information.

Please note, the Webhook Secret should be treated as confidential and never shared publicly. If a Webhook Secret is suspected to be comprimised, it is recommended to reset the secret to maintain security.

To retrieve the webhook credentials

1. From the Event Dashboard, navigate to Advanced > Webhooks > Settings
2. Copy the Event Code, Event Code, Organization Code, and Webhook Secret
   1. Select Generate New Secret if you would like to reset your Webhook Secret. After resetting, you must update your webhook endpoint to use the new secret.

3. Use this information to set up your endpoint URL

   

Adding Webhooks to the Event Dashboard

Once your webhook is created, you can add them into the Event Dashboard.

1. From the Event Dashboard, navigate to Advanced > Webhooks > Webhooks

2. Above the Webhooks table, select Create

   

3. Under the Resource field, the asset the Webhook should be triggered for
   1. For example, attendees, registrations, check-ins
4. Under the Action field, select the specific behaviour that will trigger the webhook
   1. PheedLoop supports create, update, and delete actions.
5. Under the URL field, enter the endpoint

6. Select Save Changes

   

Reviewing Webhook Logs

As your webhooks are used, PheedLoop documents each action in the Event Dashboard. You can find these yourself by navigating to Advanced > Webhooks > Webhook Log.

This log shows every webhook delivery attempt and its outcome. The Response Status column shows if the Webhook has succeeded or failed. A 200 response indicates the webhook was delivered successfully. A 400-level response usually points to a configuration issue on the receiving endpoint, such as an incorrect or misspelled URL. A 500-level response indicates an error on the receiving server and is not related to PheedLoop.

The table below provides a breakdown of the columns displayed in the webhook log.