Hipcamp API · unofficial, by Cotlet

Create your own Hipcamp API

Hipcamp: no public API found; its llms.txt "does not document a public booking API" (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Hipcamp 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 Hipcamp 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 Hipcamp. Hipcamp is a trademark of its owner. If Hipcamp's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/weekend-arrivals" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from": "2026-11-27", "to": "2026-11-29"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/weekend-arrivals";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ from: "2026-11-27", to: "2026-11-29" }),
});
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/weekend-arrivals",
    headers={"Authorization": f"Bearer {key}"},
    json={"from": "2026-11-27", "to": "2026-11-29"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "camper": "Sam K.",
      "site": "Meadow site",
      "guests": 2,
      "nights": 2
    },
    {
      "camper": "Ria T.",
      "site": "Creek site",
      "guests": 4,
      "nights": 1
    }
  ]
}

01 Build

How do you build a Hipcamp endpoint with Cotlet?

  1. Sign in to Hipcamp 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 arrivals between these dates, with camper, site, guests and nights."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a date range or a site, 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 Hipcamp session.

02 Endpoints

Example endpoints you could build for Hipcamp

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

  • POST /api/v1/custom/weekend-arrivals

    Arrivals for dates

    Camper, site, guests and nights of each stay

  • POST /api/v1/custom/open-requests

    Open booking requests

    Requests still waiting for your answer, with dates

  • POST /api/v1/custom/unanswered-messages

    Unanswered messages

    Camper messages with no reply yet

  • POST /api/v1/custom/earnings-by-site

    Earnings by site

    Booking earnings per site for a month

  • POST /api/v1/custom/block-nights writes

    Block nights

    Nights blocked on the site and dates you name

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/weekend-arrivals" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from": "2026-11-27", "to": "2026-11-29"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "camper": "Sam K.",
      "site": "Meadow site",
      "guests": 2,
      "nights": 2
    },
    {
      "camper": "Ria T.",
      "site": "Creek site",
      "guests": 4,
      "nights": 1
    }
  ]
}

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

  • Thursday Cotlet endpoint Email

    A Thursday arrivals list.

    Weekend arrivals per site, sent to your phone or email.

  • Monthly endpoint Google Sheets

    Earnings in a sheet.

    Booking earnings per site pulled into Google Sheets each month.

  • Schedule endpoint Notification

    No unanswered campers.

    Messages waiting more than 12 hours, posted to your phone.

  • Chat agent endpoint calendar

    Your own booking assistant.

    A chat agent that checks free sites before it answers a camper on your website.

04 Access

What can an endpoint see and change?

An endpoint works in your own Hipcamp session, so it can read and change only what your Hipcamp login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as blocking nights, 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 Hipcamp have an official API?

Hipcamp: no public API found (checked 20 Nov 2026). Bookings sync through Hipcamp's integrations with property management systems and channel managers, calendars by iCal, and bookings download as CSV. The full picture with sources: Does Hipcamp have an API or MCP server?

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

Hipcamp API with Cotlet: questions

Is this an official Hipcamp API?

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

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