# Civitatis API and MCP server

> Civitatis has no public API for suppliers (checked 11 Oct 2026). Bookings and availability sync only through a booking system Civitatis is connected to, such as TourCMS, FareHarbor, Bokun or Rezdy, after a commercial agreement and product mapping by Civitatis.

Spanish marketplace for guided tours, day trips, activities and transfers, where local suppliers sell through the Civitatis provider panel.

## What is the Civitatis API?

Cotlet's Civitatis API exposes 13 endpoints for your own Civitatis account: list activities, list bookings, get booking, get availability, list messages, list reviews, list invoices, list payments, close dates, open dates, set quota, send message and request payment. The list_activities endpoint returns your activities on Civitatis with destination and status. Each endpoint takes simple JSON inputs like to, activity_id 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:** 13 (8 read, 5 write)
- **Updated:** 2026-10-11

Civitatis has no public API for suppliers (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Civitatis with 13 endpoints (8 read, 5 write): your AI agent signs in as you and does the work.

## Does Civitatis have an official API?

Civitatis has no public API for suppliers (checked 11 Oct 2026). Bookings and availability sync only through a booking system Civitatis is connected to, such as TourCMS, FareHarbor, Bokun or Rezdy, after a commercial agreement and product mapping by Civitatis.

| Task | Civitatis official | Cotlet |
|---|---|---|
| List and read bookings | Partly: Pushed to a connected booking system | Yes |
| Close and open dates | Partly: Only through a connected booking system | Yes |
| Limit places by day and time | Partly: Availability sync in a connected system | Yes |
| Read customer messages and write back | No | Yes |
| Read reviews | No | Yes |
| List invoices | No | Yes |
| Request the monthly payment | No | Yes |

Sources: [Civitatis provider FAQs](https://www.civitatis.com/en/providers/landing-faqs/), [Ventrata: Civitatis reseller connection](https://support.ventrata.com/en/articles/9527499-civitatis-reseller-connection), [Zaui: becoming a Civitatis supplier](https://www.zaui.com/blog/civitatis-supplier/), [Civitatis provider FAQ (Spanish)](https://www.civitatis.com/es/proveedores/landing-preguntas-frecuentes), [Civitatis general conditions of use](https://www.civitatis.com/condiciones_generales_en)

## For AI agents

```text
Civitatis has no public API for suppliers (checked 11 Oct 2026). Bookings and availability sync only through a booking system Civitatis is connected to, such as TourCMS, FareHarbor, Bokun or Rezdy, after a commercial agreement and product mapping by Civitatis.
Cotlet provides a hosted MCP server and REST API for Civitatis: 13 tools (8 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=civitatis; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/civitatis
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_activities, list_bookings, get_booking, get_availability, list_messages, list_reviews, list_invoices, list_payments, close_dates, open_dates, set_quota, send_message, request_payment
Confirm      send_message, request_payment (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/civitatis-api-mcp-server.md

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

## What can an AI agent do in Civitatis?

Cotlet is best for activity suppliers who sell on Civitatis and want their AI agent to handle dates, quotas, bookings, messages and payment requests without running or fixing a server.

- **[Close tour dates or cut places when a guide is unavailable](https://cotlet.dev/integrations/civitatis-api-mcp-server/close-tour-dates)**: "Our guide Marta is off from 20 to 22 October: close the 10:00 bike tour on those days, keep the 16:00 tour open with 8 places instead of 14, and tell me who is already booked." → `list_activities`, `get_availability`, `list_bookings`, `close_dates`, `set_quota`
- **Limit places per day and time**: "Limit the sunset cruise to 12 places on Saturdays in November." → `list_activities`, `get_availability`, `set_quota`
- **[Send guides tomorrow's booking list](https://cotlet.dev/integrations/civitatis-api-mcp-server/daily-booking-list)** (runs: daily): "Every evening at 19:00, send me tomorrow's Civitatis bookings per tour and start time, with head counts and the lead traveler's name and phone, so I can forward it to the guides." → `list_activities`, `list_bookings`, `get_booking`
- **[Answer customer messages before the tour](https://cotlet.dev/integrations/civitatis-api-mcp-server/reply-to-customer-messages)** (runs: daily): "Twice a day, read unread Civitatis messages, draft answers from the booking details and our meeting point notes, and show me the drafts before anything is sent." → `list_messages`, `get_booking`, `send_message`
- **[Request the monthly Civitatis payment and check it](https://cotlet.dev/integrations/civitatis-api-mcp-server/request-monthly-payment)** (runs: monthly): "On the 1st of each month, check last month's Civitatis settlement against my bookings, request the payment if it matches, and send me the commission invoice." → `list_payments`, `list_bookings`, `request_payment`, `list_invoices`
- **Summarize customer reviews per activity** (runs: weekly): "Summarize last month's reviews per activity, worst first." → `list_activities`, `list_reviews`

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

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

## Tools

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

### list_activities

Your activities on Civitatis with destination and status. Access: read. REST: `POST /api/v1/civitatis/list_activities`.

No parameters.

Returns every activity your provider account sells, with its destination and status. Use activity_id from each item in the other tools.

Example response:

```json
{
  "activities": [
    {
      "activity_id": "act_48213",
      "name": "Bike tour of the old town",
      "destination": "Madrid",
      "status": "active"
    },
    {
      "activity_id": "act_51907",
      "name": "Sunset cruise",
      "destination": "Madrid",
      "status": "active"
    }
  ]
}
```

### list_bookings

Bookings by activity date, with activity, time, number of people and status. Access: read. REST: `POST /api/v1/civitatis/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. |
| `activity_id` | string | no | Only bookings for this activity. |
| `status` | enum | no | confirmed, cancelled or all. Default: confirmed. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists bookings by activity date, in start time order, with the activity, time, number of people and status. By default it returns confirmed bookings for the next 7 days. Pass next_cursor back as cursor for the next page. Use booking_id with get_booking for the price and contact.

Example response:

```json
{
  "bookings": [
    {
      "booking_id": "bk_702154",
      "activity_id": "act_48213",
      "activity": "Bike tour of the old town",
      "date": "2026-10-12",
      "time": "10:00",
      "people": 3,
      "status": "confirmed"
    },
    {
      "booking_id": "bk_702160",
      "activity_id": "act_48213",
      "activity": "Bike tour of the old town",
      "date": "2026-10-12",
      "time": "10:00",
      "people": 2,
      "status": "confirmed"
    }
  ],
  "next_cursor": null
}
```

### get_booking

One booking: reference, activity, date and time, people, price and lead traveler contact. Access: read. REST: `POST /api/v1/civitatis/get_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | string | yes | Booking ID from list_bookings. |

Returns one booking with its reference, activity, date and time, number of people, price and the lead traveler contact as shown in the provider panel. Personal data is returned as the panel shows it and is not stored by Cotlet.

Example response:

```json
{
  "booking_id": "bk_702154",
  "reference": "CIV-702154",
  "activity": "Bike tour of the old town",
  "date": "2026-10-12",
  "time": "10:00",
  "people": 3,
  "price": {
    "amount": 87,
    "currency": "EUR"
  },
  "status": "confirmed",
  "lead_traveler": {
    "name": "Sample Traveler",
    "email": "traveler@example.com",
    "phone": "+34 600 000 000"
  }
}
```

### get_availability

Calendar of an activity: open and closed dates and the quota per day and time. Access: read. REST: `POST /api/v1/civitatis/get_availability`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activity_id` | string | yes | Activity ID from list_activities. |
| `from` | date | no | First date. Default: today. |
| `to` | date | no | Last date. Default: 30 days from today. |

Returns the calendar of one activity for a date range: whether each date is open or closed, and the quota for each start time. Use it before and after close_dates or set_quota to check the result. The default range is the next 30 days.

Example response:

```json
{
  "activity_id": "act_51907",
  "days": [
    {
      "date": "2026-11-07",
      "status": "open",
      "slots": [
        {
          "time": "18:00",
          "quota": 12
        }
      ]
    },
    {
      "date": "2026-11-08",
      "status": "open",
      "slots": [
        {
          "time": "18:00",
          "quota": 20
        }
      ]
    },
    {
      "date": "2026-11-09",
      "status": "closed",
      "slots": []
    }
  ]
}
```

### list_messages

Messages with customers and the Civitatis booking department, newest first. Access: read. REST: `POST /api/v1/civitatis/list_messages`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unread_only` | boolean | no | Only unread threads. Default: false. |
| `booking_id` | string | no | Only messages about this booking. |

Lists message threads with customers and with the Civitatis booking department, newest first, with the booking each one is about and the last message. Set unread_only to see only what needs an answer.

Example response:

```json
{
  "threads": [
    {
      "booking_id": "bk_702154",
      "with": "customer",
      "unread": true,
      "last_message": "Where do we meet, and does the tour run in the rain?",
      "received_at": "2026-10-11T08:12:00+02:00"
    }
  ]
}
```

### list_reviews

Customer reviews of your activities with rating, text and date. Access: read. REST: `POST /api/v1/civitatis/list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activity_id` | string | no | Only reviews of this activity. |
| `since` | date | no | Only reviews on or after this date. |

Returns customer reviews of your activities with the rating, text and date, as the provider panel shows them. Filter by activity or by start date. Reviews are read only: Cotlet has no tool to answer or report them.

Example response:

```json
{
  "reviews": [
    {
      "activity_id": "act_48213",
      "rating": 5,
      "text": "Great guide, easy route.",
      "date": "2026-09-21"
    },
    {
      "activity_id": "act_48213",
      "rating": 3,
      "text": "Meeting point was hard to find.",
      "date": "2026-09-14"
    }
  ]
}
```

### list_invoices

Commission invoices from Civitatis with period, amount and a download link. Access: read. REST: `POST /api/v1/civitatis/list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `year` | integer | no | Invoice year. Default: current year. |

Lists the invoices Civitatis issues to you, which are commission invoices, with the period, amount and a download link. The default is the current year.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "inv_2026_09",
      "period": "2026-09",
      "amount": {
        "value": 620,
        "currency": "EUR"
      },
      "download_url": "https://www.civitatis.com/example/invoice/inv_2026_09.pdf"
    }
  ]
}
```

### list_payments

Monthly settlements: services rendered, commission, net amount and payment status. Access: read. REST: `POST /api/v1/civitatis/list_payments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `year` | integer | no | Settlement year. Default: current year. |

Lists monthly settlements with the services rendered, the Civitatis commission, the net amount and the payment status. Use it before request_payment to see which months are still open. The default is the current year.

Example response:

```json
{
  "payments": [
    {
      "month": "2026-09",
      "services": {
        "value": 3100,
        "currency": "EUR"
      },
      "commission": {
        "value": 620,
        "currency": "EUR"
      },
      "net": {
        "value": 2480,
        "currency": "EUR"
      },
      "status": "not_requested"
    },
    {
      "month": "2026-08",
      "services": {
        "value": 2750,
        "currency": "EUR"
      },
      "commission": {
        "value": 550,
        "currency": "EUR"
      },
      "net": {
        "value": 2200,
        "currency": "EUR"
      },
      "status": "paid"
    }
  ]
}
```

### close_dates

Stop sales of an activity on a date range, all day or for chosen times. Access: write. REST: `POST /api/v1/civitatis/close_dates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activity_id` | string | yes | Activity ID from list_activities. |
| `from` | date | yes | First date to close. |
| `to` | date | yes | Last date to close. |
| `times` | string[] | no | Start times to close, e.g. ["10:00"]. Default: all times. |

Closes an activity for a date range, for all start times or only the ones you list. It stops new sales only; bookings already made stay, and bookings_on_closed_slots tells you how many. close_dates runs without asking first: it messages no one and open_dates undoes it in one call.

Example response:

```json
{
  "activity_id": "act_48213",
  "activity": "Bike tour of the old town",
  "closed": [
    {
      "date": "2026-10-20",
      "times": [
        "10:00",
        "16:00"
      ]
    },
    {
      "date": "2026-10-21",
      "times": [
        "10:00",
        "16:00"
      ]
    },
    {
      "date": "2026-10-22",
      "times": [
        "10:00",
        "16:00"
      ]
    }
  ],
  "bookings_on_closed_slots": 0
}
```

### open_dates

Reopen sales of an activity on dates you closed before. Access: write. REST: `POST /api/v1/civitatis/open_dates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activity_id` | string | yes | Activity ID from list_activities. |
| `from` | date | yes | First date to open. |
| `to` | date | yes | Last date to open. |
| `times` | string[] | no | Start times to open. Default: all times. |

Reopens an activity on dates you closed before, for all start times or only the ones you list. open_dates runs without asking first: it messages no one and close_dates undoes it in one call.

Example response:

```json
{
  "activity_id": "act_48213",
  "activity": "Bike tour of the old town",
  "opened": [
    {
      "date": "2026-10-22",
      "times": [
        "10:00",
        "16:00"
      ]
    }
  ]
}
```

### set_quota

Limit the places sold for an activity on given days and times. Access: write. REST: `POST /api/v1/civitatis/set_quota`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activity_id` | string | yes | Activity ID from list_activities. |
| `from` | date | yes | First date. |
| `to` | date | yes | Last date. |
| `places` | integer | yes | Maximum places per slot. |
| `weekdays` | string[] | no | Only these days, e.g. ["sat", "sun"]. Default: every day. |
| `times` | string[] | no | Only these start times. Default: all times. |

Sets the maximum number of places sold per slot for a date range, optionally only on some weekdays and start times. places counts per slot, not per day. set_quota runs without asking first: it messages no one and another call restores the old limit.

Example response:

```json
{
  "activity_id": "act_51907",
  "activity": "Sunset cruise",
  "places": 12,
  "updated": [
    {
      "date": "2026-11-07",
      "times": [
        "18:00"
      ]
    },
    {
      "date": "2026-11-14",
      "times": [
        "18:00"
      ]
    },
    {
      "date": "2026-11-21",
      "times": [
        "18:00"
      ]
    },
    {
      "date": "2026-11-28",
      "times": [
        "18:00"
      ]
    }
  ]
}
```

### send_message

Write to a customer about a booking, or to the Civitatis booking department. Access: write, asks the user first. REST: `POST /api/v1/civitatis/send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | string | yes | Booking ID from list_bookings. |
| `to` | enum | no | customer or civitatis. Default: customer. |
| `body` | string | yes | Message text. |

Sends a message about one booking, to the customer or to the Civitatis booking department. It appears in the same thread as in the provider panel. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_id": "bk_702154",
  "to": "customer",
  "status": "sent",
  "sent_at": "2026-10-11T09:05:00+02:00"
}
```

### request_payment

Request payment for services rendered in the previous month, net of commission. Access: write, asks the user first. REST: `POST /api/v1/civitatis/request_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `month` | string | yes | Month to settle, YYYY-MM. Must be a past month. |

Requests payment for the services of one past month, net of the Civitatis commission, the same request you make online in the control panel. Civitatis opens requests from the first day of the following month. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "month": "2026-09",
  "status": "requested",
  "net": {
    "value": 2480,
    "currency": "EUR"
  },
  "requested_at": "2026-10-01T09:00:00+02:00"
}
```

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

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

### Connect Civitatis to your agent.

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

2. **Sign in to Civitatis once** Open the connect page from the console and sign in to Civitatis 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 Civitatis 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 Marta is off from 20 to 22 October: close the 10:00 bike tour on those days, keep the 16:00 tour open with 8 places instead of 14, and tell me who is already booked.
```

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

```
curl https://cotlet.dev/api/v1/civitatis/close_dates \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"activity_id":"act_48213","from":"2026-10-20","to":"2026-10-22","times":["10:00","16:00"]}'
```

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

```
{
  "activity_id": "act_48213",
  "activity": "Bike tour of the old town",
  "closed": [
    {
      "date": "2026-10-20",
      "times": [
        "10:00",
        "16:00"
      ]
    },
    {
      "date": "2026-10-21",
      "times": [
        "10:00",
        "16:00"
      ]
    },
    {
      "date": "2026-10-22",
      "times": [
        "10:00",
        "16:00"
      ]
    }
  ],
  "bookings_on_closed_slots": 0
}
```

## Why use Cotlet for Civitatis?

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

## Is there a Civitatis MCP server on GitHub?

No official or community MCP server for Civitatis exists, only small scraper repos. The realistic option is a connected booking system (channel manager), which syncs availability and bookings but leaves messages, reviews, invoices and payment requests in the panel. Cotlet works in the panel itself, so your agent covers those too.

|  | Channel manager | Cotlet |
|---|---|---|
| Setup | Move your calendar to a booking system, then wait for Civitatis to map your products | Request access, sign in to the provider panel once, add one MCP server or API key |
| What it covers | Availability, prices and bookings | Also customer messages, reviews, invoices and payment requests |
| When Civitatis changes | Maintained by the booking system vendor | Our team tests it daily and fixes it for you; failed calls are free |
| Your Civitatis session | Not needed, it uses the partner connection | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | Not an issue | Your agent gets a link to sign in again |
| Where it runs | In its own dashboard | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| 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 Civitatis 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 Civitatis API cost?

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

**Do I need to be technical?**

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

Cotlet keeps your Civitatis 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 booking system to use Cotlet with Civitatis?**

No. Cotlet works in your own provider panel account and does not use the partner connection that Civitatis reserves for connected booking systems (checked 11 Oct 2026).

**When can I request my payment?**

Per the Civitatis provider FAQ, from the first day of each month you can request payment for the previous month. Requests made Monday to Sunday are paid the following Tuesday, except Madrid public holidays.

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

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

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