Peek Pro
Peek Pro
Peek Pro
Peek Pro sends Mocca its bookings: who booked, for which event date, how much they paid and whether they checked in. Each booking becomes an Order and an Attendance record on the buyer’s Contact, and each product and time slot becomes an Event Series and Event Occurrence.
Fields
| Field | What to enter |
|---|---|
| Enable Peek Pro | Tick to switch the sync on |
| API Key | The Peek Pro API key. Required. |
| Webhook Secret | A long random value you choose. Needed only for instant updates; without it Mocca still syncs on its schedule. |
| Webhook Secret Header | The name of the request header Mocca also accepts the secret in. Leave empty for the default (X-Peek-Webhook-Secret). |
| Base URL | Leave empty unless your administrator gives you one |
How it stays up to date
- Instant updates: Peek Pro calls Mocca’s webhook address when a booking changes. Peek Pro does not sign its calls, so Mocca checks the secret instead: it is part of the webhook address Mocca registers in Peek Pro (
?token=), and Mocca also accepts it in the header named above. Treat the address, and any server log that records it, as a secret. - Daily safety net: every night Mocca re-reads the last 48 hours of bookings, so an update Peek Pro failed to deliver is picked up the next day.
To rotate the webhook secret
Peek Pro’s webhook address contains the secret, so a new secret means a new address:
- Enter the new Webhook Secret in Mocca Settings and click Save.
- Ask your administrator to register the webhook again. This adds a second subscription in Peek Pro with the new address.
- Delete the old subscription in Peek Pro. Until you do, Peek Pro keeps calling the old address and every call is refused.
The API Key rotates like any other key: paste, save, test.
Catch-up
When Peek Pro is switched back on after being off, Mocca re-reads the bookings it missed. See Switching a vendor off and on.