# GetYourGuide API and MCP server

> GetYourGuide has a Supplier API, but it is built for reservation systems and channel managers that pass its connectivity testing, not for a tour operator who wants a key (checked 11 Oct 2026). Every system must implement the mandatory endpoints, and the docs describe no API for customer messages or reviews.

Marketplace for tours, activities and attraction tickets, where local operators sell to travelers and manage products, availability, bookings, messages and reviews in the Supplier Portal.

## What is the GetYourGuide API?

Cotlet's GetYourGuide API exposes 11 endpoints for your own GetYourGuide account: list bookings, get booking, list products, get availability, list messages, list reviews, get performance, update availability, update pricing, reply to message and reply to review. The list_bookings endpoint returns bookings for your products, by activity date, with travelers, option and status. Each endpoint takes simple JSON inputs like from, to or product_id 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:** 11 (7 read, 4 write)
- **Updated:** 2026-10-11

GetYourGuide has a Supplier API, but it is built for reservation systems and channel managers that pass its connectivity testing, not for a tour operator who wants a key (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for GetYourGuide with 11 endpoints (7 read, 4 write): your AI agent signs in as you and does the work.

## Does GetYourGuide have an official API?

GetYourGuide has a Supplier API, but it is built for reservation systems and channel managers that pass its connectivity testing, not for a tour operator who wants a key (checked 11 Oct 2026). Every system must implement the mandatory endpoints, and the docs describe no API for customer messages or reviews.

| Task | GetYourGuide official | Cotlet |
|---|---|---|
| List and read bookings | Partly: Booking and cancellation calls go to a connected reservation system | Yes |
| Update availability | Partly: Availability notifications from a connected system | Yes |
| Update prices | Partly: Price fields in the availability object, connected systems only | Yes |
| List products and options | Partly: Product list is an optional feature, activated after live testing | Yes |
| Read and reply to customer messages | No | Yes |
| Read and reply to reviews | No | Yes |
| Performance figures | No | Yes |

Sources: [GetYourGuide Supplier API documentation](https://integrator.getyourguide.com/documentation/overview), [GetYourGuide Connectivity Partner FAQs](https://www.getyourguide.supply/connectivity/partners-faqs), [GetYourGuide: managing your reviews](https://getyourguide.supply/articles/new-ways-to-manage-your-reviews-on-getyourguide), [GetYourGuide: Messages, every customer conversation in one place](https://www.getyourguide.supply/articles/introducing-messages-every-customer-conversation-in-one-place), [GetYourGuide help center: Messages in the Supplier Portal](https://supply.getyourguide.support/hc/en-us/articles/34781062388637-Messages-in-the-Supplier-Portal), [GetYourGuide help center: Replying to customer reviews](https://supply.getyourguide.support/hc/en-us/articles/23135372019869-Replying-to-customer-reviews-in-the-Supplier-Portal), [GetYourGuide help center: Price over API](https://supply.getyourguide.support/hc/en-us/articles/14150365685661-Price-over-API)

## For AI agents

```text
GetYourGuide has a Supplier API, but it is built for reservation systems and channel managers that pass its connectivity testing, not for a tour operator who wants a key (checked 11 Oct 2026). Every system must implement the mandatory endpoints, and the docs describe no API for customer messages or reviews.
Cotlet provides a hosted MCP server and REST API for GetYourGuide: 11 tools (7 read, 4 write).
Access       Request access at https://cotlet.dev/app/signup?app=getyourguide; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/getyourguide
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_bookings, get_booking, list_products, get_availability, list_messages, list_reviews, get_performance, update_availability, update_pricing, reply_to_message, reply_to_review
Confirm      update_pricing, reply_to_message, reply_to_review (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/getyourguide-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=getyourguide (GetYourGuide is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to GetYourGuide 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 GetYourGuide 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 GetYourGuide 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 GetYourGuide's terms; Cotlet is not affiliated with GetYourGuide.
```

## What can an AI agent do in GetYourGuide?

Cotlet is best for tour and activity operators who sell on GetYourGuide without a channel manager and want their AI agent to handle bookings, availability, prices, messages and reviews without running or fixing a server.

- **[Block tour slots when a guide is out](https://cotlet.dev/integrations/getyourguide-api-mcp-server/block-slots-on-a-date)**: "Our guide Marco is sick on 18 October. Block every free slot of the sunset harbor tour that day and tell me who is already booked." → `list_products`, `get_availability`, `update_availability`, `list_bookings`, `get_booking`
- **[Raise tour prices for a new season](https://cotlet.dev/integrations/getyourguide-api-mcp-server/update-tour-prices-in-bulk)**: "From 1 April, raise the adult and child price on every English option by 8%, round to whole euros, and show me old and new prices before you change anything." → `list_products`, `update_pricing`
- **[Answer traveler messages](https://cotlet.dev/integrations/getyourguide-api-mcp-server/reply-to-traveler-messages)** (runs: daily): "Go through unread GetYourGuide messages, draft answers using each booking and my meeting point notes below, list any date change or cancellation requests, and show me the drafts before sending." → `list_messages`, `get_booking`, `reply_to_message`
- **[Reply to reviews without an answer](https://cotlet.dev/integrations/getyourguide-api-mcp-server/reply-to-reviews)** (runs: weekly): "Find GetYourGuide reviews from the last 30 days with a comment and no reply, draft answers that mention what each traveler wrote, and show me the 3-star and lower ones first." → `list_reviews`, `reply_to_review`
- **Check who is booked on tomorrow's tours** (runs: daily): "Who is booked on tomorrow's 10:00 walking tour, and how many adults and children?" → `list_bookings`, `get_booking`
- **Weekly performance report** (runs: weekly): "Every Monday, send me last week's performance figures per product." → `get_performance`

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

Yes. Cotlet does not replace your automation platform: it gives it a GetYourGuide 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 answer traveler messages, 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/getyourguide/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/getyourguide/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/getyourguide/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/getyourguide/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 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 GetYourGuide.

### list_bookings

Bookings for your products, by activity date, with travelers, option and status. Access: read. REST: `POST /api/v1/getyourguide/list_bookings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | no | First activity date. Default: today. |
| `to` | date | no | Last activity date. Default: 7 days from today. |
| `product_id` | string | no | Only bookings for this product. |
| `status` | enum | no | confirmed, cancelled or all. Default: confirmed. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns bookings whose activity date falls in the range, ordered by date and start time. Cancelled bookings are left out unless status is cancelled or all. Results come in pages; pass next_cursor as cursor for the next one.

Example response:

```json
{
  "bookings": [
    {
      "booking_reference": "GYGZ4K2M9T1X",
      "product_id": "88213",
      "option_id": "412087",
      "date": "2026-10-18",
      "time": "17:30",
      "status": "confirmed",
      "travelers": {
        "adult": 2,
        "child": 1
      }
    },
    {
      "booking_reference": "GYGB7Q5N3R8D",
      "product_id": "88213",
      "option_id": "412087",
      "date": "2026-10-18",
      "time": "18:30",
      "status": "confirmed",
      "travelers": {
        "adult": 4,
        "child": 0
      }
    }
  ],
  "next_cursor": null
}
```

### get_booking

One booking: reference, option, date and time, participants by category, price and lead traveler. Access: read. REST: `POST /api/v1/getyourguide/get_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_reference` | string | yes | GetYourGuide booking reference from list_bookings, e.g. GYGZ4K2M9T1X. |

Returns one booking with the option, date, start time, travelers per category, the price and the lead traveler's name and language. The reference is on the booking in list_bookings.

Example response:

```json
{
  "booking_reference": "GYGZ4K2M9T1X",
  "product": "Sunset Harbor Walking Tour",
  "option_id": "412087",
  "date": "2026-10-18",
  "time": "17:30",
  "status": "confirmed",
  "travelers": {
    "adult": 2,
    "child": 1
  },
  "price": {
    "amount": 110,
    "currency": "EUR"
  },
  "lead_traveler": {
    "name": "Sam Rivera",
    "language": "en"
  }
}
```

### list_products

Your products with their options, status and price categories. Access: read. REST: `POST /api/v1/getyourguide/list_products`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | active, inactive or all. Default: active. |

Returns your products and, under each, its options with the option ID that the availability and pricing tools need. Each option lists its price categories and current retail prices. Inactive products are left out unless you ask.

Example response:

```json
{
  "products": [
    {
      "product_id": "88213",
      "title": "Sunset Harbor Walking Tour",
      "status": "active",
      "options": [
        {
          "option_id": "412087",
          "name": "English, small group",
          "price_categories": {
            "adult": 40,
            "child": 20
          },
          "currency": "EUR"
        }
      ]
    }
  ]
}
```

### get_availability

Start times and free spots of an option for the dates you ask for. Access: read. REST: `POST /api/v1/getyourguide/get_availability`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `option_id` | string | yes | Option ID from list_products. |
| `from` | date | yes | First date. |
| `to` | date | yes | Last date. |

Returns each date in the range with its start times, free spots and how many are booked. Use it before closing a slot to see who is already booked.

Example response:

```json
{
  "option_id": "412087",
  "days": [
    {
      "date": "2026-10-18",
      "slots": [
        {
          "time": "17:30",
          "vacancies": 8,
          "booked": 3
        },
        {
          "time": "18:30",
          "vacancies": 12,
          "booked": 0
        }
      ]
    }
  ]
}
```

### list_messages

Traveler conversations from Messages, each with its booking reference. Access: read. REST: `POST /api/v1/getyourguide/list_messages`.

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

Returns your Messages conversations, most recent first, with the traveler, the booking reference, the unread count and the last message. Set unread_only to see only what needs an answer.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "cv_7a21",
      "booking_reference": "GYGZ4K2M9T1X",
      "traveler": "Sam Rivera",
      "unread": 1,
      "last_message": "Where exactly do we meet?",
      "updated_at": "2026-10-16T08:12:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_reviews

Reviews of your products with rating, text, date and your reply, if any. Access: read. REST: `POST /api/v1/getyourguide/list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `product_id` | string | no | Only reviews of this product. |
| `since` | date | no | Only reviews on or after this date. |
| `unanswered_only` | boolean | no | Skip reviews you already replied to. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns reviews of your products, newest first, with rating, text, date and your reply when there is one. Filter to unanswered reviews to build a reply queue.

Example response:

```json
{
  "reviews": [
    {
      "review_id": "rv_30482",
      "product_id": "88213",
      "rating": 5,
      "text": "Great guide, loved the harbor stories.",
      "date": "2026-10-12",
      "reply": null
    }
  ],
  "next_cursor": null
}
```

### get_performance

The figures shown in the Supplier Portal performance view, for a date range. Access: read. REST: `POST /api/v1/getyourguide/get_performance`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | Start of the period. |
| `to` | date | yes | End of the period. |
| `product_id` | string | no | Only this product. Default: all products. |

Returns the figures shown in the Supplier Portal performance view for the range. Without product_id every product is included.

Example response:

```json
{
  "from": "2026-10-05",
  "to": "2026-10-11",
  "products": [
    {
      "product_id": "88213",
      "title": "Sunset Harbor Walking Tour",
      "figures": {
        "bookings": 37
      }
    }
  ]
}
```

### update_availability

Set free spots for start times of an option on one date, or close them with 0. Access: write. REST: `POST /api/v1/getyourguide/update_availability`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `option_id` | string | yes | Option ID from list_products. |
| `date` | date | yes | Activity date. |
| `slots` | object | yes | Map of start time (HH:MM) to free spots, e.g. {"17:30": 0}. |

Sets free spots per start time for one option and one date; 0 closes the slot. Existing bookings are not touched. It reaches no one and one call reopens the slot, so it runs without asking for your OK. Returns the slots as the app now shows them.

Example response:

```json
{
  "option_id": "412087",
  "date": "2026-10-18",
  "slots": [
    {
      "time": "17:30",
      "vacancies": 0,
      "status": "closed"
    },
    {
      "time": "18:30",
      "vacancies": 0,
      "status": "closed"
    }
  ],
  "bookings_on_date": 3
}
```

### update_pricing

Change the retail price per category of an option, from a date on. Access: write, asks the user first. REST: `POST /api/v1/getyourguide/update_pricing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `option_id` | string | yes | Option ID from list_products. |
| `prices` | object | yes | Map of price category (adult, child) to price in your currency. |
| `valid_from` | date | no | First date with the new price. Default: today. |

Sets the retail price per price category of one option from a date on. Travelers see the new price on the activity page, so a wrong price costs money. A booking system that pushes rates can overwrite it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "option_id": "412087",
  "valid_from": "2026-11-01",
  "currency": "EUR",
  "prices": {
    "adult": 44,
    "child": 22
  },
  "previous": {
    "adult": 40,
    "child": 20
  }
}
```

### reply_to_message

Send a reply to a traveler in a Messages conversation. Access: write, asks the user first. REST: `POST /api/v1/getyourguide/reply_to_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_messages. |
| `body` | string | yes | Reply text. |

Sends your reply to the traveler in the conversation; it appears in their GetYourGuide app. Messages cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": "cv_7a21",
  "status": "sent",
  "sent_at": "2026-10-16T08:40:00Z"
}
```

### reply_to_review

Post your public reply under a review of your product. Access: write, asks the user first. REST: `POST /api/v1/getyourguide/reply_to_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | Review ID from list_reviews. |
| `body` | string | yes | Reply text, shown publicly on the activity page. |

Posts your reply under one review. It is public on the activity page and attached to your provider name. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rv_30482",
  "status": "published",
  "replied_at": "2026-10-16T09:05:00Z"
}
```

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

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

### Connect GetYourGuide to your agent.

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

2. **Sign in to GetYourGuide once** Open the connect page from the console and sign in to GetYourGuide 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 GetYourGuide 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.

```
Our guide Marco is sick on 18 October. Block every free slot of the sunset harbor tour that day and tell me who is already booked.
```

### Call GetYourGuide 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/getyourguide/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/getyourguide/update_availability \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"option_id":"412087","date":"2026-10-18","slots":{"17:30":0,"18:30":0}}'
```

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

```
{
  "option_id": "412087",
  "date": "2026-10-18",
  "slots": [
    {
      "time": "17:30",
      "vacancies": 0,
      "status": "closed"
    },
    {
      "time": "18:30",
      "vacancies": 0,
      "status": "closed"
    }
  ],
  "bookings_on_date": 3
}
```

## Why use Cotlet for GetYourGuide?

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

## Is there a GetYourGuide MCP server on GitHub?

We found no GetYourGuide MCP server and no official Zapier app. The realistic options are a booking system or channel manager that connects through the Supplier API, or doing it by hand in the Supplier Portal.

|  | Channel manager | Cotlet |
|---|---|---|
| Setup | Move your calendar to a booking system, then map each option in the Supplier Portal | Request access, sign in to the Supplier Portal once, add one MCP server or API key |
| What it covers | Availability, prices and bookings | Also customer messages, reviews and performance stats |
| Works with your AI agent | No, you work in its own dashboard | Yes: Claude Code, Codex, Cursor, n8n and scripts |
| When the session expires | Not an issue, it uses the Supplier API | If GetYourGuide logs you out, your agent gets a link to sign in again |
| When GetYourGuide changes | Maintained by the vendor | Our team tests it daily and fixes it for you; failed calls are free |
| Upkeep | The vendor runs it; you keep the subscription | Nothing to host or update |
| Price | Subscription or booking fees, depending on the system | 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 GetYourGuide 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 GetYourGuide API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the GetYourGuide 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 GetYourGuide 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 GetYourGuide 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 GetYourGuide tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect GetYourGuide 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.
- **GetYourGuide's terms:** You use your own GetYourGuide account and stay responsible for following GetYourGuide's terms. Cotlet is independent and not affiliated with GetYourGuide. [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 GetYourGuide. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

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

Cotlet keeps your GetYourGuide 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 the Supplier API?**

No. Cotlet works in your own Supplier Portal account and does not use the Supplier API, which GetYourGuide opens to reservation systems that pass its connectivity testing (checked 11 Oct 2026).

**Will it clash with my booking system?**

It can. If a connected booking system pushes availability or rates, it may overwrite what Cotlet sets. Use one source of truth for each option.

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

No. Every call to update_pricing, reply_to_message or reply_to_review waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_availability runs without asking, because it sends nothing to anyone and one call undoes it.

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