Last updated

Hubby eSIM API Documentation

Welcome to the Hubby eSIM API documentation. Here you'll find comprehensive guides and examples to help you integrate global eSIM connectivity into your travel services.

Core Concepts

The Hubby API is built around three entities that deliberately mirror the travel industry:

EntityWhat it representsWhy it matters
BookingA traveler's trip — groups one or more data packages, tied to a departure dateMaps directly to the booking you already have in your system (flight, hotel, tour). One API call, same mental model.
DestinationA country or region the traveler is visiting (ISO codes, names, or regional codes like EU)The same destination concept your platform already works with — no translation layer needed.
BundleA specific data product for a destination — defines size, duration, type, and priceWhat the traveler actually gets. Bundles are grouped by Destination, so browsing and purchasing feels like any other travel add-on.

We chose these names and structures so that integrating eSIM connectivity feels like adding another travel product to your platform — not like learning a telecom API.

Getting Started

Integration Use Cases

Advanced Topics

Support

Need help with your integration? Contact our support team:

  • Email: support@hubbyesim.com
  • API Reference - Detailed API specifications