FX-Port eSIM API Is Now Live — Add Travel eSIMs to Your Platform With One Integration
A few weeks ago we opened the FX-Port API for flight bookings. Today eSIMs join it, on the exact same account, the same key, and the same balance you’re already using for flights.
If you’ve already integrated FX-Port, there’s nothing new to set up. Your existing key already has permission to call eSIM endpoints, your existing balance is what gets debited, and your existing dashboard is where flight bookings and eSIM orders now show up side by side. If you haven’t integrated yet, this is a good reason to start — one connection now covers two things a traveler needs in the same moment: a seat on the plane, and a way to get online once they’re off it.
Why this pairs so naturally with flights
Selling a flight puts you right next to a question the traveler is about to ask themselves anyway: how am I getting connected when I land? An eSIM is one of the few travel add-ons that’s genuinely easy to attach — there’s no size, no seat, no date change to negotiate. It’s a QR code the traveler scans before they board or right after they land, and they’re online before they’ve found the taxi rank.
For an agency already booking flights through FX-Port, that makes eSIMs close to free upside. The integration is already done. This is one more product sitting on top of it, not a second stack to build and maintain.
What you can offer
- Data plans across 190+ countries
- Instant digital delivery — a QR code, not a physical SIM that has to ship or wait behind a counter
- Wholesale, net pricing that you mark up yourself, not a fixed referral cut
- Coverage sourced across multiple supplier networks, so it doesn’t depend on any single vendor’s gaps
Where the docs stand right now
Flights has a full technical reference live at docs.fx-port.com — request and response shapes, error codes, the works. eSIM endpoints are live and callable on that same key today; the dedicated written reference for them is landing on the docs site shortly, the same way hotels’ is. If you want to start wiring it up before that page goes live, reach out through the docs site and the team will walk you through the exact request format directly — no need to wait for the page to publish before you start building.
Same key, same responsibility
Worth repeating for anyone new to the API through this post specifically: a Read+Write key can place real orders and charge your balance on eSIMs just as it does on flights. Keep it server-side — never in a mobile app, a front-end bundle, or a public repo.
What’s next
Hotels documentation is close behind. And the same rule holds across every product on FX-Port: as more suppliers and more coverage get added behind the scenes, your integration doesn’t need to change to benefit from it.
Start building
- Docs: docs.fx-port.com
- API keys: fx-port.com/dashboard/api
- Sign up: fx-port.com/register
