# Hostelworld API and MCP server

> Hostelworld has no public API for property owners (checked 11 Oct 2026). Its affiliate programme offers an API for property and destination information "on a case by case basis", and properties sync rates, availability and bookings only through an integrated channel manager.

Booking site for hostels: travellers book beds and rooms, and properties manage bookings, reviews, guest chats and PayNow payouts in the Hostelworld Inbox.

## What is the Hostelworld API?

Cotlet's Hostelworld API exposes 15 endpoints for your own Hostelworld account: list new bookings, search bookings, get booking, list reviews, list guest chats, get chat, list payouts, get payout, export guest payments, acknowledge booking, reply to review, query review, send chat message, report payment issue and mark as no-show. The list_new_bookings endpoint returns bookings in the New Bookings tab that you have not acknowledged yet. Each endpoint takes simple JSON inputs like booking_ref, cursor or from and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Travel](https://cotlet.dev/integrations/category/travel)
- **Endpoints:** 15 (9 read, 6 write)
- **Updated:** 2026-10-11

Hostelworld has no public API for property owners (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Hostelworld with 15 endpoints (9 read, 6 write): your AI agent signs in as you and does the work.

## Does Hostelworld have an official API?

Hostelworld has no public API for property owners (checked 11 Oct 2026). Its affiliate programme offers an API for property and destination information "on a case by case basis", and properties sync rates, availability and bookings only through an integrated channel manager.

| Task | Hostelworld official | Cotlet |
|---|---|---|
| Find and read bookings | Partly: Delivered into a connected channel manager, which acknowledges them for you | Yes |
| Acknowledge new bookings | Partly: Automatic with a channel manager, otherwise by hand in Inbox | Yes |
| Read guest reviews | No | Yes |
| Reply to or query a review | No | Yes |
| Read and answer guest chats | No | Yes |
| Mark a booking as no-show | No | Yes |
| Report a payment issue | No | Yes |
| PayNow payouts and guest payments export | No | Yes |

Sources: [Hostelworld Affiliate Programme: Solutions (API on request)](https://partners.hostelworld.com/solutions), [Hostelworld Help: Connecting through a channel manager](https://support.hostelworld.com/knowledge/connecting-through-a-channel-manager), [Hostelworld Help: Reply to or query a review](https://support.hostelworld.com/knowledge/how-to-post-a-reply-to-a-review-or-query-the-review-with-hostelworld), [Hostelworld Help: Property Chat FAQ](https://support.hostelworld.com/knowledge/property-chat-in-inbox-faq-for-hostels), [Hostelworld Help: Marking customers as no-shows](https://support.hostelworld.com/knowledge/marking-customer-as-no-show), [Hostelworld Help: PayNow guide](https://support.hostelworld.com/knowledge/paynowguide), [Hostelworld Help: How to charge if a customer does not arrive](https://support.hostelworld.com/knowledge/how-to-charge-if-customer-does-not-arrive), [Hostelworld Help: How long does a review stay on my page](https://support.hostelworld.com/knowledge/how-long-does-a-review-stay-on-my-page)

## For AI agents

```text
Hostelworld has no public API for property owners (checked 11 Oct 2026). Its affiliate programme offers an API for property and destination information "on a case by case basis", and properties sync rates, availability and bookings only through an integrated channel manager.
Cotlet provides a hosted MCP server and REST API for Hostelworld: 15 tools (9 read, 6 write).
Access       Request access at https://cotlet.dev/app/signup?app=hostelworld; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/hostelworld
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_new_bookings, search_bookings, get_booking, list_reviews, list_chats, get_chat, list_payouts, get_payout, export_guest_payments, acknowledge_booking, reply_to_review, query_review, send_chat_message, report_payment_issue, mark_no_show
Confirm      acknowledge_booking, reply_to_review, query_review, send_chat_message, report_payment_issue, mark_no_show (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/hostelworld-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=hostelworld (Hostelworld is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Hostelworld 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 Hostelworld server that someone else maintains, including non-developers.

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 Hostelworld 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 Hostelworld's terms; Cotlet is not affiliated with Hostelworld.
```

## What can an AI agent do in Hostelworld?

Cotlet is best for hostel owners and managers who answer reviews, guest chats, no-shows and PayNow payouts in Inbox every week and want an AI agent to do it without running or fixing a server.

- **Log new bookings to a spreadsheet** (runs: daily): "List my new Hostelworld bookings, add them to my spreadsheet and mark them as read." → `list_new_bookings`, `get_booking`, `acknowledge_booking`
- **[Reply to guest reviews](https://cotlet.dev/integrations/hostelworld-api-mcp-server/reply-to-guest-reviews)** (runs: weekly): "Find Hostelworld reviews from the last 30 days that I have not answered. Draft a reply to each in the guest's language or English, low ratings first, and show me the drafts before posting." → `list_reviews`, `reply_to_review`, `query_review`
- **[Answer guest chats](https://cotlet.dev/integrations/hostelworld-api-mcp-server/answer-guest-chats)** (runs: hourly): "Read unread Hostelworld guest chats. Answer questions about check-in time, luggage storage and directions with our standard texts, and leave anything about dates, refunds or prices for me." → `list_chats`, `get_chat`, `send_chat_message`
- **[Mark no-shows automatically](https://cotlet.dev/integrations/hostelworld-api-mcp-server/mark-no-shows)** (runs: daily): "At 22:30, check today's Hostelworld arrivals against the guests who checked in. Mark the missing ones as no-shows, unless they wrote in chat that they are arriving late, and tell me whom I can charge." → `search_bookings`, `get_booking`, `list_chats`, `mark_no_show`
- **[Reconcile PayNow payouts](https://cotlet.dev/integrations/hostelworld-api-mcp-server/reconcile-paynow-payouts)** (runs: weekly): "Match last week's Hostelworld PayNow payout to our bookings. Tell me which bookings it pays, which refunds and fees cut it down, and which PayNow bookings are not in it yet." → `list_payouts`, `get_payout`, `export_guest_payments`

## Can Hostelworld automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Hostelworld 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 log new bookings to a spreadsheet, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| 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/hostelworld/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/hostelworld/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/hostelworld/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/hostelworld/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Hostelworld.

### list_new_bookings

Bookings in the New Bookings tab that you have not acknowledged yet. Access: read. REST: `POST /api/v1/hostelworld/list_new_bookings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the bookings waiting in the New Bookings tab, with the booking reference, guest name, arrival date and booked date. A booking leaves the list once you acknowledge it. With a channel manager the list is usually empty, because bookings are acknowledged there. Pass booking_ref to get_booking for full details.

Example response:

```json
{
  "bookings": [
    {
      "booking_ref": "412-305871264",
      "guest": "Jan Kowalski",
      "arrival": "2026-10-18",
      "nights": 2,
      "booked_at": "2026-10-10T21:14:00Z"
    }
  ],
  "next_cursor": null
}
```

### search_bookings

Advanced Search by arrival or booked date, or by reference, guest name or email. Access: read. REST: `POST /api/v1/hostelworld/search_bookings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date_type` | enum | no | arrival or booked. Default: arrival. |
| `from` | date | no | Start of the date range. |
| `to` | date | no | End of the date range. |
| `query` | string | no | Booking reference, guest name or email instead of dates. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches acknowledged and new bookings the way the Inbox search bar and Advanced Search do. Use a date range with date_type, or query for a booking reference, guest name or email. Results show reference, guest, arrival date and status. Pass booking_ref to get_booking for the details.

Example response:

```json
{
  "bookings": [
    {
      "booking_ref": "412-305871264",
      "guest": "Jan Kowalski",
      "arrival": "2026-10-10",
      "nights": 1,
      "status": "confirmed"
    }
  ],
  "next_cursor": null
}
```

### get_booking

Booking details: guest, dates, rooms or beds, rate type, deposit paid, balance due and status. No card data. Access: read. REST: `POST /api/v1/hostelworld/get_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_ref` | string | yes | Hostelworld booking reference from search_bookings or list_new_bookings. |

Returns one booking as the booking page shows it: guest, arrival date, nights, room type and number of people, rate type, deposit paid, balance due and status. Card information is never returned. Use it before mark_no_show or report_payment_issue to check the status and the rate type.

Example response:

```json
{
  "booking_ref": "412-305871264",
  "status": "confirmed",
  "guest": "Jan Kowalski",
  "arrival": "2026-10-10",
  "nights": 1,
  "room": "6-bed mixed dorm",
  "guests": 1,
  "rate_type": "flexible",
  "currency": "EUR",
  "total": 24,
  "deposit_paid": 2.4,
  "balance_due": 21.6
}
```

### list_reviews

Reviews from Reports > Customer Ratings, with ratings, text, booking reference and whether you replied. Access: read. REST: `POST /api/v1/hostelworld/list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | Start date. The range can be up to one year. |
| `to` | date | yes | End date. |
| `unanswered_only` | boolean | no | Skip reviews you already replied to. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the reviews that came in during the date range, the same list as Reports > Customer Ratings. Hostelworld allows a range of up to one year at a time. Set unanswered_only to skip reviews you replied to. Pass booking_ref to reply_to_review or query_review.

Example response:

```json
{
  "reviews": [
    {
      "booking_ref": "412-305871264",
      "rating": 7.1,
      "text": "Great location, but no hot water in the morning.",
      "language": "en",
      "replied": false,
      "reviewed_at": "2026-10-05T09:30:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_chats

Guest chats in the Inbox, newest first, with booking reference and unread flag. Access: read. REST: `POST /api/v1/hostelworld/list_chats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unread_only` | boolean | no | Only chats with unread guest messages. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists Property Chat conversations, newest first, with the guest name, booking reference and whether there are unread messages. Property Chat must be switched on in Inbox first. Pass chat_id to get_chat.

Example response:

```json
{
  "chats": [
    {
      "chat_id": "ch_77a2",
      "booking_ref": "412-305871264",
      "guest": "Jan Kowalski",
      "unread": true,
      "last_message": "What time can I check in?",
      "updated_at": "2026-10-09T15:02:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_chat

All messages in one guest chat, and whether it is still open or read-only after checkout. Access: read. REST: `POST /api/v1/hostelworld/get_chat`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `chat_id` | string | yes | Chat ID from list_chats. |

Returns the messages of one chat, oldest first, as text. Chats are open from the confirmed booking until the guest checks out and read-only after that. Images and files are not part of Property Chat.

Example response:

```json
{
  "chat_id": "ch_77a2",
  "booking_ref": "412-305871264",
  "open": true,
  "messages": [
    {
      "from": "guest",
      "body": "What time can I check in?",
      "sent_at": "2026-10-09T15:02:00Z"
    }
  ]
}
```

### list_payouts

PayNow payouts from Property Setup > Finance > Pay Now: date, status, amount, masked bank account, plus balance and next payout date. Manager users only. Access: read. REST: `POST /api/v1/hostelworld/list_payouts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | all, initiated, in_transit or completed. Default: all. |
| `from` | date | no | Payouts on or after this date. |
| `to` | date | no | Payouts on or before this date. |

Returns the Payouts tab: total balance, estimated next payout date and each payout with date, status, masked destination and amount. Status is initiated, in transit or completed. Only Manager user accounts in Inbox can view PayNow. Pass payout_id to get_payout.

Example response:

```json
{
  "balance": {
    "amount": 464.4,
    "currency": "EUR"
  },
  "next_payout_date": "2026-10-14",
  "payouts": [
    {
      "payout_id": "po_2026_10_07",
      "date": "2026-10-07",
      "status": "completed",
      "destination": "Bank account ****4821",
      "amount": 464.4,
      "currency": "EUR"
    }
  ]
}
```

### get_payout

One payout: timeline, Payout Trace ID, charges, refunds, adjustments, fees, net amount and every payment it includes. Access: read. REST: `POST /api/v1/hostelworld/get_payout`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `payout_id` | string | yes | Payout ID from list_payouts. |

Returns the payout side panel: status timeline, destination, Payout Trace ID, a summary of charges, refunds, adjustments and fees with gross and net, and every payment in the payout. Give the trace ID to your bank if a completed payout has not arrived after 5 business days. Manager users only.

Example response:

```json
{
  "payout_id": "po_2026_10_07",
  "status": "completed",
  "trace_id": "tr_9F21K0Q4",
  "summary": {
    "charges": 520,
    "refunds": 40,
    "adjustments": 0,
    "fees": 15.6,
    "net": 464.4,
    "currency": "EUR"
  },
  "transactions": [
    {
      "booking_ref": "412-305871264",
      "amount": 200,
      "status": "succeeded"
    },
    {
      "booking_ref": "412-305871377",
      "amount": 180,
      "status": "succeeded"
    },
    {
      "booking_ref": "412-305871402",
      "amount": 140,
      "status": "refunded",
      "refunded": 40
    }
  ]
}
```

### export_guest_payments

Guest Payments export as a CSV download link, with booking IDs for reconciliation. Manager users only. Access: read. REST: `POST /api/v1/hostelworld/export_guest_payments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | Start date. |
| `to` | date | yes | End date. |

Generates the Guest Payments CSV for a date range and returns a download link. The file includes the booking ID, which matches your Hostelworld booking reference. Manager users only.

Example response:

```json
{
  "url": "https://files.cotlet.example/exports/guest-payments-2026-09-30_2026-10-06.csv",
  "rows": 3,
  "from": "2026-09-30",
  "to": "2026-10-06"
}
```

### acknowledge_booking

Click "I have read this booking" so the booking leaves the New Bookings tab and Hostelworld knows you picked it up. Access: write, asks the user first. REST: `POST /api/v1/hostelworld/acknowledge_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_ref` | string | yes | Hostelworld booking reference from search_bookings or list_new_bookings. |

Marks one new booking as read. It leaves the New Bookings tab, stays in Inbox and stays searchable. Hostelworld asks you to do this for every booking. It cannot be undone with a tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_ref": "412-305871264",
  "status": "acknowledged"
}
```

### reply_to_review

Public reply under a review. Hostelworld checks it before publishing and it cannot be edited after. Access: write, asks the user first. REST: `POST /api/v1/hostelworld/reply_to_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_ref` | string | yes | Hostelworld booking reference from search_bookings or list_new_bookings. |
| `body` | string | yes | Reply in the review's language or English. Do not use the guest's name. |

Submits an owner's reply to one review. Write it in the language of the review or in English, and leave out the guest's name. Hostelworld checks the reply against its guidelines before it is published, and you cannot edit it after you submit it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_ref": "412-305871264",
  "status": "pending_moderation",
  "submitted_at": "2026-10-11T14:22:05+02:00",
  "editable": false
}
```

### query_review

Send a review to a Hostelworld moderator when you believe it breaks the review guidelines. Access: write, asks the user first. REST: `POST /api/v1/hostelworld/query_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_ref` | string | yes | Hostelworld booking reference from search_bookings or list_new_bookings. |
| `reason` | string | yes | Why the review breaks the guidelines, with evidence. |

Sends your comments about one review to a Hostelworld moderator, who reviews it and replies to you. Hostelworld does not remove a genuine unfavorable review without sufficient evidence of a breach of its Review Guidelines, so include the evidence. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_ref": "412-305871264",
  "status": "sent_to_moderator"
}
```

### send_chat_message

Reply to a guest in Property Chat, or start a chat from a booking when the Chat option is available. Access: write, asks the user first. REST: `POST /api/v1/hostelworld/send_chat_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `chat_id` | string | no | Chat ID from list_chats. Use this or booking_ref. |
| `booking_ref` | string | no | Start a new chat from this booking. |
| `body` | string | yes | Message text. |

Sends a text message to a guest in Property Chat. Use chat_id to reply, or booking_ref to message from a booking when Hostelworld shows the Chat option for it. Chat supports text only and is read-only after the guest checks out. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "chat_id": "ch_77a2",
  "status": "sent",
  "sent_at": "2026-10-09T15:10:00+02:00"
}
```

### report_payment_issue

Report Payment Issue on a booking: the guest gets an email asking them to pay. Access: write, asks the user first. REST: `POST /api/v1/hostelworld/report_payment_issue`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_ref` | string | yes | Hostelworld booking reference from search_bookings or list_new_bookings. |

Triggers Hostelworld's automatic payment request email to the guest. Use it only when the payment deadline in your policy has expired and your terms were visible at booking. If the guest does not pay within 24 hours, you can ask Hostelworld support to cancel the booking. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_ref": "412-305871264",
  "status": "payment_request_sent"
}
```

### mark_no_show

Cancel a booking as a no-show and email the guest. Available from the check-in date, not for Pay Now. Access: write, asks the user first. REST: `POST /api/v1/hostelworld/mark_no_show`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_ref` | string | yes | Hostelworld booking reference from search_bookings or list_new_bookings. |
| `comment` | string | no | Note for Hostelworld support, not shown to the guest. |

Marks the booking as a no-show, which cancels it and emails the guest. It works from the check-in date until 23:59 on that date for a one-night booking, or 48 hours after check-in for a longer stay. It does not apply to Pay Now rates or to a group where only one guest is missing. Your comment goes to Hostelworld support, not to the guest. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_ref": "412-305871264",
  "status": "cancelled_no_show"
}
```

## How do I connect Hostelworld to Claude Code, Codex or Cursor?

Connecting Hostelworld takes three steps: request access, sign in to Hostelworld once, then add one MCP server or call the REST API with the same key.

### Connect Hostelworld to your agent.

1. **Create an account** Sign up and add Hostelworld in the console. Your API key is there too.

2. **Sign in to Hostelworld once** Open the connect page from the console and sign in to Hostelworld the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Hostelworld 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.

```
List my new Hostelworld bookings, add them to my spreadsheet and mark them as read.
```

### Call Hostelworld from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/hostelworld/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/hostelworld/reply_to_review \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"booking_ref":"412-305871264","body":"Thanks for staying with us! We have fixed the hot water in dorm 3 since your visit. Hope to see you again."}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "booking_ref": "412-305871264",
  "status": "pending_moderation",
  "submitted_at": "2026-10-11T14:22:05+02:00",
  "editable": false
}
```

## Why use Cotlet for Hostelworld?

**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 Hostelworld 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 Hostelworld changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Hostelworld MCP server on GitHub?

We found no Hostelworld MCP server and no Hostelworld app on Zapier (checked 11 Oct 2026). Without an API, the realistic option is doing the work by hand in the Inbox, booking by booking. Cotlet does that work for you, through your own Inbox login.

|  | By hand in Inbox | Cotlet |
|---|---|---|
| Setup | Log in to Inbox in your browser | Request access, sign in to your Hostelworld Inbox once, add one MCP server or API key |
| Reviews | Open Reports > Customer Ratings, pick dates, click each booking reference to reply | One prompt lists reviews you have not answered and drafts the replies; Hostelworld still checks each one |
| Guest chats | Open each chat in Inbox | Your agent reads unread chats and answers; you confirm each message by default |
| PayNow payouts | Open Payouts, click each payout, export Guest Payments to match booking IDs | Your agent reads payouts and the export, and flags what does not match |
| Your session | Your browser | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When Hostelworld changes | You find the new button yourself | Our team tests it daily and fixes it for you; failed calls are free |
| 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 Hostelworld 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

## How much does the Hostelworld API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Hostelworld 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.

| 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. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Hostelworld account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Hostelworld 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 Hostelworld tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Hostelworld 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.
- **Hostelworld's terms:** You use your own Hostelworld account and stay responsible for following Hostelworld's terms. Cotlet is independent and not affiliated with Hostelworld. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Hostelworld. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Hostelworld 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 Hostelworld session would leave my computer.**

Cotlet keeps your Hostelworld 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.

**Do I need a channel manager or an API key from Hostelworld?**

No. Cotlet works in your own Hostelworld Inbox account. Hostelworld offers its API case by case to affiliates and connects properties through channel managers only (checked 11 Oct 2026). With a channel manager, bookings are acknowledged there, so New Bookings is empty.

**Who can use the PayNow tools?**

Only Manager user accounts in Inbox can view PayNow payouts and the Guest Payments export, so list_payouts, get_payout and export_guest_payments need a Manager login.

**Can my agent post or send messages in Hostelworld without asking me?**

No. Every call to acknowledge_booking, reply_to_review, query_review, send_chat_message, report_payment_issue or mark_no_show waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Hostelworld 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/hostelworld/{tool} from the HTTP Request node.