Webhooks
Updated May 8, 2026
Webhooks are automatic HTTP notifications triggered by an event in an application. They enable immediate data transfer to other systems without the need for constant polling and are well-suited for integrations and workflow automations.
As an administrator, go to your account settings. Under the "Webhooks" menu item, you will find a list of existing webhooks and the option to add new ones.
Creating New Webhooks:
To create a new webhook, please click on the "Create Webhook" menu item. You can then give the webhook any name you like. This is solely for your orientation and has no further impact on the actual webhook.
Next, please specify for which category you want to receive the corresponding events.
Example:
Single Category: webinar.created → A webinar was createdMultiple Categories: webinar.created, webinar.deleted → Webinar created & deletedWildcard Categories: webinar.* → includes, for example, webinar.created, webinar.updated, webinar.deletedTo finalize the webhook setup, you must then add the HTTP endpoint address and save the settings.
Webhooks are sent JSON serialized.
Further information on JavaScript Object Notation can be found here in the Wikipedia article.
In the Webhook overview, you can immediately see if there have been any errors in the delivery of individual webhooks.
Failed webhooks will be retried for up to 24 hours.
Retries are exponentially delayed:First delivery: ImmediatelySecond: After two secondsThird: After four secondsFourth: After eight secondsFifth: After 16 secondsetc.17th delivery: After 24hFurther details on failed deliveries can be found by selecting the corresponding webhook. There you also have the option to manually re-trigger the delivery.
Urgent Security Notice:
Webhooks can be sent by anyone. To ensure that edudip is the sender, the signature must be verified. We use ECDSA for signing the data in the payload.
• Every webhook request contains the following relevant HTTP headers:
X-Edudip-Signature-Algorithm: The algorithm used for the signature (e.g., SHA256).
X-Edudip-Signature: The actual signature of the payload, required for verification.
• To verify the signature:
• Load the public key that belongs to our private key. We provide this public key.
• Hash the webhook's payload using the algorithm from theX-Edudip-Signature-Algorithm
-header to obtain the payload hash.
• Use the public key to compare the received signature (X-Edudip-Signature) with the hashed payload.
Click here to download the Public Key
