Registrations Straight to Your CRM

No. The connection is one-way by design: data leaves Quick Event, nothing is written in from outside. There is no inbound API key and no public write endpoint for bookings.

No. If your CRM can receive a webhook, point the destination straight at it. An automation layer is useful when you want to transform the payload, fan it out to several systems, or connect a CRM that has no webhook endpoint of its own.

Nothing is lost. The destination's cursor stays where it was, so delivery resumes at the first record it missed. After 20 consecutive failures the destination is switched off and the last error stays visible — turn it back on and the backlog is delivered.

Recompute the HMAC-SHA256 of <x-quickevent-timestamp>.<raw body> with your destination secret and compare it against the x-quickevent-signature header in constant time. Reject requests whose timestamp is far from the current time.

Yes — with the check-in point name, the direction, the device and whether it was a manual override. A CRM that knows who registered but not who actually turned up is only telling half the story.