How Peak Leverage connects to Peek Pro

Developers can configure webhooks via the API to perform POST HTTP requests to a designated URL whenever a 'booking_update' event occurs. This payload includes the booking UUID and status, allowing external systems to trigger custom marketing automations.

To prevent API throttling, integrations should aggressively cache static product data and only query the availability endpoints when a user actively attempts to select a date.

Peek Pro's API is built around the OCTO specification, which is an open industry standard for tour and activity connectivity. Developers should refer to the OCTO documentation for schema definitions.

API keys provide full access to read inventory and write bookings. They must be stored securely on the server-side and never exposed in client-side JavaScript or public repositories.

Peak Leverage uses native embeds when they preserve the required data capture and operator flow, and uses custom integration when more control is needed.

If the platform does not document a capability publicly, Peak Leverage does not claim it or rely on it.