PaxRelay Connect

Bring operational changes in, in the shape your systems provide them.

Connect receives source data through modern and established integration patterns, validates it and maps it to a common operational event for downstream workflows.

Discuss an integration Platform overview

Inbound mapping

01Webhook · flight.updated
02SFTP · movement_20260818.csv
03API · departure status
04→ DELAY_UPDATED

Different systems, one event

A delay should mean the same thing after it enters the platform.

Source systems use different field names, identifiers and timing conventions. Connect keeps those differences at the integration boundary so workflow rules do not need to understand every source format.

Validate at entry: Reject malformed or incomplete source records before they reach an operational workflow.
Map identifiers: Relate source service, segment and passenger references to the operator’s operating model.
Normalize timestamps: Preserve source time and timezone context while producing consistent event fields.
Trace the source: Keep the origin and mapping result available for support and audit.

Mapping trace

Source format in. Common event out.

Mappings are explicit and reviewable. A custom integration pattern does not require custom logic in every passenger workflow.

1Receive and authenticate the source
2Validate required fields and identifiers
3Map to the common operational event
4Publish the event to the applicable workflow

Connect is not a new system of record.

The source system remains authoritative. Connect handles transport, validation and normalization so the rest of the response can operate consistently.

Show us the format you already exchange.

We can review a webhook, API shape, scheduled feed or structured file and identify the shortest responsible path to a working event.

Book a demo Contact us