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.

Member data-rights notices

Sent to every partner that holds the member: the partner the member signed up through, and every partner the member has an active enrolment with. The payloads carry no name, email or phone.

member.closed — the member closed their account. Carries memberId, partnerMemberRef (your own key for the member, where you set one), closedAt and retainUntil: delete the member data you exported by this date, 3 years after closure.
member.erased — the member’s personal data was erased. Carries memberId, partnerMemberRef and erasedAt.
member.rectified — a field you receive (name, email or phone) was corrected. Carries memberId, partnerMemberRef, changedFields (the field names, not the values) and rectifiedAt. Read the corrected record through the API.
member.restricted — the member restricted processing of their data (GDPR Article 18). Carries memberId, partnerMemberRef and restrictedAt. Keep what you hold, but stop processing it until member.restriction_lifted arrives; AKIN stops returning the member from member reads in the meantime.
member.restriction_lifted — the restriction ended. Carries memberId, partnerMemberRef and liftedAt. You may process the member’s data again.

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.