Webhook events
The nine events a webhook can subscribe to, what each is called on screen, and exactly when Ovante sends it.
Pro
These are the events a Zapier, Make or custom webhook connection can subscribe to. The type is what arrives in the payload's type field and the X-Ovante-Event-Type header; the label is what Events to send shows.
| Type | Label | Sent when |
|---|---|---|
registration.created | Attendee registered | A ticket with a holder is created, once per ticket. Also when someone names a ticket that had no holder. |
attendee.checked_in | Attendee checked in | A guest is checked in, at the door or by hand |
attendee.checkin_undone | Check-in undone | A check-in is undone |
registration.revoked | Attendee revoked | A ticket with a holder is set to Not going, without a refund |
order.completed | Order completed | An order lands paid or free, once per order |
order.refunded | Order refunded | A ticket on an order is refunded, once per order. Also an order with no tickets, such as a gift alone, when it's refunded. |
donation.received | Donation received | A gift is recorded: a donation at checkout or by hand, a sponsorship, a journal ad, a card-fee cover, a paid pledge, or the part of a ticket's price above its value |
contact.created | Contact created | A registration adds a new person to your contacts |
contact.updated | Contact updated | A registration changes a contact: a name, a total, the last event |
What every event follows
- Requests wait. Nothing about a request is sent until you approve it. Approving sends
registration.createdfor each named ticket, andorder.completed. A declined request sends nothing. - Unnamed tickets wait. A ticket nobody has named belongs to the buyer's order: it's in
order.completed, but has noregistration.createduntil someone names it. - Only registrations change contacts.
contact.createdandcontact.updatedfire only when a registration caused the change. Your edits on the People page, merges and imports send nothing. - A refund isn't also a Not going. A refunded ticket sends
order.refunded, neverregistration.revokedas well. - Order events come once.
order.completedandorder.refundedare sent once per order, and carry the whole order, every ticket included. - Promised money waits. A sponsorship or ad marked Not paid yet sends
donation.receivedwhen it's marked paid.
- When
- You approve a request
- Then
- Your integrations hear about it then, as a new registration for each named ticket and one completed order, as if it had been bought that moment.
- When
- A guest ticket has no name and no email
- Then
- It stays on the buyer's order as an unnamed ticket, carrying the buyer's name, email and phone so the confirmation and the door have something. It makes no contact and sends nothing to integrations until you name it.
- When
- You edit, merge or import contacts
- Then
- Nothing goes to your CRM or webhooks. Only contact changes that a registration makes are sent.
Good to know
- Only send contacts who opted into marketing holds back
registration.created, both check-in events and both contact events for anyone who hasn't opted in or has unsubscribed. Orders, refunds, gifts andregistration.revokedalways go. - A connection subscribes to at least one event.
- Salesforce and ChabadOne pick their events from their own switches; you don't tick them.
Was this helpful?
Related
PayloadsEvery webhook is one JSON envelope with the event's id, type and time, and a data object shaped for its kind: a ticket, an order, a gift or a contact.Send events to a webhookOvante posts a signed JSON message to your HTTPS endpoint each time an event you picked happens, retries what fails, and logs every delivery.What Ovante sends, and what staysRegistrations, check-ins, orders, refunds, gifts and the contact changes they cause go out. Your own edits, merges and imports stay in Ovante, and so do requests until you approve them.Use Zapier or MakeZapier and Make connections are webhooks with their own cards. They send the same events and payloads, need no signature check, and turn off when the hook is deleted.