Vagaro Webhooks

Outbound event notifications - HTTP POST requests to a merchant- registered HTTPS endpoint, not a WebSocket - fired whenever Appointments, Customers, Employees, Transactions, Form Responses, or Business Locations change, plus booking-widget interaction events (tab clicked, book now clicked, service searched, time slot clicked, form viewed/submitted, credit card capture viewed, booking completed, gift card/promo code applied, customer login, product added/removed from cart, widget loaded). Each event carries an id, createdDate, type, action (created/updated/deleted), and a typed payload; delivery follows a documented retry policy and endpoints can be signature-verified. A business may register up to 10 webhooks. Enabling APIs & Webhooks requires a request submitted from Settings > Developers > APIs & Webhooks and is limited to paid, non-trial accounts running Credit Card Processing on the computer, tablet, Pay Desk, or PayPro version; approval takes roughly five to seven business days.

API entry from apis.yml

apis.yml Raw ↑
aid: vagaro:vagaro-webhooks
name: Vagaro Webhooks
tags:
- Webhooks
- Events
- Real-Time
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://docs.vagaro.com/public/docs/introduction
properties:
- url: https://docs.vagaro.com/public/docs/introduction
  type: Documentation
- url: https://docs.vagaro.com/public/docs/webhook-events
  type: Documentation
- url: https://docs.vagaro.com/public/docs/appointment-events
  type: Documentation
- url: https://docs.vagaro.com/public/docs/securing-webhook-endpoint
  type: Documentation
- url: https://docs.vagaro.com/public/docs/retry-policy
  type: Documentation
- url: https://support.vagaro.com/hc/en-us/articles/29521637950875-Set-Up-Webhooks-From-Vagaro
  type: Documentation
description: Outbound event notifications - HTTP POST requests to a merchant- registered HTTPS endpoint,
  not a WebSocket - fired whenever Appointments, Customers, Employees, Transactions, Form Responses, or
  Business Locations change, plus booking-widget interaction events (tab clicked, book now clicked, service
  searched, time slot clicked, form viewed/submitted, credit card capture viewed, booking completed, gift
  card/promo code applied, customer login, product added/removed from cart, widget loaded). Each event
  carries an id, createdDate, type, action (created/updated/deleted), and a typed payload; delivery follows
  a documented retry policy and endpoints can be signature-verified. A business may register up to 10
  webhooks. Enabling APIs & Webhooks requires a request submitted from Settings > Developers > APIs &
  Webhooks and is limited to paid, non-trial accounts running Credit Card Processing on the computer,
  tablet, Pay Desk, or PayPro version; approval takes roughly five to seven business days.