Polarsteps API · unofficial, by Cotlet

Create your own Polarsteps API

No public Polarsteps API was found (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Polarsteps 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 Polarsteps session and returns only what your login can see.

Try it free now

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

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

curl
curl -X POST "https://cotlet.dev/api/v1/custom/trip-steps" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"trip": "Portugal"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/trip-steps";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ trip: "Portugal" }),
});
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/trip-steps",
    headers={"Authorization": f"Bearer {key}"},
    json={"trip": "Portugal"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "date": "2026-05-12",
      "place": "Lisbon",
      "photos": 6,
      "has_story": true
    },
    {
      "date": "2026-05-13",
      "place": "Sintra",
      "photos": 4,
      "has_story": false
    }
  ]
}

01 Build

How do you build a Polarsteps endpoint with Cotlet?

  1. Sign in to Polarsteps in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List the steps of my Portugal trip in order, with place, date, number of photos and whether each has a story."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a trip name or a date, and the fields it returns.

  4. 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 Polarsteps session.

02 Endpoints

Example endpoints you could build for Polarsteps

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

  • POST /api/v1/custom/trip-steps

    Steps of a trip

    Place, date, photos and story status for each step, in order

  • POST /api/v1/custom/my-trips

    Your trips

    Title, dates and who can see each trip

  • POST /api/v1/custom/steps-without-story

    Steps without a story

    Steps of a trip that have no text yet

  • POST /api/v1/custom/trip-plan

    A planned trip

    Planned stops and flights of an upcoming trip

  • POST /api/v1/custom/add-step writes

    Add a step

    A new step with place, date and story on the trip you name

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/trip-steps" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"trip": "Portugal"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "date": "2026-05-12",
      "place": "Lisbon",
      "photos": 6,
      "has_story": true
    },
    {
      "date": "2026-05-13",
      "place": "Sintra",
      "photos": 4,
      "has_story": false
    }
  ]
}

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 Polarsteps endpoints for?

  • Schedule Cotlet endpoint Blog draft

    A travel blog.

    New steps with their stories, pulled into your blog drafts each week.

  • Trip ends endpoint Google Sheets

    A trip log sheet.

    The places and dates of each trip, kept in Google Sheets.

  • Schedule endpoint Phone message

    An evening reminder on the road.

    The steps still missing a story, sent to your phone each evening of the trip.

  • Chat agent endpoint trips

    Your own travel assistant.

    A chat agent that reads your past trips before it suggests the next one.

04 Access

What can an endpoint see and change?

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

An endpoint that changes something, such as adding a step, 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 Polarsteps have an official API?

No public or partner API for Polarsteps was found on polarsteps.com or its help center (checked 20 Nov 2026). The official way to get data out is Download my data, an archive of your whole account sent by an emailed link. The full picture with sources: Does Polarsteps have an API or MCP server?

Want ChatGPT or Claude to work in Polarsteps instead of code? See the Polarsteps 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.

Polarsteps API with Cotlet: questions

Is this an official Polarsteps API?

No. Cotlet is independent and not affiliated with Polarsteps. The endpoints you build run in your own signed-in Polarsteps 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 Polarsteps changes its screens?

An endpoint works while Polarsteps works the way it did when you built it. If Polarsteps 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 Polarsteps endpoint

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

Try it free now

No card. Takes about 5 minutes.