What it is. Under Settings → Integrations, the owner or an admin adds an https address and chooses which events it gets. Piklo then sends a POST with a small JSON body to that address each time one of them happens. Use it with Zapier, Make or your own system. A business can have up to three.
The events.
- booking.created — a customer booked, or a held booking was paid
- booking.cancelled — a customer cancelled
- booking.rescheduled — a customer moved her time
- client.created — a booking made a new customer
- review.received — a customer gave stars
- membership.started — a membership was paid for and began
- ping — sent when you press "Send test"
Bookings, customers and memberships you create yourselves in the dashboard are sent too.
What a call looks like. Every call has the same shape: the event, when it happened, the business, and the data.
{
"event": "booking.created",
"occurred_at": "2026-11-02T14:03:11.204Z",
"organization_id": "5b0c…",
"data": {
"booking": {
"id": "e1f4…",
"status": "confirmed",
"seats": 1,
"starts_at": "2026-11-06T15:30:00+00:00",
"ends_at": "2026-11-06T16:15:00+00:00",
"services": ["Haircut"],
"staff": "Anna",
"location": "Main street",
"client_id": "77ad…"
}
}
}Customer details only when you ask for them. The customer's name, e-mail and phone, the price and a review's comment are only in the call when "Send customer details" is ticked on the webhook. Then data also carries client (name, email, phone) and price (amount_cents, currency). It is off unless you tick it, because what the receiver does with those details is your responsibility under GDPR.
Check the signature. Every call has the header X-Piklo-Signature: sha256=… — an HMAC-SHA256 of the raw body, made with the secret you were shown when you added the webhook. In Node.js:
const expected = 'sha256=' + crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const valid = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signatureHeader));
if (!valid) return response.status(401).end();Check it against the body exactly as it arrived, before it is parsed. The header X-Piklo-Event carries the event's name too.
Answering. Answer with any 2xx within 5 seconds. Anything else, or no answer, is tried again after 1, 5 and 30 minutes, and then marked as failed. After 10 failed deliveries in a row, Piklo turns the webhook off and says so in Settings; fix the address, send a test, and turn it on again. A call may arrive twice, and two calls may arrive out of order — use occurred_at, and the booking's id, to keep track.
What you can see. Each webhook shows its latest 50 deliveries with their status. Deliveries are deleted after 14 days.
Contact. Write to support@piklobooking.com.