A webhook is a message Soventro sends to a web address you choose whenever something happens, such as a registration being confirmed. Your system can then update a CRM, a spreadsheet or a chat channel right away, without polling the API.
Add an endpoint
- Choose Integrations in the organization menu.
- Under Webhooks, enter the Address that will receive the messages. It must start with
https://, use port 443 or 8443, and be on the public internet. - Add a Description if you like.
- Under Events to send, tick the events you want. All are ticked to start with.
- Click Add endpoint.
- Copy the signing secret that appears and give it to whoever runs the receiving system. It's shown once.
You can have up to 10 endpoints.
Events you can send
registration.submitted: an application was submitted for review.registration.confirmed: a registration was confirmed.registration.waitlisted: someone joined a waitlist.registration.approved: an application was approved.registration.rejected: an application was declined.registration.cancelled: a registration was cancelled.registration.substituted: a registration passed to someone else.payment.received: a payment was recorded on a registration.refund.completed: a refund was completed.
Each message includes the registration as it was at that moment. Check-ins, hotel bookings and speakers don't send webhooks.
Test it
Click Delivery log and settings under the endpoint, then Send test event. Soventro sends a ping message, and the result appears in the Delivery log.
Signatures
Every message carries a Soventro-Signature header made with your signing secret. Your receiving system should check it, and refuse messages more than 5 minutes old, so nobody can fake or replay a message. The developer page has the exact method and sample code.
To change the secret, click Replace signing secret on the endpoint's page. The new secret is used straight away, so update your receiver at the same time.
Delivery and retries
- Your system must answer with a success code within 10 seconds. Anything else, including a redirect, counts as a failure. Redirects are never followed, so use the final address.
- A failed message is tried again, up to 8 attempts in all, about 1, 2, 4, 8, 16, 32 and 64 minutes apart. After that it's marked failed.
- A message can arrive more than once, and out of order. Each one has an event id your system can use to ignore repeats.
The delivery log
The endpoint's page lists every message with its status (delivered, retrying, failed or cancelled), the number of attempts, the last answer from your system, and the next try. Filter by status at the top. Open Body and attempts to see exactly what was sent.
Click Resend to send a message again. A resend has the same event id and content as the original.
The Integrations page shows each endpoint's last 7 days: delivered, waiting and failed.
Pause or remove an endpoint
On the endpoint's page, untick Send events to this endpoint and click Save. Anything still queued for it is cancelled. Click Delete… then Delete endpoint to remove it.
Who can manage webhooks
Owners and Admins.
Common questions
Can I use Zapier or Make? Yes, if your automation tool gives you an https address for incoming webhooks. Paste it as the endpoint address.
My endpoint keeps failing. Open its delivery log and read the last answer. Common causes are an address that redirects, a server that takes longer than 10 seconds, or one that isn't reachable from the internet.