ITT eSIM API (1.0.0)

Searches for available eSIM plans for a given region, country or supplier. Use this endpoint to build the initial connectivity offer alongside hotel search results, then narrow down to a specific package with /esim/single-esim-package.

Retrieves detailed information and pricing for a specific eSIM package that was returned from /esim/search. The response can be used to confirm the offer shown to the user before creating a booking with /esim/create-booking.

Updates passenger and contact details on an existing eSIM booking. Call this endpoint after hotel or itinerary changes so that the connectivity order has the same traveller profile and contact information as the related hotel booking.

Creates a confirmed eSIM booking for one or more packages. Typically called after hotel booking confirmation, using the same member and contact details so that eSIM vouchers and installation instructions can be surfaced in the same post-booking experience.

Returns data usage for a provisioned eSIM, including remaining balance and consumption trends. Use this to power “trip dashboard” or “upcoming stay” views where usage is shown next to hotel and itinerary details.

Retrieves the full details of an eSIM booking, including package, traveller, and status information. This is the primary read endpoint to keep your UI in sync when showing combined hotel, flight or activity bookings with attached eSIMs.

Provides device-specific installation instructions for a purchased eSIM, in the requested language. Use this endpoint to embed install guides into your trip confirmation flows alongside hotel check-in instructions.

Returns the list of devices that are compatible with the eSIM offering. This can be used during hotel or package checkout to pre-validate that travellers’ phones and tablets support eSIM before you surface connectivity upsells.

Lists available top-up options for an active eSIM. Call this endpoint when building account or “manage booking” pages so that travellers staying at a hotel can purchase additional data without leaving your application.

Creates a booking for a selected top-up package. This is usually invoked from a self-service area where the traveller is reviewing their hotel stay and chooses to add more data for the same trip.

Returns historical top-up transactions for a given eSIM. Use this to show spend history and support flows (for example, confirming charges related to a hotel stay or corporate trip).

Registers a webhook subscription so that your platform can receive asynchronous events such as low data balance or lifecycle updates. These events can be used to trigger notifications inside your travel UI, for example while the traveller is viewing upcoming or in-progress hotel stays.