Connected to the tools you already use

The problem

Operators rarely start from zero. There is already a tech log app, a charter marketplace, a booking system and fuel suppliers that send price lists and invoices. A platform that ignores them just adds more copy-and-paste.

How BXI solves it

BXI integrates with the services small-fleet operators use most, and exposes its own REST API — the same API used by the BXI Mobile and BXI eATL apps — for everything else. Outbound webhooks notify external systems when the schedule changes.

Key capabilities

• TailLog — completed flights imported automatically into the tech log: times, fuel, checklists.
• AvioWiki — airport details, opening hours, providers, runways and operational notes.
• Avinode Schedaero — flight legs and trips received by webhook; quotes tagged by source.
• PnrGO — flights, trips and passenger lists available through a pull API.
• AeroCRS — passenger import from bookings.
• Air BP, AEG Fuels, World Fuel Services, Jetex — price list and invoice file import and matching.
• Air Support PPS — airport information.
• REST API with JWT authentication, per-tenant service tokens for machine-to-machine access.
• Schedule webhooks — flight created/updated/deleted events, signed with HMAC-SHA256.
• Excel, Word, PDF and CSV exports (including CSV for Zoho).

What it changes in your day

Data that already exists somewhere else arrives in BXI on its own: the tech log from TailLog, airport data from AvioWiki, trips from Schedaero. The ops team stops re-typing and starts checking.

Where API & Integrations sits in BXI

Integrations feed Flight Planning, Technical, Fuel and Passengers. If you need an integration that is not listed, talk to us — the API and webhooks are how we build them.