How it works
Connect once. Approve partners. Data flows.
BIXAero gives each organisation its own message service and connects it to the partners it chooses. Here is the journey, from registration to live data.
The journey
From registration to live data
You are registered
We register your organisation with the details you give us, including a business contact and a technical contact, and your IATA airline or airport code.
Your contacts are welcomed
Both contacts receive an email confirming the registration.
Your service starts
The platform starts your own dedicated message service and message broker, one for each kind of data you exchange.
You sign in
Your contacts sign in with single sign-on, using their own organisation account. BIXAero never asks for or stores their passwords.
You request data
Find a partner in the directory of registered organisations and ask for its baggage or flight data, explaining why you need it. The partner is emailed.
The partner decides
The partner accepts, optionally narrowing what it sends, or denies the request with an explanation. You are emailed either way.
Data flows
Once accepted, the platform links the two organisations and messages flow automatically for as long as the agreement is in force.
Connect your way
Four ways to connect your systems
Choose separately for baggage data and flight data. Your systems keep working the way they do today.
Hosted endpoint
Your systems connect to your own BIXAero endpoint using AMQP over TLS, with a client certificate issued by the platform.
Connector
The platform connects out to the messaging system you already run: IBM MQ, Apache Kafka, RabbitMQ or AMQP 1.0.
HTTPS webhook
Each message is delivered to your web endpoint, signed so your system can prove it came from BIXAero.
REST API
Your systems send messages and collect those waiting for them over HTTPS, authenticated with OAuth 2.0.
No automated link yet? Business teams can send and read messages in the portal.
Standards
Checked and converted between IATA standards
Every message is checked when it enters the platform, whichever route it takes. If your partner uses a different standard, BIXAero converts it for them.
- Baggage messages in IATA 1745 (Type B) are strictly validated; IATA 1755 XML must be well formed
- Flight messages in IATA AIDX are checked against the AIDX schemas
- Conversion between IATA 1745 and IATA 1755, and between Type B flight messages and AIDX
- Baggage and flight data kept apart in separate services, so they can never be mixed
Control
Share exactly what your partners need
- Limit a baggage agreement to particular airlines and airports, so partners only receive the bags that concern them
- Choose which elements of each baggage message you send to each partner
- Set a period for an agreement, and revoke it at any time with an explanation
- Let a trusted organisation, such as your messaging vendor, manage your data feeds for you
Visibility
Know where every message is
Live messages
Watch messages arrive for your organisation within seconds.
Delivery status
For every message you sent in the last seven days, see when the platform accepted it and when each partner received it.
Alerts
Your technical contact is emailed when messages pile up, when your systems stop collecting, or when a service stops answering, and again when it clears.
Replay and network map
Send the last seven days of delivered messages to your systems again, and see all your data flows on one map.
See it working with your own data
Tell us a little about your organisation and we will set up a trial for your team. No commitment, nothing to install.