# Idealista API and MCP server

> Idealista has no public API for your own listings or contacts (checked 11 Oct 2026). Its Search API is read-only and given only after an application, and its official Claude and ChatGPT app only searches public listings, with no login.

The main property portal in Spain, Italy and Portugal, where owners and agencies list homes for sale or rent and answer the people who contact them.

## What is the Idealista API?

Cotlet's Idealista API exposes 14 endpoints for your own Idealista account: list listings, get listing, get listing stats, list contacts, get conversation, list demands, update listing, deactivate listing, reactivate listing, reply to contact, send listings to contact, mark contact as handled, add contact note and archive conversation. The list_listings endpoint returns your ads with status, operation, price, address and quality score. Each endpoint takes simple JSON inputs like listing_id, contact_id or operation and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Real estate](https://cotlet.dev/integrations/category/real-estate)
- **Endpoints:** 14 (6 read, 8 write)
- **Updated:** 2026-10-11

Idealista has no public API for your own listings or contacts (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Idealista with 14 endpoints (6 read, 8 write): your AI agent signs in as you and does the work.

## Does Idealista have an official API?

Idealista has no public API for your own listings or contacts (checked 11 Oct 2026). Its Search API is read-only and given only after an application, and its official Claude and ChatGPT app only searches public listings, with no login.

| Task | Idealista official | Cotlet |
|---|---|---|
| List your own listings, active or not | No | Yes |
| Visits, contacts and quality of a listing | No | Yes |
| Change price or description | Partly: Agencies only, pushed from an approved CRM feed | Yes |
| Deactivate or reactivate a listing | No | Yes |
| Read contacts and conversations in Inbox | No | Yes |
| Reply to a contact | No | Yes |
| Send other properties to a contact | No | Yes |
| Mark contacts as handled or archive them | No | Yes |

Sources: [Idealista Search API access request](https://developers.idealista.com/access-request), [Idealista for Claude: official app docs](https://github.com/idealista/mcp-app-docs/blob/main/claude/index.md), [idealista/tools help: Inbox](https://www.idealista.com/tools/centrodeayuda/articulos/inbox/), [idealista/tools help: Rendimiento de un anuncio](https://www.idealista.com/tools/centrodeayuda/articulos/rendimiento-de-un-anuncio/), [Idealista help: Edit your listing](https://www.idealista.com/ayuda/categorias/edit-your-listing/?lang=en), [Casafari CRM: exporting properties to idealista](https://helpcenter.casafari.com/en/crm/how-can-i-export-my-properties-to-idealista.pt)

## For AI agents

```text
Idealista has no public API for your own listings or contacts (checked 11 Oct 2026). Its Search API is read-only and given only after an application, and its official Claude and ChatGPT app only searches public listings, with no login.
Cotlet provides a hosted MCP server and REST API for Idealista: 14 tools (6 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=idealista; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/idealista
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_listings, get_listing, get_listing_stats, list_contacts, get_conversation, list_demands, update_listing, deactivate_listing, reactivate_listing, reply_to_contact, send_listings_to_contact, mark_contact_handled, add_contact_note, archive_conversation
Confirm      update_listing, reactivate_listing, reply_to_contact, send_listings_to_contact (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/idealista-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=idealista (Idealista is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Idealista 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 Idealista server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Idealista MCP server instead.

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

## What can an AI agent do in Idealista?

Cotlet is best for Idealista advertisers and small agencies who want their AI agent to answer contacts, update prices and close finished listings without running or fixing a server.

- **[Answer new Idealista Inbox contacts](https://cotlet.dev/integrations/idealista-api-mcp-server/reply-to-contacts)** (runs: daily): "Answer every unread Idealista contact about the Malasaña flat: offer Saturday 11:00 or 12:30 for a viewing, leave price questions for me, and note what you sent." → `list_contacts`, `get_conversation`, `get_listing`, `reply_to_contact`, `send_listings_to_contact`, `add_contact_note`
- **[Find listings with visits but no contacts](https://cotlet.dev/integrations/idealista-api-mcp-server/listings-with-visits-but-no-contacts)** (runs: weekly): "Which of my Idealista rental listings got plenty of visits but no contacts in the last 30 days, and what is the likely reason for each?" → `list_listings`, `get_listing_stats`, `get_listing`
- **[Lower a listing price](https://cotlet.dev/integrations/idealista-api-mcp-server/lower-listing-price)**: "Lower the Valencia apartment on Idealista from 259,000 to 245,000 EUR, check the new price is live and tell me its quality score." → `list_listings`, `get_listing`, `update_listing`
- **[Deactivate a rented or sold listing](https://cotlet.dev/integrations/idealista-api-mcp-server/deactivate-rented-listing)**: "The Lisbon room is rented: tell everyone still waiting about it, take the ad off Idealista and archive its conversations." → `list_listings`, `list_contacts`, `reply_to_contact`, `deactivate_listing`, `archive_conversation`
- **Send similar properties to a contact**: "Send this contact our two other 3-bedroom flats in the same area." → `list_listings`, `send_listings_to_contact`
- **Weekly report of unanswered contacts** (runs: weekly): "Every Monday, give me new contacts per listing and the ones nobody answered." → `list_listings`, `list_contacts`

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

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

## Tools

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

### list_listings

Your ads with status, operation, price, address and quality score. Access: read. REST: `POST /api/v1/idealista/list_listings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | active, inactive or all. Default: active. |
| `operation` | enum | no | sale, rent or all. Default: all. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the ads in your account, newest first. Use the listing_id of each item in the other tools. Filter by status to see deactivated ads and by operation to separate sales from rentals. Pages hold up to 100 ads; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "listings": [
    {
      "listing_id": "108274561",
      "title": "Flat in Malasana, Madrid",
      "operation": "rent",
      "status": "active",
      "price": 1450,
      "currency": "EUR",
      "quality_score": 82,
      "url": "https://www.idealista.com/inmueble/108274561/"
    }
  ],
  "next_cursor": null
}
```

### get_listing

Full ad: price, size, rooms, features, description, photos count, URL and quality score. Access: read. REST: `POST /api/v1/idealista/get_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |

Returns one ad as it appears on Idealista, with its description, features and number of photos. Use it before update_listing to see the current values, and after it to confirm the change.

Example response:

```json
{
  "listing_id": "108274561",
  "operation": "rent",
  "status": "active",
  "price": 1450,
  "currency": "EUR",
  "size_m2": 68,
  "rooms": 2,
  "bathrooms": 1,
  "features": [
    "lift",
    "air conditioning"
  ],
  "description": "Bright two-bedroom flat near Calle Fuencarral.",
  "photos": 14,
  "quality_score": 82,
  "url": "https://www.idealista.com/inmueble/108274561/"
}
```

### get_listing_stats

Visits, contacts and favorites of a listing for a period. Access: read. REST: `POST /api/v1/idealista/get_listing_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `period` | enum | no | 7d, 30d or 90d. Default: 30d. |

Returns the number of visits, contacts and favorites an ad received in the period, as the statistics of your account show them. One listing per call.

Example response:

```json
{
  "listing_id": "108274561",
  "period": "30d",
  "visits": 912,
  "contacts": 14,
  "favorites": 37
}
```

### list_contacts

People who contacted you in Inbox, with the listing, last message and unread count. Access: read. REST: `POST /api/v1/idealista/list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | no | Only contacts about this listing. |
| `state` | enum | no | active, unread, handled or archived. Default: active. |
| `since` | date | no | Only contacts with messages on or after this date. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists contacts in your Inbox, most recent first, each with the listing it is about, the last message and the number of unread messages. State matches the Inbox lists: active, unread, handled or archived. Pages hold up to 50 contacts; pass next_cursor back as cursor.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "c_83920417",
      "name": "Marta R.",
      "listing_id": "108274561",
      "state": "unread",
      "unread": 1,
      "last_message": "Is it still available?",
      "updated_at": "2026-10-10T17:55:00+02:00"
    }
  ],
  "next_cursor": null
}
```

### get_conversation

All messages with one contact, with dates, notes and the listing they asked about. Access: read. REST: `POST /api/v1/idealista/get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |

Returns the messages of one conversation, oldest first, with your private notes and the listing the contact asked about. Your agent should read it before replying.

Example response:

```json
{
  "contact_id": "c_83920417",
  "listing_id": "108274561",
  "messages": [
    {
      "from": "contact",
      "body": "Is it still available?",
      "sent_at": "2026-10-10T17:55:00+02:00"
    }
  ],
  "notes": []
}
```

### list_demands

Demands created from your contacts in idealista/tools, with what each person is looking for. Access: read. REST: `POST /api/v1/idealista/list_demands`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `operation` | enum | no | sale, rent or all. Default: all. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Lists the demands you created from contacts in idealista/tools, each with the operation, area and budget the person is looking for. Use it to match new listings to people already waiting. Agency accounts in idealista/tools only.

Example response:

```json
{
  "demands": [
    {
      "demand_id": "d_2210",
      "contact_id": "c_83920417",
      "operation": "rent",
      "area": "Malasana",
      "max_price": 1600,
      "currency": "EUR",
      "rooms": 2
    }
  ]
}
```

### update_listing

Change the price, description or features of one of your ads. Access: write, asks the user first. REST: `POST /api/v1/idealista/update_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `fields` | object | yes | Any of price, description, size_m2, rooms, bathrooms, features. |

Changes the fields you pass and leaves the rest as they are. The new price and text are public once saved. Returns the ad as saved, so your agent can check it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "108274561",
  "status": "active",
  "price": 245000,
  "currency": "EUR",
  "updated_at": "2026-10-10T18:20:00+02:00"
}
```

### deactivate_listing

Take an ad off search results. It stays in your account and can be reactivated. Access: write. REST: `POST /api/v1/idealista/deactivate_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |

Deactivates one ad, so it no longer shows in search results. The ad stays in your account. deactivate_listing runs without asking first: it messages no one and reactivate_listing undoes it.

Example response:

```json
{
  "listing_id": "108274561",
  "status": "inactive"
}
```

### reactivate_listing

Put an expired or deactivated ad back in search results. Access: write, asks the user first. REST: `POST /api/v1/idealista/reactivate_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |

Reactivates one ad that expired or was deactivated, so it shows in search results again. An ad cannot be reactivated if the account was closed together with it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "108274561",
  "status": "active"
}
```

### reply_to_contact

Send a chat message as you to a contact in Inbox. Access: write, asks the user first. REST: `POST /api/v1/idealista/reply_to_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |
| `body` | string | yes | Message text. |

Sends a message in the Inbox conversation with one contact, under your name. It appears next to the messages you wrote by hand. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "contact_id": "c_83920417",
  "message_id": "m_552019384",
  "status": "sent",
  "sent_at": "2026-10-10T18:42:00+02:00"
}
```

### send_listings_to_contact

Share other properties from your portfolio in the conversation. Access: write, asks the user first. REST: `POST /api/v1/idealista/send_listings_to_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |
| `listing_ids` | string[] | yes | Up to 5 listing IDs from list_listings. |
| `body` | string | no | Message sent with the properties. |

Attaches up to 5 of your listings to the conversation with one contact, with an optional message, like the clip icon in Inbox. The contact sees them under your name. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "contact_id": "c_83920417",
  "message_id": "m_552019390",
  "listing_ids": [
    "108274562",
    "108274563"
  ],
  "status": "sent"
}
```

### mark_contact_handled

Mark a contact as handled, for example after a phone call. Access: write. REST: `POST /api/v1/idealista/mark_contact_handled`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |

Marks one contact as handled, the green check in Inbox, for example after you dealt with it by phone. It messages no one and is undone from Inbox. mark_contact_handled runs without asking first.

Example response:

```json
{
  "contact_id": "c_83920417",
  "state": "handled"
}
```

### add_contact_note

Private note on a conversation, only visible to you and your team. Access: write. REST: `POST /api/v1/idealista/add_contact_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |
| `note` | string | yes | Note text. |

Adds a note to the conversation detail. The contact never sees it. add_contact_note runs without asking first, because it reaches no one.

Example response:

```json
{
  "contact_id": "c_83920417",
  "note_id": "n_4410",
  "status": "saved"
}
```

### archive_conversation

Move a finished conversation out of the active list. Access: write. REST: `POST /api/v1/idealista/archive_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |

Archives one conversation, so it leaves the active list. Idealista lets you reactivate an archived request from the conversation, so nothing is lost. archive_conversation runs without asking first: it messages no one.

Example response:

```json
{
  "contact_id": "c_83920417",
  "state": "archived"
}
```

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

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

### Connect Idealista to your agent.

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

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

```
Answer every unread Idealista contact about the Malasaña flat: offer Saturday 11:00 or 12:30 for a viewing, leave price questions for me, and note what you sent.
```

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

```
curl https://cotlet.dev/api/v1/idealista/reply_to_contact \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contact_id":"c_83920417","body":"Hi, the flat is still available. I can show it on Saturday at 11:00 or 12:30."}'
```

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

```
{
  "contact_id": "c_83920417",
  "message_id": "m_552019384",
  "status": "sent",
  "sent_at": "2026-10-10T18:42:00+02:00"
}
```

## Why use Cotlet for Idealista?

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

## Is there a Idealista MCP server on GitHub?

Yes. Open-source Idealista MCP servers exist on GitHub, usually maintained by one person. Most wrap the Search API or scrape public listings; one drives a Chrome window to read the Inbox. You install and fix them yourself. Cotlet hosts the same kind of server for you, covers your own listings and Inbox, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Apply for a Search API key, or install and launch a browser session yourself | Request access, sign in to Idealista once, add one MCP server or API key |
| When Idealista changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Idealista session | In a browser profile or file on your computer | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | Tools fail until you sign in again by hand | We keep it alive; if Idealista logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| 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 Idealista 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 Idealista API cost?

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

**Do I need to be technical?**

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

Cotlet keeps your Idealista 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 idealista/tools for this?**

No for listings, stats and Inbox replies, which work in a normal advertiser account. Demands and the Inbox features that Idealista describes in its idealista/tools help center need an agency account in idealista/tools.

**Is it the same as the official Idealista app for Claude?**

No. Idealista's own app searches public listings, needs no login and is read-only (checked 11 Oct 2026). Cotlet works inside your own account: your listings, stats and contacts.

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

No. Every call to update_listing, reactivate_listing, reply_to_contact or send_listings_to_contact waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. deactivate_listing, mark_contact_handled, add_contact_note, archive_conversation runs without asking, because it sends nothing to anyone and one call undoes it.

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