Convergence

Convergence is the booking platform used by US tunnels. It’s integrated with iflyworld via a Google Tag Manager flow that drives bookings from the customer-facing site into Convergence and surfaces the resulting booking state back in IBA.

This page is a placeholder. The technical integration details haven’t been fully written up yet — fill in as integration work progresses. For now:

What we have

• Audience-level overview: Convergence (Overview) — what Convergence is, who it serves, where it fits in the bookings landscape vs Fuzemetrix and Tunn3l.
• Booking flow: Tunnel bookings (Business logic) — the rules our platform applies to booking data flowing in or out.

What this page should eventually cover

When the integration is documented in detail, the following sections belong here:

• Authentication / API token model — how IBA authenticates against Convergence, where the credential lives, rotation schedule.
• Data flow — what fields move which direction (member identity, booking confirmation, cancellation, no-show, etc.), where the authoritative source is for each.
• Failure modes — what happens when Convergence is unavailable, what queueing or retry mechanism (if any) the platform has, and what reconciliation looks like.
• Webhook events — if Convergence pushes events to IBA, the endpoints + payload shape + idempotency model.
• Useful tooling — Bruno collection (api/bruno/convergence-external/, api/bruno/convergence-internal/), interactive API reference, any helper scripts under api/scripts/.

See also

• Fuzemetrix integration — the sibling booking platform; structurally similar integration shape.
• Bookings overview — the framework-agnostic description of “who books where, via what.”