# Zola API and MCP server

> Zola has no public API, developer docs or webhooks for couples (checked 11 Oct 2026). Guest list, RSVP and gift data leave Zola only as files you download by hand from a desktop browser.

Wedding planning platform: wedding website, guest list with events and RSVPs, registry, gift tracker and thank-you tracking in one account.

## What is the Zola API?

Cotlet's Zola API exposes 10 endpoints for your own Zola account: list guests, list events, track RSVPs, list gifts, add guest, update guest address, invite guest to event, record RSVP, mark mail sent and mark thank-you sent. The list_guests endpoint returns guests with their list (Definitely Invited or Maybe), events invited to and RSVP state. Each endpoint takes simple JSON inputs like guest_id, event_id or list and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas)
- **Endpoints:** 10 (4 read, 6 write)
- **Updated:** 2026-10-11

Zola has no public API, developer docs or webhooks for couples (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Zola with 10 endpoints (4 read, 6 write): your AI agent signs in as you and does the work.

## Does Zola have an official API?

Zola has no public API, developer docs or webhooks for couples (checked 11 Oct 2026). Guest list, RSVP and gift data leave Zola only as files you download by hand from a desktop browser.

| Task | Zola official | Cotlet |
|---|---|---|
| List guests with lists and addresses | Partly: Manual download of the guest list and invitation addresses, desktop only | Yes |
| Add a guest to the guest list | No: Zola lets you type guests in or upload a spreadsheet by hand | Yes |
| Invite guests to events | No | Yes |
| Track RSVPs and meal choices per event | Partly: Manual "Export RSVPs" file, desktop only | Yes |
| Record an RSVP you got by phone or mail | No | Yes |
| Track Save the Dates and invitations mailed | No | Yes |
| List gifts with thank-you note status | Partly: Manual gift tracker CSV download | Yes |
| Mark thank-you notes as sent | No | Yes |

Sources: [Zola Help: What is the Guest List tool?](https://www.zola.com/faq/115002148572-what-is-the-guest-list-tool-), [Zola Help: Can I export or print my guest list?](https://www.zola.com/faq/115002148892-can-i-export-or-print-my-guest-list-from-zola-), [Zola Help: What about thank you notes?](https://www.zola.com/faq/115002837032), [Zola Help: Can I edit RSVPs that were collected online?](https://www.zola.com/faq/115002136491-can-i-edit-rsvps-that-were-collected-online-), [Zola Help: How can my guests RSVP online?](https://www.zola.com/faq/115002259432-how-can-my-guests-rsvp-online-what-does-that-experience-look-like-to-them-)

## For AI agents

```text
Zola has no public API, developer docs or webhooks for couples (checked 11 Oct 2026). Guest list, RSVP and gift data leave Zola only as files you download by hand from a desktop browser.
Cotlet provides a hosted MCP server and REST API for Zola: 10 tools (4 read, 6 write).
Access       Request access at https://cotlet.dev/app/signup?app=zola; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/zola
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_guests, list_events, track_rsvps, list_gifts, add_guest, update_guest_address, invite_guest_to_event, record_rsvp, mark_mail_sent, mark_thank_you_sent
Markdown     https://cotlet.dev/integrations/zola-api-mcp-server.md

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

## What can an AI agent do in Zola?

Cotlet is best for couples planning a wedding on Zola who want their AI agent to add guests, track RSVPs and thank-you notes without running or fixing a server.

- **Add guests from a spreadsheet and invite them to events**: "Add everyone from family.csv to my Zola guest list and invite them to the rehearsal dinner." → `add_guest`, `list_events`, `invite_guest_to_event`
- **[Weekly RSVP and meal count report](https://cotlet.dev/integrations/zola-api-mcp-server/weekly-rsvp-and-meal-report)** (runs: weekly): "Every Monday, tell me who still has not RSVP'd to each event on Zola, the meal counts for the reception so far, and what changed since last week." → `list_events`, `track_rsvps`, `list_guests`
- **[Record RSVPs from phone calls and paper cards](https://cotlet.dev/integrations/zola-api-mcp-server/record-rsvps-from-phone-and-mail)**: "Here are this week's RSVP cards: the Morales family is coming to the reception, two chicken and two kids' meals; Uncle Pete declines everything; Grace Liu called and is coming, vegetarian. Record them in Zola." → `list_guests`, `list_events`, `record_rsvp`, `track_rsvps`
- **[Track thank-you notes and mark them sent](https://cotlet.dev/integrations/zola-api-mcp-server/track-thank-you-notes)**: "List the Zola gifts we still owe a thank-you note for, grouped by giver with their address. When I tell you which cards I mailed, mark them sent." → `list_gifts`, `mark_thank_you_sent`
- **Mark thank-you notes as sent**: "I mailed these 12 thank-you cards today, mark them sent." → `list_gifts`, `mark_thank_you_sent`
- **Track Save the Dates and invitations mailed**: "I posted Save the Dates to the Smith and Jones families today. Mark them as mailed and fix the Smiths' address." → `list_guests`, `update_guest_address`, `mark_mail_sent`

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

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

## Tools

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

### list_guests

Guests with their list (Definitely Invited or Maybe), events invited to and RSVP state. Access: read. REST: `POST /api/v1/zola/list_guests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list` | enum | no | definitely_invited, maybe or all. Default: all. |
| `include_contact` | boolean | no | Add mailing address, email and phone. Default: false. |
| `search` | string | no | Match on guest name. |

Returns the guests on your guest list, each with the list they are on, the events they are invited to and their reply per event. Contact details are left out unless include_contact is true. Use guest_id from each item in the other tools.

Example response:

```json
{
  "guests": [
    {
      "guest_id": "gst_a41c07",
      "name": "Maria Example",
      "list": "definitely_invited",
      "events": [
        {
          "event_id": "evt_ceremony",
          "rsvp": "attending"
        },
        {
          "event_id": "evt_reception",
          "rsvp": "no_response"
        }
      ]
    },
    {
      "guest_id": "gst_a41c08",
      "name": "Tom Example",
      "list": "definitely_invited",
      "events": [
        {
          "event_id": "evt_ceremony",
          "rsvp": "declined"
        }
      ]
    }
  ]
}
```

### list_events

Your wedding events with type, name, date and start time. Access: read. REST: `POST /api/v1/zola/list_events`.

No parameters.

Returns the events from "Your Events" in Zola: ceremony, reception, rehearsal dinner and any others you added. Use event_id from each item in the RSVP and invite tools. Guests can only RSVP to events they are invited to.

Example response:

```json
{
  "events": [
    {
      "event_id": "evt_ceremony",
      "type": "Ceremony",
      "name": "Wedding Ceremony",
      "date": "2027-06-12",
      "start_time": "15:00"
    },
    {
      "event_id": "evt_reception",
      "type": "Reception",
      "name": "Dinner and Dancing",
      "date": "2027-06-12",
      "start_time": "18:00"
    }
  ]
}
```

### track_rsvps

RSVPs for one event: who is attending, declined or has not replied, with meal choices. Access: read. REST: `POST /api/v1/zola/track_rsvps`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `status` | enum | no | attending, declined, no_response or all. Default: all. |

Returns the replies for one event with each guest's status, meal choice and answers to the questions you added to the event. Online RSVPs from your wedding website and replies you recorded by hand are both included. Meal totals are counted from the attending guests.

Example response:

```json
{
  "event_id": "evt_reception",
  "counts": {
    "attending": 2,
    "declined": 1,
    "no_response": 1
  },
  "meals": {
    "Chicken": 1,
    "Fish": 1
  },
  "rsvps": [
    {
      "guest_id": "gst_a41c07",
      "name": "Maria Example",
      "status": "attending",
      "meal_choice": "Chicken"
    },
    {
      "guest_id": "gst_a41c08",
      "name": "Tom Example",
      "status": "attending",
      "meal_choice": "Fish"
    },
    {
      "guest_id": "gst_a41c09",
      "name": "Ana Example",
      "status": "declined",
      "meal_choice": null
    },
    {
      "guest_id": "gst_a41c10",
      "name": "Sam Example",
      "status": "no_response",
      "meal_choice": null
    }
  ]
}
```

### list_gifts

Gift tracker: each gift with giver, message, value, giver address, order status and thank-you note status. Access: read. REST: `POST /api/v1/zola/list_gifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `thank_you` | enum | no | sent, not_sent or all. Default: all. |

Returns the gifts in your gift tracker with the fields Zola's CSV download has: order number, name, quantity, value, gift message, giver's address, order status and thank-you note status. Use gift_id from each item in mark_thank_you_sent.

Example response:

```json
{
  "gifts": [
    {
      "gift_id": "gft_8f21c4",
      "order_number": "ZO-100412",
      "name": "Dutch Oven",
      "quantity": 1,
      "value": 389,
      "giver": "Alex Example",
      "message": "Congratulations!",
      "address": "12 Example Street, Springfield, IL 62701",
      "order_status": "delivered",
      "thank_you": "not_sent"
    },
    {
      "gift_id": "gft_8f21d9",
      "order_number": "ZO-100417",
      "name": "Honeymoon Fund",
      "quantity": 1,
      "value": 150,
      "giver": "Sam Example",
      "message": "Have a great trip.",
      "address": "4 Sample Road, Portland, OR 97201",
      "order_status": "completed",
      "thank_you": "not_sent"
    }
  ]
}
```

### add_guest

Add a guest, optionally with a plus-one, to your guest list. Nothing is sent to the guest. Access: write. REST: `POST /api/v1/zola/add_guest`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | Guest first name. |
| `last_name` | string | yes | Guest last name. |
| `email` | string | no | Guest email. |
| `phone` | string | no | Guest phone number. |
| `plus_one` | object | no | first_name and last_name of the plus-one, if known. |
| `list` | enum | no | definitely_invited or maybe. Default: definitely_invited. |

Adds a guest to "Definitely Invited" or "Maybe" and returns the new guest_id. A plus-one is added as a second guest in the same party. Nothing is sent to anyone, so add_guest runs without asking first. Events are set with invite_guest_to_event.

Example response:

```json
{
  "guest_id": "gst_b7720e",
  "name": "Maria Example",
  "list": "definitely_invited",
  "plus_one": {
    "guest_id": "gst_b7720f",
    "name": "Tom Example"
  },
  "status": "added"
}
```

### update_guest_address

Set the mailing address used for Save the Dates and invitation envelopes. Access: write. REST: `POST /api/v1/zola/update_guest_address`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `guest_id` | string | yes | Guest ID from list_guests. |
| `address` | object | yes | address_1, address_2, city, state_province, postal_code, country_code. |

Replaces the mailing address of one guest, the address shown on the "Address Envelopes" page. Nothing is sent to the guest, so it runs without asking first, and calling it again with the old address undoes it.

Example response:

```json
{
  "guest_id": "gst_a41c07",
  "address": {
    "address_1": "12 Example Street",
    "address_2": null,
    "city": "Springfield",
    "state_province": "IL",
    "postal_code": "62701",
    "country_code": "US"
  },
  "status": "updated"
}
```

### invite_guest_to_event

Mark a guest as invited to an event, so they can RSVP to it on your wedding website. Access: write. REST: `POST /api/v1/zola/invite_guest_to_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `guest_id` | string | yes | Guest ID from list_guests. |

Adds an event to the events a guest is invited to, the choice you make on the "Invite Guests to Events" tab. Guests can only RSVP to events they are invited to. It sends no message, so it runs without asking first.

Example response:

```json
{
  "guest_id": "gst_a41c07",
  "event_id": "evt_reception",
  "invited": true
}
```

### record_rsvp

Record a reply you got by phone or mail: attending or declined, with meal choice. Access: write. REST: `POST /api/v1/zola/record_rsvp`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `event_id` | string | yes | Event ID from list_events. |
| `guest_id` | string | yes | Guest ID from list_guests. |
| `status` | enum | yes | attending or declined. |
| `meal_choice` | string | no | One of the meal options set on the event. |

Records the reply of one guest to one event, the same as entering it under "Track RSVPs". The guest must be invited to the event, and meal_choice must be one of the options set on it. It changes only your own records and one more call corrects it, so it runs without asking first.

Example response:

```json
{
  "guest_id": "gst_a41c07",
  "event_id": "evt_reception",
  "status": "attending",
  "meal_choice": "Vegetarian",
  "recorded": true
}
```

### mark_mail_sent

Track that a guest has received a Save the Date or an invitation. Access: write. REST: `POST /api/v1/zola/mark_mail_sent`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `guest_id` | string | yes | Guest ID from list_guests. |
| `type` | enum | yes | save_the_date or invitation. |

Updates the mail tracking on the "Address Envelopes" page for one guest. It does not mail anything and reaches no one, so it runs without asking first.

Example response:

```json
{
  "guest_id": "gst_a41c07",
  "type": "save_the_date",
  "mailed": true
}
```

### mark_thank_you_sent

Mark the thank-you note for one or more gifts in the gift tracker as sent. Access: write. REST: `POST /api/v1/zola/mark_thank_you_sent`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `gift_ids` | string[] | yes | Gift IDs from list_gifts. |
| `sent` | boolean | no | false to undo. Default: true. |

Sets the thank-you note status of the gifts you pass, as the gift tracker does for one gift at a time. Set sent to false to undo. It changes only your tracker and nothing goes to the giver, so it runs without asking first.

Example response:

```json
{
  "updated": [
    {
      "gift_id": "gft_8f21c4",
      "gift": "Dutch Oven",
      "giver": "Alex Example",
      "thank_you": "sent"
    },
    {
      "gift_id": "gft_8f21d9",
      "gift": "Honeymoon Fund",
      "giver": "Sam Example",
      "thank_you": "sent"
    }
  ]
}
```

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

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

### Connect Zola to your agent.

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

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

```
Add everyone from family.csv to my Zola guest list and invite them to the rehearsal dinner.
```

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

```
curl https://cotlet.dev/api/v1/zola/mark_thank_you_sent \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"gift_ids":["gft_8f21c4","gft_8f21d9"],"sent":true}'
```

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

```
{
  "updated": [
    {
      "gift_id": "gft_8f21c4",
      "gift": "Dutch Oven",
      "giver": "Alex Example",
      "thank_you": "sent"
    },
    {
      "gift_id": "gft_8f21d9",
      "gift": "Honeymoon Fund",
      "giver": "Sam Example",
      "thank_you": "sent"
    }
  ]
}
```

## Why use Cotlet for Zola?

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

## Is there a Zola MCP server on GitHub?

Yes. Community Zola MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, sign it in to Zola, and keep it running yourself; when Zola changes its site, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, sign it in to Zola, add it to each MCP client | Request access, sign in to Zola once, add one MCP server or API key |
| When Zola 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 Zola session | In a file on your computer, readable by any program you run | 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 | If Zola 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 Zola 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 Zola API cost?

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

**Do I need to be technical?**

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

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

**Can the agent download my guest list as a file?**

It reads the same data directly, so no download is needed. Zola's own exports of the guest list, RSVPs and gifts are manual and work from a desktop browser only (checked 11 Oct 2026).

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

No. Every call to undefined waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_guest, update_guest_address, invite_guest_to_event, record_rsvp, mark_mail_sent, mark_thank_you_sent runs without asking, because it sends nothing to anyone and one call undoes it.

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