One connection.
The whole cargo chain.
Approve once. Keys, channels, and event routes are provisioned automatically. No key is ever copy-pasted.
White-label booking portal. Looks up the airline, requests to sell its capacity.
Airline cargo ERP. System of record. Its admin approves, rejects, or revokes.
Ground handling, per station. Looks up the airline, requests to handle for it at named stations.
Airline cargo ERP. System of record. Its admin approves, rejects, or revokes.
White-label booking portal. Looks up the airline, requests to sell its capacity.
Ground handling, per station. Looks up the airline, requests to handle for it at named stations.
Look up the airline by designator. If it runs on Flaks the answer carries its capabilities: live rates, capacity, AWB issue, tracking events. Never a 404, so nobody can probe the directory.
The request lands in the airline's approval queue in Flaks. The admin approves, rejects with a reason, or revokes later. Handlers' station lists can be edited before approval.
The first poll after approval carries the key or channel bundle. The claim is atomic and the server destroys the secret right after. There is no “show again”.
Cargo-IMP messaging sits at the edge of the ecosystem, for parties outside it. Flaks generates FWB and FFM for outside parties; Skidd speaks FFM-in and FSU-out to non-Flaks airlines; Takst's manual channel dispatches FWB and reads SSIM. Inside, the spine is REST/JSON plus ONE Record JSON-LD. No Cargo-IMP message touches Connect.
Flaks Connect: FAQ
What is Flaks Connect?
Flaks Connect is the handshake layer of the Flaks ecosystem: an airline directory, a consent flow, and a one-time credential service. A seller's Takst portal or a handler's Skidd workspace looks up an airline, requests a relationship, and the airline's admin approves it in Flaks. Approval provisions the credentials and event routes automatically. Connect itself never carries bookings, waybills, or status updates.
What actually flows through Connect?
Four things: a directory lookup (is this airline on Flaks, and what can it do?), a relationship request, the airline's approval decision, and one credential bundle delivered exactly once. Cargo data then flows on separate surfaces: sellers use the Booking API for quotes, bookings, and tracking; handlers exchange ONE Record events with the airline over two station-scoped channels.
How long does connecting take?
As long as the airline takes to click approve. The consumer product looks up the airline, sends the request, and polls for the decision. The first poll after approval carries the credentials; there is no key exchange by email and nothing to copy-paste.
What if my airline partner doesn't run Flaks?
Every product works alone. Takst has a manual channel: SSIM-based schedules, locally maintained rates, AWB stock management, and FWB message dispatch, so you can sell for a carrier that has no API at all. Skidd speaks FFM-in and FSU-out to airlines outside the ecosystem.
Is Flaks Connect a separate product I pay for?
No. Connect ships with the ecosystem products. You pay for the products you use — see pricing for details.