Go to the Tools<\/strong> tab and click\u00a0Integrations<\/strong><\/p>\n<\/li>\n Select Webhooks<\/strong><\/p>\n<\/li>\n Click Add<\/strong> to set up your webhook connection<\/p>\n<\/li>\n<\/ol>\n After clicking Add<\/strong>, you’ll be asked to configure several fields to define what kind of notifications you want to receive.<\/p>\n Attendee<\/strong> Meeting<\/strong> Session<\/strong> Sponsor<\/strong> Poll<\/strong> Example: Conte<\/span>nt Type<\/span>: <\/strong><\/p>\n Status<\/span>: <\/strong><\/p>\n Endpoint:<\/span>\u00a0<\/strong><\/p>\n Headers<\/span>: <\/strong>When your webhook sends data, you can tack on extra pieces of information called headers. These help the receiving system know who\u2019s sending data, verify it\u2019s genuine, or pass along small bits of \u201cbehind-the-scenes\u201d info.<\/p>\n How to use<\/span>:<\/p>\n Now, every time the webhook runs, it will include those named pieces of information along with the data payload, ensuring the receiving system can recognize, authenticate, or process your request correctly.<\/p>\n Target Attendees:<\/span> <\/strong>(for Attendee Webhooks only)<\/p>\n Apply filters to limit the webhook to specific attendees, like a particular ticket type, attendee type, language preference, etc.<\/p>\n Example: If you’re unfamiliar with webhooks, think of them as tools for automated data delivery. Instead of manually checking for updates, admins are notified as soon as new data is available. You can use webhooks to send these notifications to third-party platforms like Slack, Microsoft Teams, or Cisco. To get started, first create a webhook in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_crdt_document":"","footnotes":""},"doc_category":[56,18],"doc_tag":[],"class_list":["post-374","docs","type-docs","status-publish","hentry","doc_category-integration","doc_category-tools"],"year_month":"2026-04","word_count":453,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"Canapii","author_nicename":"Canapii","author_url":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/author\/administrator\/"},"doc_category_info":[{"term_name":"Integration","term_url":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/docs-category\/integration\/"},{"term_name":"Tools","term_url":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/docs-category\/tools\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/docs\/374","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/comments?post=374"}],"version-history":[{"count":1,"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/docs\/374\/revisions"}],"predecessor-version":[{"id":909,"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/docs\/374\/revisions\/909"}],"wp:attachment":[{"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/media?parent=374"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/doc_category?post=374"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/staging.knowledge-base.canapii.com\/index.php\/wp-json\/wp\/v2\/doc_tag?post=374"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![](\"https:\/\/staging.knowledge-base.canapii.com\/\/wp-content\/uploads\/2026\/03\/image-png-Jul-10-2025-03-41-52-1830-PM.png\")
<\/p>\n
\nSetting Up a Webhook<\/h4>\n
Event Types and Actions<\/span>:\u00a0<\/strong>Each webhook is associated with a specific event type and a corresponding action. The action determines when the webhook should activate based on activity.<\/p>\n\n
Notified when an attendee is created<\/strong>, updated<\/strong>, or deleted<\/strong>.<\/p>\n<\/li>\n
Notified when a meeting is booked<\/strong>, rescheduled<\/strong>, cancelled<\/strong>, or when an attendee\u2019s<\/strong> status is updated<\/strong>.<\/p>\n<\/li>\n
Notified when a session is created<\/strong>, booked<\/strong>, unbooked<\/strong>, joined<\/strong>, or watched<\/strong>.<\/p>\n<\/li>\n
Notified on sponsor-related activities such as product creation<\/strong>, deletion<\/strong>, update<\/strong>, view<\/strong>, link click<\/strong>, asset download<\/strong>, chat<\/strong>, or when marked as interested<\/strong>.<\/p>\n<\/li>\n
Notified when a poll is created<\/strong> or answered<\/strong>.<\/p>\n<\/li>\n<\/ul>\n\n
Event Type: Meeting<\/strong>
Action: Book<\/strong>
You’ll receive a notification whenever a meeting is booked.<\/p>\n<\/blockquote>\n\n
<\/span><\/li>\n<\/ul>\n\n
\n
\n
\n
\n
\n
Authorization<\/code><\/li>\nX-Client-ID<\/code><\/li>\nX-Signature<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n
\n
Bearer abcd1234<\/code> (your secret token)<\/li>\n67890<\/code> (your app\u2019s ID)<\/li>\nf1e2d3c4b5<\/code> (a checksum or signature)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n
Event Type: Attendee<\/strong>
Action: Create<\/strong>
Target: Sponsor ticket type<\/strong>
The webhook will notify you only when an attendee registers using the Sponsor<\/strong> ticket.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"