Wanderlog has no public API and no developer docs (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Wanderlog with 14 endpoints (5 read, 9 write): your AI agent signs in as you and does the work.
Wanderlog has no public API and no developer docs (checked 11 Oct 2026). Trips, places, reservations and expenses are edited in its web and mobile apps; bookings come in by forwarding confirmation emails or connecting Gmail.
What Wanderlog's own tools do compared with Cotlet
Task
Wanderlog official
Cotlet
List your trips and read an itinerary
No
Yes
Create a trip with dates
No
Yes
Add places, hotels and notes to a day
No
Yes
Add a checklist to a trip
No
Yes
Log and read trip expenses
No
Yes
Import a flight or hotel booking
PartlyOnly by forwarding the confirmation email or connecting Gmail in the app
Yes
Optimize the route for a day
NoPro members run Optimize route per day in the app
Cotlet is best for travellers and trip planners who want their AI agent to build itineraries, add bookings and track expenses in Wanderlog without running or fixing a server.
Plan 4 days in Lisbon from May 12 for two: museums, food markets and a day trip to Sintra. Put these saved spots on the right days and keep each day walkable. Your agent calls list_trips, create_trip, search_places, add_place, add_note, optimize_day_route, get_trip and remove_place.
Add hotel and flight bookings to a trip
Add our hotel in Porto, check-in May 16, check-out May 19, to the Portugal trip, and tell me where to forward the flight confirmation. Your agent calls list_trips, add_hotel and get_trip_forwarding_email.
Log today's receipts in the Portugal trip, split the dinners with Maya and Tom, and tell me where we stand against our 2,000 EUR budget. Your agent calls list_trips, list_expenses and add_expense.
Create packing checklists and invite tripmates
Add a packing checklist for a rainy week in Scotland and invite friend@example.com to the trip. Your agent calls add_checklist and invite_tripmate.
Rearrange a crowded day in a trip
Day 3 is overloaded. Move the castle to day 4 and reorder day 3 for less walking. Your agent calls get_trip, remove_place, add_place and optimize_day_route.
Endpoints
What is the Wanderlog API?
Cotlet's Wanderlog API exposes 14 endpoints for your own Wanderlog account: list trips, get trip, search places, list expenses, get booking import address, create trip, add place, remove place, add hotel, add note, add checklist, add expense, optimize day route and invite tripmate. The list_trips endpoint returns your trips and trips shared with you, with destination, dates and tripmates. Each endpoint takes simple JSON inputs like trip_id, day or limit and works both as an MCP tool for agents and as a REST call for scripts.
Find attractions, restaurants and hotels near the trip destination, with rating and address.
read
Searches near the trip destination and returns up to the limit, best match first, with a place_id for add_place and add_hotel. Nothing is added to the trip.
POST /api/v1/wanderlog/search_places
Input
Input: search_places
Parameter
Type
Description
trip_id required
string
Trip ID from list_trips.
query required
string
What to find, e.g. "seafood restaurant" or "Belem Tower".
limit
integer
1 to 20. Default: 10.
Example response
{
"places": [
{
"place_id": "pl_91c0",
"name": "Time Out Market Lisboa",
"category": "restaurant",
"rating": 4.4,
"address": "Av. 24 de Julho 49, Lisboa"
}
]
}
POST
list_expenses
Trip expenses with amount, currency, category and date, plus totals by category.
read
Returns the expenses logged on the trip, newest first, with the currency each was paid in. Totals by category are in the trip's home currency, as the app shows them.
The address to forward flight, hotel and car confirmations to for this trip.
read
Returns the address Wanderlog shows for forwarding confirmation emails to this trip. Forward a confirmation from your mail client and Wanderlog fills in dates and times. Cotlet does not read your mailbox.
New trip plan for a destination and date range. Private until you invite someone.
write
Creates a trip with one day per date between start and end. The trip is visible only to you until invite_tripmate. It reaches no one and you can delete it in the app, so it runs without asking.
Add a place to a day of the itinerary or to a list such as "Places to visit".
write
Adds the place at the end of the day, or of the list when no day is given. On a shared trip, tripmates see it as the app syncs in real time. It runs without asking, because it is undone with remove_place.
POST /api/v1/wanderlog/add_place
Input
Input: add_place
Parameter
Type
Description
trip_id required
string
Trip ID from list_trips.
place required
string
Place ID from search_places, or a name to look up.
day
date
Day of the trip. Omit to use the trip-level list or notes instead.
list
string
List heading when no day is given. Default: Places to visit.
start_time
string
HH:MM, local time.
note
string
Note shown under the place.
Example response
{
"block_id": "blk_2c07",
"trip_id": "tr_8kQ2mZ",
"name": "Castelo de S. Jorge",
"day": "2027-05-13",
"start_time": "10:00"
}
POST
remove_place
Remove a place from a day or list.
write
Removes one entry from the itinerary. Use block_id from get_trip. It runs without asking, because add_place puts it back.
POST /api/v1/wanderlog/remove_place
Input
Input: remove_place
Parameter
Type
Description
trip_id required
string
Trip ID from list_trips.
block_id required
string
Place entry ID from get_trip.
Example response
{
"block_id": "blk_2c07",
"status": "removed"
}
POST
add_hotel
Add lodging with check-in and check-out dates and an optional confirmation number.
write
Adds a lodging entry with the dates you pass and returns the number of nights. It runs without asking, because it reaches no one outside the trip and is removed with remove_place.
Free-text note on a day or the trip: transit tips, opening hours, booking details.
write
Adds a note to the day you name, or to the trip when no day is given. It runs without asking, because it reaches no one outside the trip and is removed with remove_place.
POST /api/v1/wanderlog/add_note
Input
Input: add_note
Parameter
Type
Description
trip_id required
string
Trip ID from list_trips.
text required
string
Note text.
day
date
Day of the trip. Omit to use the trip-level list or notes instead.
Checklist for packing, to-dos or shopping, for the whole trip or one day.
write
Creates a checklist with the items you pass, all unchecked. It runs without asking, because it reaches no one outside the trip and you can delete it in the app.
POST /api/v1/wanderlog/add_checklist
Input
Input: add_checklist
Parameter
Type
Description
trip_id required
string
Trip ID from list_trips.
title required
string
Checklist heading, e.g. Packing.
items required
string[]
Checklist items, unchecked.
day
date
Day of the trip. Omit to use the trip-level list or notes instead.
Log an expense in the currency you paid in, optionally split between tripmates.
asks first write
Logs the expense with its category and date (today by default). With split_with, the app shows who owes whom, so this reaches tripmates. By default you confirm each call; you can switch that off for this tool.
Reorder the places of one day for a shorter route, as the app's route optimization does.
write
Reorders the places of one day and returns the new order. It runs without asking, because the old order is in the response and you can restore it with remove_place and add_place.
POST /api/v1/wanderlog/optimize_day_route
Input
Input: optimize_day_route
Parameter
Type
Description
trip_id required
string
Trip ID from list_trips.
day required
date
Day to reorder.
Example response
{
"trip_id": "tr_8kQ2mZ",
"day": "2027-05-14",
"order": [
"Castelo de S. Jorge",
"Alfama walk",
"Time Out Market Lisboa"
]
}
POST
invite_tripmate
Invite someone by email to collaborate on the trip.
asks first write
Sends the invitation for the trip to the email you pass. The person sees the itinerary once they accept. By default you confirm each call; you can switch that off for this tool.
How do I connect Wanderlog to Claude Code, Codex or Cursor?
Connecting Wanderlog takes three steps: request access, sign in to Wanderlog once, then add one MCP server or call the REST API with the same key.
Connect Wanderlog over MCP
1
Create an account
Sign up and add Wanderlog in the console. Your API key is there too.
2
Sign in to Wanderlog once
Open the connect page from the console and sign in to Wanderlog the way you always do. We keep the session, never your password, and you can revoke it anytime.
Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
4
Ask your agent
Prompt
Plan 4 days in Lisbon from May 12 for two: museums, food markets and a day trip to Sintra. Put these saved spots on the right days and keep each day walkable.
Ask in plain words. Your agent finds the Wanderlog tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.
Call Wanderlog over REST
1
Export your API key
Shell
export COTLET_API_KEY="cotlet_..."
Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.
You get plain JSON back, ready for your script. A failed call costs nothing.
Why Cotlet
Why use Cotlet for Wanderlog? Hosted, safe and kept working.
Built for agents
One MCP server for every app you connect.
The same tools as a REST API for scripts and cron jobs.
Works with Claude Code, Codex and Cursor.
Your login stays yours
You sign in to Wanderlog yourself. We keep only the session, encrypted with AES-256.
The model never sees a login.
No stored passwords, no CAPTCHA solving, no MFA bypass.
You stay in control
Pick read only, or read and write.
Anything that reaches other people waits for your OK, unless you switch it off per tool.
Revoke access in one click.
Kept working for you
We test every integration daily.
When Wanderlog changes, the tool pauses until we fix it.
Failed calls cost nothing.
Alternatives
Is there a Wanderlog MCP server on GitHub?
Yes. Community Wanderlog MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, sign it in to Wanderlog, and keep it running yourself; when Wanderlog changes its site, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.
Cotlet compared with a GitHub MCP server
GitHub MCP server
Cotlet
Setup
Clone the repo, install it, sign it in to Wanderlog, add it to each MCP client
Request access, sign in to Wanderlog once, add one MCP server or API key
When Wanderlog changes
It breaks until you or the maintainer fix it
Our team tests it daily and fixes it for you; failed calls are free
Your Wanderlog session
In a file on your computer, readable by any program you run
Encrypted in an EU vault, limited to the actions you allow, revoked in one click
When the session expires
Tools fail until you sign in again by hand
If Wanderlog logs you out, your agent gets a link to sign in again
Upkeep
You update, monitor and debug it yourself
Nothing to host or update
Where it runs
Your computer, while it is on
Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule
Price
Free, paid for with your time
Free 7-day trial with 5,000 credits, then credits per call
Which one fits you
Pick Cotlet if
you are not a developer, or you do not want to maintain a server
you need it to keep working when Wanderlog changes, without checking it yourself
your agent or a script should run it on a schedule, also while your computer is off
Pick an open-source server if
you are comfortable installing, updating and fixing it yourself
you want the session to stay on your own computer
you only need it now and then, from one MCP client
For AI agents
Cotlet for Wanderlog in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.
Endpoint health
verified 2h ago
list_tripspassing
get_trippassing
search_placespassing
list_expensespassing
get_trip_forwarding_emailpassing
+ 9 more endpoints
14/14 passing latest checkself-healing
wanderlog.txt
Wanderlog has no public API and no developer docs (checked 11 Oct 2026). Trips, places, reservations and expenses are edited in its web and mobile apps; bookings come in by forwarding confirmation emails or connecting Gmail.
Cotlet provides a hosted MCP server and REST API for Wanderlog: 14 tools (5 read, 9 write).
Access Request access at https://cotlet.dev/app/signup?app=wanderlog; we email the API key.
MCP server https://cotlet.dev/mcp/v1
REST base https://cotlet.dev/api/v1/wanderlog
Auth Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools list_trips, get_trip, search_places, list_expenses, get_trip_forwarding_email, create_trip, add_place, remove_place, add_hotel, add_note, add_checklist, add_expense, optimize_day_route, invite_tripmate
Confirm add_expense, invite_tripmate (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown https://cotlet.dev/integrations/wanderlog-api-mcp-server.md
How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=wanderlog (Wanderlog is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Wanderlog once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.
Fits: people who want a hosted Wanderlog server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Wanderlog MCP server instead.
Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Wanderlog in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Wanderlog's terms; Cotlet is not affiliated with Wanderlog.
Can Wanderlog automations run on a schedule in n8n, Make or Zapier?
Yes. Cotlet does not replace your automation platform: it gives it a Wanderlog connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to track and split trip expenses, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.
Where to run Wanderlog automations through Cotlet, and how to schedule them
Where
How to connect
How to schedule
Your AI agent
Add https://cotlet.dev/mcp/v1 with your API key.
A scheduled agent run, for example a Claude Code routine.
n8n
MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/wanderlog/{tool}.
Schedule Trigger node.
Make
HTTP module: POST https://cotlet.dev/api/v1/wanderlog/{tool} with an Authorization: Bearer header and a JSON body.
Scenario schedule.
Zapier
Webhooks by Zapier: POST https://cotlet.dev/api/v1/wanderlog/{tool} with the same header and body.
Schedule by Zapier trigger.
Your own script
POST https://cotlet.dev/api/v1/wanderlog/{tool} with your API key.
cron or GitHub Actions.
Pricing & limits
How much does the Wanderlog API cost?
Free 7-day trial with 5,000 credits, no card needed. After that, the Wanderlog API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.
Cotlet plan sizes: price, monthly credits and price per credit
Size
Price
Credits / month
Per credit
Solo
$29/mo
3,000
about $0.0097
Pro
$99/mo
12,000
about $0.0083
Agency
$299/mo
40,000
$0.0075
Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.
About Cotlet
How Cotlet holds your access
Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Wanderlog account.
Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to Wanderlog yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Wanderlog tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Wanderlog in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
Wanderlog's terms
You use your own Wanderlog account and stay responsible for following Wanderlog's terms. Cotlet is independent and not affiliated with Wanderlog. Terms
Request access and pick Wanderlog. Cotlet reviews each request and emails you your API key.
Do I need to be technical?
No. You sign in to Wanderlog once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.
Is a hosted server safe? My Wanderlog session would leave my computer.
Cotlet keeps your Wanderlog session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.
Can my agent import a booking from my email?
Indirectly. get_trip_forwarding_email returns the address Wanderlog uses for forwarding confirmations, and Wanderlog then fills in dates and times itself. Cotlet does not read your mailbox. Wanderlog also offers connecting Gmail in the app, which its App Store listing describes as a Pro feature.
Can my agent post or send messages in Wanderlog without asking me?
No. Every call to add_expense or invite_tripmate waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_trip, add_place, remove_place, add_hotel, add_note, add_checklist, optimize_day_route runs without asking, because it sends nothing to anyone and one call undoes it.
Can I use the Wanderlog API in n8n?
Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/wanderlog/{tool} from the HTTP Request node.
