Skip to main content
The Roamly API is built for two kinds of partner. Listing partners — comparison sites, directories and publishers who show Roamly plans alongside other providers. The catalog endpoints give you every destination and plan we sell, with live pricing, so your listings stay current without anyone maintaining a spreadsheet. Enterprise customers — businesses buying eSIMs for their own travellers, staff or customers. Alongside the catalog, you can retrieve the eSIMs on your account: installation details, activation status and data usage, ready to drop into your own dashboard or travel tooling. If you need purchasing wired into your systems as well, talk to us — we build bespoke integrations for volume customers.
All endpoints are GET requests returning JSON, authenticated with an API key — see Authentication.

Endpoints

Quick example

Good to know

  • Currencies — prices are in AUD by default. Pass ?currency=USD for US-dollar prices, converted at a fixed reference rate; checkout on onroamly.com always charges AUD.
  • Freshness — the catalog is served from a short-lived cache and reflects changes within about a minute. Polling more than a few times an hour is rarely useful.
  • Your eSIMs — an API key belongs to one Roamly account, and the /v1/esims endpoints only ever return that account’s eSIMs. Usage figures come from an hourly poll, so usage.updatedAt tells you how fresh a reading is.
  • Purchasing — buying through the API isn’t public yet. Each plan’s url links to its purchase page on onroamly.com, and for volume customers we set up purchasing directly — get in touch.