# Thryv API and MCP server

> Thryv Business Center has no public developer API (checked 11 Oct 2026). The only official way in from code is a Zapier connection with 4 triggers and 5 actions, authorized with a token that only the primary admin can see; the REST API Thryv documents is for Keap, its separate CRM.

All-in-one software for small local businesses: clients, calendar, estimates, invoices, an inbox for client messages and online reviews.

## What is the Thryv API?

Cotlet's Thryv API exposes 14 endpoints for your own Thryv account: list clients, get client, list services, list appointments, list invoices, list conversations, list reviews, add client, book appointment, mark no-show, create estimate, create invoice, send message and reply to review. The list_clients endpoint returns clients with contact details and tags, newest first. Each endpoint takes simple JSON inputs like client_id, limit or staff 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:** 14 (7 read, 7 write)
- **Updated:** 2026-10-11

Thryv Business Center has no public developer API (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Thryv with 14 endpoints (7 read, 7 write): your AI agent signs in as you and does the work.

## Does Thryv have an official API?

Thryv Business Center has no public developer API (checked 11 Oct 2026). The only official way in from code is a Zapier connection with 4 triggers and 5 actions, authorized with a token that only the primary admin can see; the REST API Thryv documents is for Keap, its separate CRM.

| Task | Thryv official | Cotlet |
|---|---|---|
| List appointments | Partly: Zapier "New Appointment" trigger, new ones only | Yes |
| Add a client | Partly: Zapier "Create Client" and "Find or Create Client" actions | Yes |
| Book an appointment for a client | No: Zapier can only create a busy time | Yes |
| Create and send an estimate | No | Yes |
| Create and send an invoice | No: Zapier only reports new invoices | Yes |
| Read the inbox | No: Zapier can create a conversation, not read one | Yes |
| Message several clients | No | Yes |
| Reply to online reviews | No | Yes |

Sources: [Thryv Help: Zapier Integrations Overview](https://learn.thryv.com/hc/en-us/articles/360003054791-Zapier-Integrations-Overview), [Thryv Help: How To Grab Zapier API Token](https://learn.thryv.com/hc/en-us/articles/14858117059853-How-To-Grab-Zapier-API-Token), [Thryv integrations on Zapier](https://zapier.com/apps/thryv/integrations), [Thryv marketplace](https://www.thryv.com/marketplace/), [Thryv Help: Review Management (ThryvAI replies, posted by hand)](https://learn.thryv.com/hc/en-us/articles/360002386411-Review-Management), [Thryv Help: How to Create and Send Estimates](https://learn.thryv.com/hc/en-us/articles/360001936011-How-to-Create-and-Send-Estimates-in-Thryv-Business-Center)

## For AI agents

```text
Thryv Business Center has no public developer API (checked 11 Oct 2026). The only official way in from code is a Zapier connection with 4 triggers and 5 actions, authorized with a token that only the primary admin can see; the REST API Thryv documents is for Keap, its separate CRM.
Cotlet provides a hosted MCP server and REST API for Thryv: 14 tools (7 read, 7 write).
Access       Request access at https://cotlet.dev/app/signup?app=thryv; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/thryv
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_clients, get_client, list_services, list_appointments, list_invoices, list_conversations, list_reviews, add_client, book_appointment, mark_no_show, create_estimate, create_invoice, send_message, reply_to_review
Confirm      book_appointment, mark_no_show, create_estimate, create_invoice, send_message, reply_to_review (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/thryv-api-mcp-server.md

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

## What can an AI agent do in Thryv?

Cotlet is best for owners of small local businesses on Thryv who want their AI agent to book appointments, invoice jobs, answer reviews and message clients without running or fixing a server.

- **Daily schedule and unpaid invoices briefing** (runs: daily): "What appointments do I have tomorrow, and who still has an unpaid invoice?" → `list_appointments`, `list_invoices`
- **Invoice completed jobs** (runs: daily): "Invoice today's completed jobs from my calendar." → `list_appointments`, `create_invoice`
- **[Reply to unanswered online reviews](https://cotlet.dev/integrations/thryv-api-mcp-server/reply-to-reviews)** (runs: weekly): "Reply to every Thryv review from the last 7 days that still needs a response. Thank the happy ones by what they mention, apologize on the low ones and give our phone number, and hold anything about refunds for me." → `list_reviews`, `list_clients`, `reply_to_review`
- **[Book appointments from client messages](https://cotlet.dev/integrations/thryv-api-mcp-server/book-appointments)**: "Go through my Thryv inbox, find everyone asking for an appointment and book them. Add new people as clients first, check the calendar for clashes, and show me each booking before it goes out." → `list_conversations`, `list_clients`, `add_client`, `list_services`, `list_appointments`, `book_appointment`
- **Message clients about open slots** (runs: weekly): "Message all clients tagged "spring" that slots are open next week." → `list_clients`, `send_message`
- **[Create estimates from quote requests](https://cotlet.dev/integrations/thryv-api-mcp-server/create-estimates-from-quote-requests)** (runs: daily): "Find this week's quote requests in my Thryv inbox and draft an estimate for each one from my services menu. Save them as drafts and tell me what you assumed." → `list_conversations`, `list_clients`, `add_client`, `list_services`, `create_estimate`

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

Yes. Cotlet does not replace your automation platform: it gives it a Thryv 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 daily schedule and unpaid invoices briefing, 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/thryv/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/thryv/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/thryv/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/thryv/{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 Thryv.

### list_clients

Clients with contact details and tags, newest first. Access: read. REST: `POST /api/v1/thryv/list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Name or email. |
| `tag` | string | no | Only clients with this tag. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the clients on your account, newest first. Filter by name, email or tag to find a group such as everyone tagged "spring". Pages hold up to 100 clients; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "clients": [
    {
      "client_id": "cl_8f2a91",
      "name": "Sample Client",
      "email": "client@example.com",
      "phone": "+1 555 0100",
      "tags": [
        "spring"
      ]
    },
    {
      "client_id": "cl_20b4d7",
      "name": "Jordan Hale",
      "email": "jordan@example.com",
      "phone": "+1 555 0101",
      "tags": [
        "spring",
        "lawn"
      ]
    }
  ],
  "next_cursor": null
}
```

### get_client

Client card: contact details, tags, notes, client details, appointments, invoices and message history. Access: read. REST: `POST /api/v1/thryv/get_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients. |

Returns one client card with contact details, tags, internal notes, appointments, invoices and the message history. Use it before replying or invoicing so your agent sees everything about the client.

Example response:

```json
{
  "client_id": "cl_8f2a91",
  "name": "Sample Client",
  "email": "client@example.com",
  "tags": [
    "spring"
  ],
  "notes": "Prefers morning visits.",
  "appointments": [
    {
      "appointment_id": "ap_40b2d8",
      "service": "Lawn treatment",
      "start": "2026-09-29T09:00:00-05:00"
    }
  ],
  "invoices": [
    {
      "invoice_id": "inv_2041",
      "total": "85.00",
      "balance_due": "0.00"
    }
  ],
  "messages": 3
}
```

### list_services

Services from your services menu, with their saved prices. Access: read. REST: `POST /api/v1/thryv/list_services`.

No parameters.

Returns the services on your services menu with their saved prices. Use the name as the service parameter of book_appointment.

Example response:

```json
{
  "services": [
    {
      "name": "Lawn treatment",
      "price": "85.00"
    },
    {
      "name": "Edging",
      "price": "25.00"
    }
  ]
}
```

### list_appointments

Calendar appointments in a date range, with client, service, staff and price. Access: read. REST: `POST /api/v1/thryv/list_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | First day. |
| `to` | date | yes | Last day, at most 31 days after from. |
| `staff` | string | no | Only this staff member. |

Lists calendar appointments between two dates, with client, service, staff and price. The range is at most 31 days. Filter by staff member to see one person's calendar.

Example response:

```json
{
  "appointments": [
    {
      "appointment_id": "ap_40b2d8",
      "client": "Sample Client",
      "client_id": "cl_8f2a91",
      "service": "Lawn treatment",
      "start": "2026-10-13T09:00:00-05:00",
      "end": "2026-10-13T10:00:00-05:00",
      "staff": "Alex",
      "price": "85.00"
    },
    {
      "appointment_id": "ap_40b2d9",
      "client": "Jordan Hale",
      "client_id": "cl_20b4d7",
      "service": "Edging",
      "start": "2026-10-13T11:00:00-05:00",
      "end": "2026-10-13T11:30:00-05:00",
      "staff": "Alex",
      "price": "25.00"
    }
  ]
}
```

### list_invoices

Invoices from the Sales tab with client, total, balance due and dates. Access: read. REST: `POST /api/v1/thryv/list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | no | Only this client. |
| `unpaid_only` | boolean | no | Skip invoices paid in full. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Lists invoices from the Sales tab with client, total, balance due and dates. Set unpaid_only to skip invoices paid in full. Pages hold up to 100 invoices.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "inv_2044",
      "client": "Jordan Hale",
      "client_id": "cl_20b4d7",
      "total": "110.00",
      "balance_due": "110.00",
      "issued": "2026-10-05",
      "due": "2026-10-19"
    }
  ]
}
```

### list_conversations

Inbox conversations with the latest messages, across email, text and other connected channels. Access: read. REST: `POST /api/v1/thryv/list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | no | Only this client. |
| `limit` | integer | no | 1 to 50. Default: 20. |

Lists inbox conversations with the latest messages, across email, text and the other channels you connected in Thryv. Filter by client to see one thread. Pages hold up to 50 conversations.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "cv_77d2",
      "client": "Sample Client",
      "client_id": "cl_8f2a91",
      "channel": "text",
      "last_message": "Can we move Tuesday to 10:00?",
      "updated_at": "2026-10-10T16:02:00-05:00"
    }
  ]
}
```

### list_reviews

Reviews from the Reputation dashboard, from every connected site, with rating and whether you replied. Access: read. REST: `POST /api/v1/thryv/list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unanswered_only` | boolean | no | Skip reviews you already answered. |
| `since` | date | no | Only reviews posted on or after this date. |

Lists reviews from the Reputation dashboard, from every site you connected, with rating, text and whether you replied. Use unanswered_only to see what needs a reply. Pass review_id to reply_to_review.

Example response:

```json
{
  "reviews": [
    {
      "review_id": "rv_3b90c1",
      "site": "Google",
      "rating": 5,
      "author": "Dana K.",
      "text": "The lawn looks great.",
      "posted": "2026-10-08",
      "replied": false
    }
  ]
}
```

### add_client

New client card. Nothing is sent to the client. Access: write. REST: `POST /api/v1/thryv/add_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | First name. |
| `last_name` | string | no | Last name. |
| `email` | string | no | Email address. |
| `phone` | string | no | Phone number. |
| `tags` | string[] | no | Tags to add. |
| `notes` | string | no | Internal notes, not shown to the client. |

Creates a client card. Nothing is sent to the client, and the card can be edited or removed in Thryv, so the call skips confirmation. Only the first name is required.

Example response:

```json
{
  "client_id": "cl_8f2a91",
  "name": "Sam Lee",
  "email": "client@example.com",
  "tags": [
    "spring"
  ],
  "status": "created"
}
```

### book_appointment

New calendar appointment. Thryv emails the client a booking confirmation. Access: write, asks the user first. REST: `POST /api/v1/thryv/book_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients. |
| `service` | string | yes | Service name from list_services, or a custom title. |
| `start` | datetime | yes | ISO 8601 with time zone. |
| `end` | datetime | no | End time. Default: the service length. |
| `staff` | string | no | Staff member. Default: the primary admin. |
| `price_type` | enum | no | fixed, custom or no_fee. Default: the service setting. |
| `price` | string | no | Price for a fixed-price appointment. |
| `additional_recipients` | string[] | no | More emails that get the booking email. |

Books an appointment on your calendar for a client. Thryv emails the client a booking confirmation, plus any extra recipients you add. End time defaults to the service length and staff to the primary admin. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "ap_51c7e0",
  "client": "Sample Client",
  "service": "Lawn treatment",
  "start": "2026-10-13T09:00:00-05:00",
  "end": "2026-10-13T10:00:00-05:00",
  "staff": "Alex",
  "price": "85.00",
  "confirmation_sent_to": [
    "client@example.com"
  ]
}
```

### mark_no_show

Mark an appointment as a no-show, before its end time. May send your missed appointment email. Access: write, asks the user first. REST: `POST /api/v1/thryv/mark_no_show`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Appointment ID from list_appointments. |

Marks one appointment as a no-show, before its end time. If you set up a missed appointment email in Thryv, it may go out to the client. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "ap_40b2d9",
  "status": "no_show"
}
```

### create_estimate

Itemized estimate on the client card, saved or sent for approval in the client portal. Access: write, asks the user first. REST: `POST /api/v1/thryv/create_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients. |
| `line_items` | object[] | yes | List of items, each with description, quantity and unit_price. |
| `notes` | string | no | Notes shown on the estimate. |
| `send` | boolean | no | Send it to the client now. Default: false. |

Creates an itemized estimate on the client card. With send false it is only saved; with send true it goes to the client for approval in the client portal. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "estimate_id": "est_1180",
  "client_id": "cl_8f2a91",
  "total": "110.00",
  "status": "saved"
}
```

### create_invoice

Invoice on the client card, saved to send later or sent with an online payment link. Access: write, asks the user first. REST: `POST /api/v1/thryv/create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients. |
| `line_items` | object[] | yes | List of items, each with description, quantity and unit_price. |
| `send` | boolean | no | Send it to the client now. Default: false. |

Creates an invoice on the client card from line items. With send false it is saved to send later; with send true it goes to the client with an online payment link. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_2051",
  "client_id": "cl_8f2a91",
  "line_items": [
    {
      "description": "Lawn treatment",
      "quantity": 1,
      "unit_price": "85.00"
    },
    {
      "description": "Edging",
      "quantity": 1,
      "unit_price": "25.00"
    }
  ],
  "total": "110.00",
  "balance_due": "110.00",
  "status": "draft"
}
```

### send_message

Message one or more clients, the same as Send Message on your dashboard. Access: write, asks the user first. REST: `POST /api/v1/thryv/send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_ids` | string[] | yes | Client IDs from list_clients. |
| `subject` | string | yes | Subject line. |
| `message` | string | yes | Message text. |

Sends a message to one or more clients, the same as Send Message on your dashboard. Subject and message text are required. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "sent_to": [
    "cl_8f2a91",
    "cl_20b4d7"
  ],
  "subject": "Open slots next week",
  "status": "sent"
}
```

### reply_to_review

Post a public reply to a review from the Reputation dashboard. Access: write, asks the user first. REST: `POST /api/v1/thryv/reply_to_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | Review ID from list_reviews. |
| `text` | string | yes | Reply text. |

Posts a public reply to one review from the Reputation dashboard. The reply is visible to anyone who reads the review. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rv_3b90c1",
  "status": "published"
}
```

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

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

### Connect Thryv to your agent.

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

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

```
What appointments do I have tomorrow, and who still has an unpaid invoice?
```

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

```
curl https://cotlet.dev/api/v1/thryv/book_appointment \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"client_id":"cl_8f2a91","service":"Lawn treatment","start":"2026-10-13T09:00:00-05:00","staff":"Alex","price_type":"fixed","price":"85.00"}'
```

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

```
{
  "appointment_id": "ap_51c7e0",
  "client": "Sample Client",
  "service": "Lawn treatment",
  "start": "2026-10-13T09:00:00-05:00",
  "end": "2026-10-13T10:00:00-05:00",
  "staff": "Alex",
  "price": "85.00",
  "confirmation_sent_to": [
    "client@example.com"
  ]
}
```

## Why use Cotlet for Thryv?

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

## Is there a Thryv MCP server on GitHub?

No open-source MCP server or hosted scraper for Thryv Business Center is known. The realistic option is the official Zapier app, which can be called from an AI client through Zapier MCP, but it covers only clients, busy times and conversations.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | The primary admin copies a token from Settings > Integrations into Zapier | Request access, sign in to Thryv once in your browser, add one MCP server or API key |
| What it can do | 4 triggers, plus create or find a client, create a busy time or a conversation | Calendar, estimates, invoices, inbox, messages and reviews |
| Write actions | No booking, invoices or estimates | Book, invoice, message and reply, each asking for your OK by default |
| When Thryv changes | Maintained by Thryv and Zapier | Our team tests it daily and fixes it for you; failed calls are free |
| Your Thryv session | A token that only the primary admin can see | Session encrypted in an EU vault, never your password, revoked in one click |
| Where it runs | Zaps you build in advance, or Zapier MCP | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free Zapier plan, paid plans for more volume | 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 Thryv 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 Thryv API cost?

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

**Do I need to be technical?**

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

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

**Who can connect Thryv, and do I need Zapier?**

No Zapier is needed. Cotlet works in your own Thryv Business Center account after you sign in once. Thryv's own Zapier token can be viewed or generated only by the primary admin, and Cotlet does not use it.

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

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

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