Omio API · unofficial, by Cotlet
Create your own Omio API
Omio's APIs are for affiliates and B2B partners, with no public docs found (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Omio 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 Omio session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Omio. Omio is a trademark of its owner. If Omio's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/upcoming-trips" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"month": "2026-12"}' const url = "https://cotlet.dev/api/v1/custom/upcoming-trips";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ month: "2026-12" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/upcoming-trips",
headers={"Authorization": f"Bearer {key}"},
json={"month": "2026-12"},
)
data = res.json()["data"] {
"data": [
{
"date": "2026-12-04",
"route": "Berlin to Prague",
"departure": "07:30",
"mode": "train",
"status": "confirmed"
},
{
"date": "2026-12-19",
"route": "Prague to Vienna",
"departure": "09:15",
"mode": "bus",
"status": "confirmed"
}
]
} 01 Build
How do you build an Omio endpoint with Cotlet?
-
Sign in to Omio in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List my Omio trips in December with route, departure time, mode and booking status."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a month or a route, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Omio session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Omio
Cotlet ships no fixed list of Omio endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/upcoming-trips Trips in a month
Route, departure time, mode and booking status for each trip
-
POST
/api/v1/custom/route-options Options for a route
Trains, buses and flights for a date, with duration and price
-
POST
/api/v1/custom/booking-details Booking details
Passengers, tickets and carrier for a booking
-
POST
/api/v1/custom/trip-costs Trip costs for a period
Each booking with its price, for an expense report
-
POST
/api/v1/custom/writesresend-confirmation Resend a confirmation
The confirmation email of the booking you name, sent again
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/upcoming-trips" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"month": "2026-12"}' The answer is JSON, with your fields under data:
{
"data": [
{
"date": "2026-12-04",
"route": "Berlin to Prague",
"departure": "07:30",
"mode": "train",
"status": "confirmed"
},
{
"date": "2026-12-19",
"route": "Prague to Vienna",
"departure": "09:15",
"mode": "bus",
"status": "confirmed"
}
]
} 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 Omio endpoints for?
- Schedule Cotlet endpoint Calendar
A travel calendar.
Your booked trips pulled each week into Google Calendar.
- Month end endpoint Google Sheets
An expense sheet.
Trips and prices by month, pulled into Google Sheets for your expense report.
- Schedule endpoint Slack or email
A reminder before each trip.
The day before you travel, the departure time and booking status sent to your phone.
- Chat agent endpoint route options
Your own AI assistant.
A chat agent that checks the options for a route before it suggests a trip.
04 Access
What can an endpoint see and change?
An endpoint works in your own Omio session, so it can read and change only what your Omio login can. You choose what each endpoint does when you build it.
An endpoint that changes something, such as resending a confirmation email, 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.
05 Official API
Does Omio have an official API?
No self-serve Omio API for travelers was found (checked 20 Nov 2026). Omio's search API comes with its Affiliate Programme, and its booking APIs are B2B partner products. Omio's app in ChatGPT, launched on 14 April 2026, searches and compares trips. The full picture with sources: Does Omio have an API or MCP server?
Want ChatGPT or Claude to work in Omio instead of code? See the Omio MCP server.
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.
Omio API with Cotlet: questions
Is this an official Omio API?
No. Cotlet is independent and not affiliated with Omio. The endpoints you build run in your own signed-in Omio 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 Omio changes its screens?
An endpoint works while Omio works the way it did when you built it. If Omio 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.
Build your first Omio endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.