[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own Airalo API

> Airalo's only API is the Partner API for eSIM resellers. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/airalo

Airalo's only API is the Partner API for businesses that resell eSIMs, by application (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Airalo account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Airalo session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=airalo)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Airalo. Airalo is a trademark of its owner. If Airalo's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/esim-data-left" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"country": "Japan"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/esim-data-left";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ country: "Japan" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/esim-data-left",
headers={"Authorization": f"Bearer {key}"},
json={"country": "Japan"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"esim": "Japan eSIM",
"data_left": "1.2 GB",
"expires": "2026-12-02"
}
]
}
```

01 Build

## How do you build an Airalo endpoint with Cotlet?

1. 01  
www.airalo.com  
Signed in  
### Sign in to Airalo in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
Show the data left and expiry date of my eSIM for Japan.  
### Do the job once with your agent.  
For example: "Show the data left and expiry date of my eSIM for Japan."
3. 03  
Save endpoint  
Name  
esim-data-left  
Input  
country  
Returns  
esim, data\_left, expires  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a country or an eSIM, and the fields it returns.
4. 04  
$ POST /api/v1/custom/esim-data-left  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in Airalo session.

02 Endpoints

## Example endpoints you could build for Airalo

Cotlet ships no fixed list of Airalo endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/esim-data-left`  
### Data left on an eSIM  
Data and days left on the eSIM you name
- POST `/api/v1/custom/all-esims`  
### All my eSIMs  
Each eSIM with its country, data left and expiry
- POST `/api/v1/custom/plans-for-trip`  
### Plans for a trip  
Plans for a country and number of days, with prices
- POST `/api/v1/custom/airmoney-balance`  
### Airmoney balance  
Your Airmoney balance
- POST `/api/v1/custom/buy-top-up` writes  
### Buy a top up  
The top up you name bought for an eSIM
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/esim-data-left" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"country": "Japan"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"esim": "Japan eSIM",
"data_left": "1.2 GB",
"expires": "2026-12-02"
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your Airalo endpoints for?

- Schedule Cotlet endpoint Phone message  
### A low data alert.  
A message on your phone when an eSIM drops below 1 GB.
- Calendar endpoint plans  
### A trip checklist.  
Before each trip in your calendar, the plans and prices for that country.
- Schedule endpoint Google Sheets  
### A trip data sheet.  
Data left on each eSIM pulled into Google Sheets during a long trip.
- Chat agent endpoint eSIMs  
### Your own AI travel assistant.  
A chat agent that checks your eSIMs before it plans a trip.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Airalo session, so it can read and change only what your Airalo login can. You choose what each endpoint does when you build it.

An endpoint that changes something, such as buying a top up, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/buy-top-up

would POST www.airalo.com/... buy 10 GB for the Japan eSIM

`buy-top-up`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Airalo have an official API?

Airalo has a Partner API for businesses that resell eSIMs, after an application reviewed by an account manager; it does not cover a traveler's own account (checked 20 Nov 2026). The full picture with sources: [Does Airalo have an API or MCP server?](https://cotlet.dev/api-status/airalo.md)

Want ChatGPT or Claude to work in Airalo instead of code? See the [Airalo MCP server](https://cotlet.dev/integrations/airalo-api-mcp-server.md).

1/3

Official API

Partners only

[Full API & MCP report](https://cotlet.dev/api-status/airalo.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## Airalo API with Cotlet: questions

### Is this an official Airalo API?

No. Cotlet is independent and not affiliated with Airalo. The endpoints you build run in your own signed-in Airalo account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when Airalo changes its screens?

An endpoint works while Airalo works the way it did when you built it. If Airalo changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first Airalo endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=airalo)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
