● Live
DELIVERY 01 · SUCCEEDED
POST
your-endpoint.com/hooks/abc123
X-SmoothStay-Event
reservation.created
X-SmoothStay-Delivery
d_7CUHUG91
X-SmoothStay-Secret
••••••••••••
{
“uuid”: “1784403540405x749914698”,
“guest_name”: “Lucía Herrera”,
“check_in”: “2026-09-14T15:00:00.000Z”,
“check_out”: “2026-09-18T11:00:00.000Z”,
“unit”: { “name”: “Casa Foggy Bottom”, … },
“contact”: { “email”: “lucia@example.com”, … },
“access”: { “token”: “7CUHUG”, “link”: “…” }
}
Illustrative payload. Related records arrive nested as full objects.
Events As They Happen
Six events cover contacts and reservations. Each one fires a single POST the moment the record changes. No polling, no exports.
Any Tool You Already Use
Paste a webhook URL from Zapier, Make or Activepieces and build the rest of the workflow where your other tools already live.
Verified And Logged
Every request carries a shared secret over HTTPS. Failed deliveries retry, and the Logs tab shows the exact payload we sent.
Six Events, Contacts And Reservations
Pick only the events your workflow acts on, so your endpoint never receives traffic it will ignore. You can change the selection at any time.
✓
Each event sends one POST with the full record
✓
Guest Registration, manual entry and PMS sync all fire
✓
Deselect every event to pause delivery without disconnecting
contact.created
reservation.created
contact.updated
reservation.updated
contact.deleted
reservation.deleted
Get Connected In Minutes
Settings → Integrations → Set up webhooks. Four steps, and the first live event lands the same day.
You Will Know If A Delivery Fails, And Usually It Won’t
The risk with any automation is that it stops working quietly and you find out weeks later. Three things make sure that doesn’t happen here.
A blip doesn’t lose the event
If your receiving tool is briefly down or busy, we try again. Up to three attempts, for timeouts, rate limits and server errors.
A real break gets you an email
If your endpoint keeps failing we deactivate the webhook and email your admin, so a workflow that has stopped doesn’t go unnoticed.
You can see exactly what we sent
The Logs tab records every delivery with the status your endpoint returned, its raw response, and the payload itself. No guessing.
Building directly against the data instead of using an automation tool? The full reference covers events, payload shape, headers, retries and delivery guarantees.
Questions About Webhooks
Do I need to write code to use webhooks?
No. Most hosts connect an automation tool such as Zapier, Make or Activepieces: paste its webhook (catch hook) URL into SmoothStay and build the rest with the tool's own steps. Any endpoint that accepts POST requests over HTTPS works. You only need the technical reference if you're building directly against the data.
Do webhooks replace the Airbnb and PMS integrations?
No, they do different jobs. Airbnb Connect, Hospitable and OwnerRez bring reservations into SmoothStay; webhooks send SmoothStay records out to your other tools. Many hosts run both.
What happens if a webhook delivery fails?
We try each delivery up to three times. If your endpoint keeps failing, we deactivate the webhook and email your organization's admin. Fix it, send a successful test event and delivery resumes; events from the downtime aren't resent. To see what happened, open the Logs tab and click Debug on a delivery: you'll see the status your endpoint returned, its response and the exact payload we sent.
How do I verify and deduplicate webhook events?
Compare the X-SmoothStay-Secret header with your stored secret using a plain string match, and reject anything that doesn't match. Delivery is at-least-once and not ordered, so deduplicate on the X-SmoothStay-Delivery header and use X-SmoothStay-Timestamp to tell which update is newer.
Can I pause webhook events without losing my setup?
Yes: deselect all events. Disconnecting is permanent and deletes your endpoint settings, secret and delivery logs.
Put Your Reservation Data Where You Need It
Start free for 14 days. No credit card required.