Skip to Content

Accordion flight-data connector

Shipped 2026-09-22

Added Accordion as a fourth connector. Unlike FuzeMetrix, Convergence and Tunn3l, it is not a check-in integration: Accordion post a daily batch of completed flights by IBA members at US iFLY tunnels to POST /api/external/accordion, and we validate and store each one in connector_accordion_booking. The first live delivery arrived on 2026-09-29 with 42 records, all accepted.

  • Same HMAC scheme as the other connectors, through the shared req-validate middleware, with a batch-aware envelope check.
  • 422 for any rejected record, because Accordion read the response body only on failure. Accepted records are stored regardless, and storage is idempotent on (CartID, CustomerID), so their single retry is harmless.
  • Times stored as UTC. Accordion send a Pacific clock with a daylight-saving-aware offset; the offset is applied on arrival and kept for audit.
  • Tunnel codes mapped by hand. connector_tunnel_mapping gains an external_code column, seeded with Accordion’s 36 codes.
  • Audit written after the response. A new audit-history middleware records the connector_history row once the response has gone, so a failed audit write can no longer change what the partner receives.

The stored data has no member-facing use yet. See Integration: Accordion for the contract and known limitations, and Accordion integration rules for the rules and the staff sharecode list.

Last updated on