Webhooks
Phase 3.2 — coming soon
Webhook delivery (booking lifecycle, tier promotions, perk fulfilment) is on the roadmap for Phase 3.2 of the partner platform. This page will fill in once the surface ships.
Planned events
The first webhook surface will cover the events partners need to keep their own CRM/loyalty system in sync without polling:
booking.confirmed— a booking landed in the PMS and points have been issued.booking.cancelled— a confirmed booking was cancelled; points have been reversed.member.tier_changed— a member’s tier was promoted or demoted (carry-forward rules apply).perk.fulfilled— an automatic or member-selected perk was applied to a folio.
Subscription model
We expect to mirror the standard signed-webhook approach:
- Configure endpoints in the partner dashboard.
- Each delivery is signed with an HMAC against your endpoint secret — verify before processing.
- Failed deliveries are retried with exponential backoff for 24 hours.
Until then
Query the GraphQL API on page navigation or on a schedule to stay current. Within a live session, the React SDK’s useAkinLoyalty hook also refreshes on AKIN Travel’s realtime channel for tier changes. Webhooks become important for offline / server-to-server sync.
Interested?
If your integration is blocked on webhooks, let your AKIN Travel contact know — we prioritise the surface against actual demand.