Guide
A booking-system integration should pass one reliable event into the feedback workflow, then make the response easy to bring back into your product or operational tools.
Last reviewed: 19 September 2026
Create a follow-up when the appointment is complete. Include a stable external appointment ID, the completion time, and the customer information needed to send the request.
For a platform with many client businesses, also include the stable external account ID so each downstream account remains isolated.
Integrations fail and retry. Use an idempotency key when creating a follow-up so a network retry does not create a second customer request for the same appointment.
Use a test API key first. It lets an implementation team verify the payload and workflow without sending live customer email.
Read feedback and NPS through the API when a dashboard or report needs it, or receive signed webhooks as responses arrive. Keep external appointment and customer IDs with the data so a team can find the original interaction.
Verify webhook signatures against the exact request body and deduplicate events before processing them. A webhook receiver should be safe to retry as well.
The developer guide includes a working request, API response, and webhook model.
Read the developer guide