# Zoopla API and MCP server

> Zoopla has no public API (checked 11 Oct 2026): its developer docs say the listings API is no longer publicly available. Member agents can arrange a Leads API and a Premium Listings API with Member Services, and listings arrive through property software feeds such as Alto, Jupix or Expert Agent.

UK property portal where estate and letting agents advertise homes for sale and to rent, managed in their ZooplaPro account.

## What is the Zoopla API?

Cotlet's Zoopla API exposes 12 endpoints for your own Zoopla account: list listings, get listing, get listing performance, get performance overview, list leads, get Featured Properties report, get upgrade credits, create listing, update listing, set listing status, upgrade to Premium Listing and feature listing for a week. The list_listings endpoint returns your listings in one department, with address, price, site status, listing status and upload method. Each endpoint takes simple JSON inputs like listing_id, from or to 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:** 12 (7 read, 5 write)
- **Updated:** 2026-10-11

Zoopla has no public API (checked 11 Oct 2026): its developer docs say the listings API is no longer publicly available. Cotlet is a hosted MCP server and REST API for Zoopla with 12 endpoints (7 read, 5 write): your AI agent signs in as you and does the work.

## Does Zoopla have an official API?

Zoopla has no public API (checked 11 Oct 2026): its developer docs say the listings API is no longer publicly available. Member agents can arrange a Leads API and a Premium Listings API with Member Services, and listings arrive through property software feeds such as Alto, Jupix or Expert Agent.

| Task | Zoopla official | Cotlet |
|---|---|---|
| List your listings with status | No | Yes |
| Add or edit a listing | Partly: Only through a property software feed, not your own code | Yes |
| Mark under offer, sold or let agreed | Partly: Only through a property software feed | Yes |
| Read email and phone leads | Partly: Leads API for member agents, arranged with Member Services | Yes |
| Listing performance report and share link | No | Yes |
| Performance overview and lead counts | No | Yes |
| Upgrade to Premium Listing | Yes: Premium Listings API, subject to available credits | Yes |
| Check upgrade credits left | No | Yes |

Sources: [Zoopla Developer Docs](https://developers.zoopla.co.uk/), [ZooplaPro help: Leads API and Push Delivery Service](https://support.zoopla.co.uk/hc/en-gb/articles/4415890363281-Leads-API-and-Push-Delivery-Service), [ZooplaPro help: Premium Listings tech documentation](https://support.zoopla.co.uk/hc/en-gb/articles/360015664558-Premium-Listings-Tech-documentation), [ZooplaPro help: Featured Properties (weekly) tech documentation](https://support.zoopla.co.uk/hc/en-gb/articles/360015612077-Featured-Properties-weekly-Tech-documentation), [ZooplaPro help: manual and feed uploaders](https://support.zoopla.co.uk/hc/en-gb/articles/360004572077-What-s-the-difference-between-a-manual-and-feed-uploader)

## For AI agents

```text
Zoopla has no public API (checked 11 Oct 2026): its developer docs say the listings API is no longer publicly available. Member agents can arrange a Leads API and a Premium Listings API with Member Services, and listings arrive through property software feeds such as Alto, Jupix or Expert Agent.
Cotlet provides a hosted MCP server and REST API for Zoopla: 12 tools (7 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=zoopla; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/zoopla
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_performance, get_performance_overview, list_leads, get_featured_properties_report, get_upgrade_credits, create_listing, update_listing, set_listing_status, upgrade_to_premium, feature_listing
Confirm      update_listing, set_listing_status, upgrade_to_premium, feature_listing (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/zoopla-api-mcp-server.md

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

## What can an AI agent do in Zoopla?

Cotlet is best for estate and letting agents who want their AI agent to report on leads, update listings and send vendor reports without running or fixing a server.

- **[Weekly leads report with missed calls and valuation requests](https://cotlet.dev/integrations/zoopla-api-mcp-server/weekly-leads-report)** (runs: weekly): "Every Monday, give me last week’s Zoopla leads by type against the week before, list the missed calls with the caller’s number, and the valuation requests in full." → `get_performance_overview`, `list_leads`
- **[Mark listings under offer, sold or let agreed](https://cotlet.dev/integrations/zoopla-api-mcp-server/mark-listing-under-offer)**: "Offers were accepted on 14 Elm Road and 7 Station Road, and the flat at 2 Quay Street is let agreed. Update Zoopla and tell me which listings you could not change." → `list_listings`, `get_listing`, `set_listing_status`
- **[Send vendors their listing performance report](https://cotlet.dev/integrations/zoopla-api-mcp-server/vendor-listing-performance-reports)** (runs: weekly): "Every Friday, get the Zoopla listing performance report for each live sales listing, send me the share links per vendor, and flag the listings below the similar listings benchmark." → `list_listings`, `list_leads`, `get_listing_performance`
- **[Use Premium Listings and Weekly Featured credits before they reset](https://cotlet.dev/integrations/zoopla-api-mcp-server/upgrade-listings-to-premium)** (runs: monthly): "It is the 24th. Check how many Zoopla Premium Listings and Weekly Featured credits I have left this month, and suggest which listings should get them." → `get_upgrade_credits`, `list_listings`, `get_listing`, `upgrade_to_premium`, `feature_listing`
- **Reduce a listing price**: "Drop the price of 22 Park Street to 340,000 and add the new floorplan link." → `list_listings`, `update_listing`
- **Find listings with few leads** (runs: weekly): "Which of my live sales listings got fewer than 2 leads this month? Show their page views too." → `list_listings`, `list_leads`, `get_listing_performance`

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

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

## Tools

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

### list_listings

Your listings in one department, with address, price, site status, listing status and upload method. Access: read. REST: `POST /api/v1/zoopla/list_listings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `department` | enum | yes | residential_sales, residential_lettings, commercial_sales, commercial_lettings or overseas. |
| `site_status` | enum | no | public, private or all. Default: public. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the listings of one department as ZooplaPro shows them. Each item has the upload method (manual or feed), which tells you whether the write tools can change it. Pages hold up to 100 listings; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "listings": [
    {
      "listing_id": "67251984",
      "address": "14 Elm Road, Bristol BS7 8AB",
      "price": 375000,
      "site_status": "public",
      "listing_status": "for_sale",
      "upload_method": "manual",
      "premium": false
    },
    {
      "listing_id": "67251990",
      "address": "22 Park Street, Bath BA1 2EX",
      "price": 350000,
      "site_status": "public",
      "listing_status": "for_sale",
      "upload_method": "manual",
      "premium": true
    },
    {
      "listing_id": "67252011",
      "address": "3 Mill Lane, Bristol BS6 5JD",
      "price": 325000,
      "site_status": "public",
      "listing_status": "for_sale",
      "upload_method": "manual",
      "premium": false
    }
  ],
  "next_cursor": null
}
```

### get_listing

Full listing: address, price, property details, description, features, photos, utilities, EPC and floorplans. Access: read. REST: `POST /api/v1/zoopla/get_listing`.

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

Returns one listing with the fields you see when you edit it in ZooplaPro. Use it before update_listing so your agent changes only what you asked for.

Example response:

```json
{
  "listing_id": "67251984",
  "department": "residential_sales",
  "address": "14 Elm Road, Bristol BS7 8AB",
  "price": 375000,
  "site_status": "public",
  "listing_status": "for_sale",
  "upload_method": "manual",
  "details": {
    "bedrooms": 3,
    "bathrooms": 1,
    "receptions": 2,
    "property_type": "terraced",
    "tenure": "freehold"
  },
  "full_description": "A bright three bedroom terraced house close to the park, with a south facing garden and off street parking.",
  "features": [
    "South facing garden",
    "Off street parking"
  ],
  "photo_urls": [
    "https://example.com/photos/elm-road-1.jpg",
    "https://example.com/photos/elm-road-2.jpg",
    "https://example.com/photos/elm-road-3.jpg"
  ],
  "floorplan_urls": []
}
```

### get_listing_performance

Listing performance report: daily page views, price changes, Featured Properties upgrades, similar listings benchmark and a shareable link for the vendor or landlord. Access: read. REST: `POST /api/v1/zoopla/get_listing_performance`.

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

Returns the listing performance report you generate from the ZooplaPro Dashboard for one property. Daily page views run oldest first, and the same chart marks price changes and Featured Properties upgrades. The share link gives the vendor or landlord a live snapshot that Zoopla updates daily. The tool only reads and sends nothing to the vendor.

Example response:

```json
{
  "listing_id": "67252011",
  "address": "3 Mill Lane, Bristol BS6 5JD",
  "from": "2026-10-05",
  "to": "2026-10-11",
  "page_views": {
    "total": 321,
    "daily": [
      41,
      38,
      52,
      47,
      60,
      44,
      39
    ]
  },
  "price_changes": [],
  "featured_upgrades": [],
  "similar_listings": {
    "average_page_views": 388
  },
  "share_url": "https://www.zoopla.co.uk/pro/example-report/3f9c2a"
}
```

### get_performance_overview

Listings live per department, email and phone lead counts, and Premium Listings in use for a date range. Access: read. REST: `POST /api/v1/zoopla/get_performance_overview`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | no | Start of the date range. Default: 7 days ago. |
| `to` | date | no | End of the date range. Default: today. |

Returns the headline numbers of the ZooplaPro Dashboard for a date range: listings live per department, lead counts by type and the number of Premium Listings in use. Use list_leads for the individual leads behind the counts.

Example response:

```json
{
  "from": "2026-10-05",
  "to": "2026-10-11",
  "listings_live": {
    "residential_sales": 18,
    "residential_lettings": 11
  },
  "leads": {
    "sales_email": 24,
    "lettings_email": 19,
    "valuation_email": 6,
    "phone": 11,
    "total": 60
  },
  "premium_listings_in_use": 4
}
```

### list_leads

Leads from the Leads report: email enquiries with message and listing, phone calls with time, caller number and result. Access: read. REST: `POST /api/v1/zoopla/list_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | enum | no | for_sale_email, to_rent_email, valuation_email, phone or all. Default: all. |
| `listing_id` | string | no | Only leads for this listing. |
| `from` | date | no | Start of the date range. Default: 7 days ago. |
| `to` | date | no | End of the date range. Default: today. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the leads of the ZooplaPro Leads report for a date range, newest first. Email leads have the enquirer's message and the listing; phone leads have the call time, the caller's number and whether it was answered or missed. Totals count all leads in the range, not only this page. Set listing_id to see one property.

Example response:

```json
{
  "from": "2026-10-05",
  "to": "2026-10-11",
  "totals": {
    "sales_email": 24,
    "lettings_email": 19,
    "valuation_email": 6,
    "phone": 11,
    "total": 60
  },
  "leads": [
    {
      "lead_id": "l_90c1",
      "type": "sales_email",
      "received_at": "2026-10-10T16:42:00+01:00",
      "listing_id": "67251984",
      "address": "14 Elm Road, Bristol BS7 8AB",
      "name": "Sam",
      "message": "Is the garden south facing, and can we view on Saturday?"
    },
    {
      "lead_id": "l_90b7",
      "type": "phone",
      "received_at": "2026-10-10T11:05:00+01:00",
      "listing_id": "67251990",
      "address": "22 Park Street, Bath BA1 2EX",
      "caller_number": "07700 900123",
      "result": "answered"
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjIwfQ"
}
```

### get_featured_properties_report

How each of your Featured Properties is performing on Zoopla, listing by listing. Access: read. REST: `POST /api/v1/zoopla/get_featured_properties_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | no | Start of the date range. Default: 7 days ago. |
| `to` | date | no | End of the date range. Default: today. |

Returns the Featured Property report of ZooplaPro for a date range, one row per Featured listing. It is available when your package includes Featured Property. Use get_listing_performance for the full report of a single property.

Example response:

```json
{
  "from": "2026-10-05",
  "to": "2026-10-11",
  "listings": [
    {
      "listing_id": "67251990",
      "address": "22 Park Street, Bath BA1 2EX",
      "featured_from": "2026-10-06",
      "featured_until": "2026-10-13",
      "page_views": 412
    }
  ]
}
```

### get_upgrade_credits

Premium Listings and Weekly Featured Property credits left, their expiry, and which listings use them. Access: read. REST: `POST /api/v1/zoopla/get_upgrade_credits`.

No parameters.

Returns the upgrade credits of your account and the listings that use them. Check it before upgrade_to_premium or feature_listing, because each upgrade uses one credit.

Example response:

```json
{
  "premium_listings": {
    "credits_left": 3,
    "used_by": [
      "67251990"
    ]
  },
  "weekly_featured": {
    "credits_left": 2,
    "used_by": []
  }
}
```

### create_listing

New listing in a department, saved as Private so it is not on Zoopla until you publish it. Manual uploaders only. Access: write. REST: `POST /api/v1/zoopla/create_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `department` | enum | yes | residential_sales, residential_lettings, commercial_sales, commercial_lettings or overseas. |
| `address` | object | yes | Street, town and postcode. |
| `price` | integer | yes | Sale price or rent in pounds, numbers only. |
| `details` | object | yes | Bedrooms, bathrooms, receptions, property type, tenure, council tax band and other required fields. |
| `full_description` | string | yes | Full description shown on the listing. |
| `photo_urls` | string[] | no | Photos in display order. |
| `copy_from_listing_id` | string | no | Start from an existing or deleted listing, like Create similar. |

Creates a listing and saves it as Private, so it is not on Zoopla and reaches no one. Publish it with set_listing_status, which asks for your OK. Because nothing goes public and set_listing_status can delete it, create_listing runs without asking first. Use copy_from_listing_id to start from an existing or deleted listing, like Create similar in ZooplaPro.

Example response:

```json
{
  "listing_id": "67252040",
  "department": "residential_sales",
  "address": "9 Orchard Close, Bristol BS9 3QE",
  "price": 410000,
  "site_status": "private",
  "listing_status": "for_sale"
}
```

### update_listing

Change price, description, features, photos, video or floorplan links. Normally live on Zoopla within the hour. Manual uploaders only. Access: write, asks the user first. REST: `POST /api/v1/zoopla/update_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `fields` | object | yes | Any of price, price_modifier, full_description, features, photo_urls, video_urls, floorplan_urls. |

Changes the fields you pass on one listing and leaves the others as they are. Edits on a public listing normally go live on Zoopla within 1 hour, and a price change appears as a mark in the listing performance chart. Listings sent by a property software feed cannot be changed here. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "67251990",
  "address": "22 Park Street, Bath BA1 2EX",
  "price_before": 350000,
  "price": 340000,
  "live_on_zoopla": "within 1 hour"
}
```

### set_listing_status

Publish, hide or delete a listing, or mark it under offer, sold, let agreed or let. Manual uploaders only. Access: write, asks the user first. REST: `POST /api/v1/zoopla/set_listing_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `site_status` | enum | no | public, private or deleted. |
| `listing_status` | enum | no | for_sale, sale_under_offer, sold, to_rent, let_agreed or let. |

Changes the site status or the listing status of one listing, or both. Listing status shows the buyer or tenant what stage the property is at. Changes normally go live on Zoopla within 1 hour. Listings sent by a property software feed cannot be changed here. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "67251984",
  "department": "residential_sales",
  "address": "14 Elm Road, Bristol BS7 8AB",
  "site_status": "public",
  "listing_status": "sale_under_offer",
  "live_on_zoopla": "within 1 hour",
  "url": "https://www.zoopla.co.uk/for-sale/details/67251984/"
}
```

### upgrade_to_premium

Make a listing Premium for 12 months, using one credit, with 2 highlights. Needs 3 photos and a 200 character description. Access: write, asks the user first. REST: `POST /api/v1/zoopla/upgrade_to_premium`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `highlight_ids` | string[] | no | Up to 2 highlights from the Premium Listings highlights chart. |

Upgrades one listing to Premium, which lasts 12 months or until the listing is removed. It uses one Premium Listings credit and fails if the listing has fewer than 3 photos or a full description under 200 characters. Pick the 2 highlights from the Premium Listings highlights chart. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "67251984",
  "premium": true,
  "premium_until": "2027-10-11",
  "highlights": [
    "garden",
    "parking"
  ],
  "credits_left": 2
}
```

### feature_listing

Upgrade a listing to Weekly Featured Property, using one credit. Access: write, asks the user first. REST: `POST /api/v1/zoopla/feature_listing`.

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

Upgrades one listing to Weekly Featured Property for a week and uses one Weekly Featured Property credit. It works when your package includes Featured Property. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "67252011",
  "featured_from": "2026-10-12",
  "featured_until": "2026-10-19",
  "credits_left": 1
}
```

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

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

### Connect Zoopla to your agent.

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

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

```
Every Monday, give me last week’s Zoopla leads by type against the week before, list the missed calls with the caller’s number, and the valuation requests in full.
```

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

```
curl https://cotlet.dev/api/v1/zoopla/set_listing_status \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"listing_id":"67251984","listing_status":"sale_under_offer"}'
```

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

```
{
  "listing_id": "67251984",
  "department": "residential_sales",
  "address": "14 Elm Road, Bristol BS7 8AB",
  "site_status": "public",
  "listing_status": "sale_under_offer",
  "live_on_zoopla": "within 1 hour",
  "url": "https://www.zoopla.co.uk/for-sale/details/67251984/"
}
```

## Why use Cotlet for Zoopla?

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

## Is there a Zoopla MCP server on GitHub?

No Zoopla MCP server turned up on GitHub and Zoopla has no official Zapier app (checked 11 Oct 2026). Most agents do these jobs by hand in ZooplaPro, or forward lead emails into a CRM.

|  | By hand in ZooplaPro | Cotlet |
|---|---|---|
| Setup | None, you click through ZooplaPro | Request access, sign in to ZooplaPro once, add one MCP server or API key |
| Reports and leads | Open the Dashboard, the Leads report and each listing report, copy the numbers | One question to your agent, or a weekly run on a schedule |
| Bulk changes | Edit each listing in turn | Your agent walks through the list; you confirm each public change |
| When Zoopla changes | You relearn the screens | Our team tests it daily and fixes it for you; failed calls are free |
| Your ZooplaPro session | In your browser | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| Where it runs | Your browser, while you work | 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 Zoopla 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 Zoopla API cost?

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

**Do I need to be technical?**

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

Cotlet keeps your Zoopla 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 feed or Member Services credentials?**

No. Cotlet works in your own ZooplaPro account and does not use the Leads API or Premium Listings API. Listing changes work for manual uploaders only, because Zoopla lets feed listings be changed in the property software alone.

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

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

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