[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Podium API and MCP server

> Podium has an official REST API (v4, OAuth 2) but no official MCP server (checked 23 Oct 2026). You cannot just create a key: you build an app in Podium's developer portal and ask for scopes, and Podium's API terms say it must approve you first and may deny access for any reason. Podium's partner terms describe an app review that generally takes about 2 weeks.

Customer messaging platform for local businesses: one Inbox for texts, email and chat, plus Reviews, review invites, Contacts, bulk messages and payment requests.

## What is the Podium API?

Cotlet's Podium API exposes 14 endpoints for your own Podium account: list locations, list conversations, get conversation, list reviews, list contacts, get contact, list payment requests, get bulk message usage, send message, assign conversation, send review invite, reply to review, update contact tags and request payment. The list_locations endpoint returns Podium locations your login can open, with the ID the other tools take. Each endpoint takes simple JSON inputs like location, limit or cursor and works both as an operation of the podium_read or podium_write MCP tool for agents and as a REST call for scripts.

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

Podium has an official REST API (v4, OAuth 2) but no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Podium with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Podium have an official API?

Podium has an official REST API (v4, OAuth 2) but no official MCP server (checked 23 Oct 2026). You cannot just create a key: you build an app in Podium's developer portal and ask for scopes, and Podium's API terms say it must approve you first and may deny access for any reason. Podium's partner terms describe an app review that generally takes about 2 weeks.

| Task | Podium official | Cotlet |
|---|---|---|
| Read conversations and messages | Partly: Podium's guide describes messages as webhook events that Podium sets up for you | Yes |
| Send a text or email | Yes: Scope write_messages | Yes |
| Assign a conversation to a teammate | No: None of the 17 OAuth scopes covers assignment | Yes |
| Read reviews | Yes: Scope read_reviews | Yes |
| Reply to Google and Facebook reviews | Partly: Scope write_reviews exists; the Zapier app has a New Review trigger and no reply action | Yes |
| Send a review invite | Yes: The API creates the invite link; you send it with the message endpoint | Yes |
| Create, update and delete contacts | Yes: Scopes read_contacts and write_contacts | Yes |
| Request a payment, cancel or refund it | Yes: Invoices endpoint, scope write_payments | Yes |
| Read bulk message usage | No: No scope covers it | Yes |

Sources: [Podium developer docs: OAuth 2](https://docs.podium.com/docs/oauth), [Podium developer docs: OAuth scopes](https://docs.podium.com/docs/oauth-scopes), [Podium developer docs: Reading conversations and messages](https://docs.podium.com/docs/sync-messages-from-podium-conversations), [Podium partner terms and API Terms of Use](https://partner-terms.podium.com/)

## Quick reference

```text
Podium has an official REST API (v4, OAuth 2) but no official MCP server (checked 23 Oct 2026). You cannot just create a key: you build an app in Podium's developer portal and ask for scopes, and Podium's API terms say it must approve you first and may deny access for any reason. Podium's partner terms describe an app review that generally takes about 2 weeks.
Cotlet provides a hosted MCP server and REST API for Podium: 14 tools (8 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=podium, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    podium_read, podium_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/podium, each operation at its own route, e.g. POST /api/v1/podium/review-invites
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_locations, list_conversations, get_conversation, list_reviews, list_contacts, get_contact, list_payment_requests, get_bulk_message_usage, send_message, assign_conversation, send_review_invite, reply_to_review, update_contact_tags, request_payment
Confirm      send_message, send_review_invite, reply_to_review, request_payment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/podium-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=podium, requests Podium in the Cotlet console and creates an API key there.
2. The user signs in to Podium once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Podium for agents. 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 Podium 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.
Sign-in: the user signs in to Podium in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Podium only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Podium login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Podium's terms; Cotlet is not affiliated with Podium.
```

## What can an AI agent do in Podium?

Cotlet is best for owners and office managers of local businesses on Podium who want an AI agent to answer reviews, route the Inbox and send review invites without running or fixing a server.

- **[Reply to Google reviews](https://cotlet.dev/integrations/podium-api-mcp-server/reply-to-google-reviews.md)** (runs: daily): "Read the new Google reviews of Riverside Dental that nobody replied to. Thank the 4 and 5 star ones by name and mention something they wrote. For 1 to 3 stars, write a calm reply that gives our phone number. Show me each reply before it posts." → `list_reviews`, `reply_to_review`
- **[Assign Inbox conversations to the right teammate](https://cotlet.dev/integrations/podium-api-mcp-server/assign-inbox-conversations.md)** (runs: daily): "List unassigned Podium conversations at Riverside Dental. Assign billing questions to Dana Reyes, scheduling questions to Sam Ortiz, and tell me about anything else." → `list_conversations`, `get_conversation`, `assign_conversation`
- **[Send review invites from a customer list](https://cotlet.dev/integrations/podium-api-mcp-server/send-review-invites.md)** (runs: weekly): "Here are the patients who finished treatment this week. For each one, find the contact in Podium and send the Review Invitation - Default template. Skip anyone invited in the last 60 days." → `list_contacts`, `send_review_invite`
- **Request payment for finished jobs** (runs: weekly): "For each job on this list, send a Podium payment request with the amount and invoice number. Then list which requests from last week are still pending." → `request_payment`, `list_payment_requests`
- **Tag contacts for the next bulk message** (runs: weekly): "Tag everyone in this list as recall-nov in Podium, then tell me how many bulk messages I have left this month." → `list_contacts`, `update_contact_tags`, `get_bulk_message_usage`

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

Yes. Cotlet does not replace your automation platform: it gives it a Podium 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 reply to google reviews, 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 with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/podium/reviews. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/podium/reviews 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 401 without an API key and 403 while the key has no access to Podium.

### list_locations

Podium locations your login can open, with the ID the other tools take. Access: read. REST: `GET /api/v1/podium/locations`. MCP: `podium_read → list_locations`.

No parameters.

Returns each location of your Podium account with its location_id and name. Use location_id as the location parameter of the other tools. A single-location account returns one row. What you can open follows your own Podium role.

Example response:

```json
{
  "locations": [
    {
      "location_id": "loc_2b81",
      "name": "Riverside Dental",
      "city": "Salt Lake City"
    },
    {
      "location_id": "loc_7c40",
      "name": "Riverside Dental Orthodontics",
      "city": "Provo"
    }
  ]
}
```

### list_conversations

Inbox conversations with channel, contact, last message and assignee. Access: read. REST: `GET /api/v1/podium/conversations`. MCP: `podium_read → list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | no | Location ID from list_locations. Needed when your account has more than one location. |
| `assigned_to` | string | no | A teammate's name as the assign dropdown shows it, or 'unassigned'. |
| `limit` | integer | no | How many rows to return in one call. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists conversations of the Podium Inbox in the order the Inbox shows them, one page at a time; pass next_cursor back as cursor for the next page. Each row has the channel (text, email, Facebook, Google or Instagram), the contact, a preview of the last message and the teammate it is assigned to. assigned_to unassigned returns conversations nobody owns. Use conversation_id with get_conversation, send_message and assign_conversation.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "conv_91d3",
      "channel": "text",
      "contact": "Priya Nair",
      "last_message": "Can I move my cleaning to Friday?",
      "last_message_at": "2026-10-22T16:41:00Z",
      "assigned_to": null
    },
    {
      "conversation_id": "conv_55a0",
      "channel": "email",
      "contact": "Marcus Webb",
      "last_message": "Do you take Delta Dental?",
      "last_message_at": "2026-10-22T14:05:00Z",
      "assigned_to": "Dana Reyes"
    }
  ],
  "next_cursor": null
}
```

### get_conversation

One conversation with its messages, channel and assignee. Access: read. REST: `GET /api/v1/podium/conversations/{conversation_id}`. MCP: `podium_read → get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |
| `limit` | integer | no | How many rows to return in one call. |

Returns the messages of one conversation in the order Podium shows them, with who sent each (the contact or a teammate), the channel and the current assignee. Use it to read the whole thread before you reply or assign it. Reading does not change the conversation.

Example response:

```json
{
  "conversation_id": "conv_91d3",
  "channel": "text",
  "contact": {
    "contact_id": "ct_4410",
    "name": "Priya Nair"
  },
  "assigned_to": null,
  "messages": [
    {
      "from": "contact",
      "body": "Hi, can I move my cleaning to Friday?",
      "sent_at": "2026-10-22T16:41:00Z"
    }
  ]
}
```

### list_reviews

Reviews from your connected review sites, with rating, text and whether you replied. Access: read. REST: `GET /api/v1/podium/reviews`. MCP: `podium_read → list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | no | Location ID from list_locations. Needed when your account has more than one location. |
| `source` | string | no | Review site, for example 'google' or 'facebook'. Default: all connected sites. |
| `rating` | integer | no | Only reviews with this star rating, 1 to 5. |
| `limit` | integer | no | How many rows to return in one call. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the reviews on the Podium Reviews page, one page at a time. Each row has the source site, the star rating, the reviewer, the text, the date, whether a reply exists and can_reply. can_reply is true for Google and Facebook reviews of profiles connected to Podium; Podium cannot post replies on other sites. source and rating narrow the list.

Example response:

```json
{
  "reviews": [
    {
      "review_id": "rev_8f21c4",
      "source": "google",
      "rating": 5,
      "reviewer": "Lena K.",
      "text": "Quick and friendly visit. Dana explained every step.",
      "posted_at": "2026-10-21",
      "replied": false,
      "can_reply": true
    },
    {
      "review_id": "rev_8f1e90",
      "source": "google",
      "rating": 2,
      "reviewer": "Tom R.",
      "text": "Waited 40 minutes past my appointment and nobody called.",
      "posted_at": "2026-10-20",
      "replied": false,
      "can_reply": true
    }
  ],
  "next_cursor": null
}
```

### list_contacts

Contacts from the Podium Contacts page, searchable by name, phone or email. Access: read. REST: `GET /api/v1/podium/contacts`. MCP: `podium_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, phone number or email address to look for. |
| `tag` | string | no | Only contacts with this tag. |
| `limit` | integer | no | How many rows to return in one call. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists contacts one page at a time. query matches name, phone number or email address, the same fields the Contacts search uses. tag keeps only contacts with that tag. Each row has the contact_id, name, phone, email, status and tags. Use contact_id with get_contact and update_contact_tags.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "ct_4410",
      "name": "Priya Nair",
      "phone": "+15555550142",
      "email": "priya@example.com",
      "status": "active",
      "tags": [
        "cleaning"
      ]
    }
  ],
  "next_cursor": null
}
```

### get_contact

One contact with phone, email, status, tags and custom fields. Access: read. REST: `GET /api/v1/podium/contacts/{contact_id}`. MCP: `podium_read → get_contact`.

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

Returns one contact with the fields Podium shows on its profile: name, phone, email, status, tags and the custom fields an admin set up under Settings. Reading does not change the contact.

Example response:

```json
{
  "contact_id": "ct_4410",
  "name": "Priya Nair",
  "phone": "+15555550142",
  "email": "priya@example.com",
  "status": "active",
  "tags": [
    "cleaning"
  ],
  "custom_fields": {
    "next_visit": "2026-11-05"
  }
}
```

### list_payment_requests

Payment requests with amount and status: pending, paid, refunded or canceled. Access: read. REST: `GET /api/v1/podium/payment-requests`. MCP: `podium_read → list_payment_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | no | Location ID from list_locations. Needed when your account has more than one location. |
| `status` | enum | no | pending, paid, refunded or canceled. Default: all. |
| `limit` | integer | no | How many rows to return in one call. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the payment requests of the Payments page, one page at a time. Each row has the invoice number, the customer, the amount and the status. status is pending (nothing paid yet), paid, refunded (in full or in part) or canceled (the link no longer takes payment). Use it to see which requests are still open.

Example response:

```json
{
  "payment_requests": [
    {
      "payment_request_id": "pay_3c19",
      "invoice_number": "INV-1042",
      "customer": "Priya Nair",
      "amount": 480,
      "status": "pending",
      "sent_at": "2026-10-21T10:12:00Z"
    },
    {
      "payment_request_id": "pay_3b77",
      "invoice_number": "INV-1038",
      "customer": "Marcus Webb",
      "amount": 120,
      "status": "paid",
      "sent_at": "2026-10-19T09:30:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_bulk_message_usage

How many bulk messages your plan allows and how many you used. Access: read. REST: `GET /api/v1/podium/bulk-message-usage`. MCP: `podium_read → get_bulk_message_usage`.

No parameters.

Returns what the Bulk Messages tab under Settings shows: the number of bulk messages your plan includes and how many you used. Check it before you plan a send to a long list.

Example response:

```json
{
  "used": 212,
  "limit": 500
}
```

### send_message

Send a text or email from Podium, in an existing conversation or to a phone number or email. Access: write, asks the user first. REST: `POST /api/v1/podium/messages`. MCP: `podium_write → send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | no | Location ID from list_locations. Needed when your account has more than one location. |
| `conversation_id` | string | no | Conversation to answer. Use this or to. |
| `to` | string | no | Phone number or email address for a new conversation. Use this or conversation_id. |
| `body` | string | yes | Message text. |
| `close_after_send` | boolean | no | Close the conversation after sending. Default: false. |

Sends a message under your Podium login. Pass conversation_id to answer in a thread, which uses the channel of that thread, or to to start one with a phone number or an email address. close_after_send closes the conversation after sending, like Send & Close in the Inbox. The message reaches a customer and cannot be unsent. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "msg_7a03",
  "conversation_id": "conv_91d3",
  "channel": "text",
  "status": "sent"
}
```

### assign_conversation

Assign a conversation to one or more teammates. Access: write. REST: `POST /api/v1/podium/conversations/{conversation_id}/assign`. MCP: `podium_write → assign_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |
| `users` | array | yes | Teammate names as the assign dropdown shows them, for example ['Dana Reyes']. |

Sets the assignee of a conversation, as the + Assign icon does in the Inbox. Pass one name, or several to assign more than one teammate. The names are the ones the assign dropdown lists for your account. It reaches no customer and one more call changes the assignment again, so it does not wait for your OK.

Example response:

```json
{
  "conversation_id": "conv_91d3",
  "assigned_to": [
    "Dana Reyes"
  ],
  "status": "assigned"
}
```

### send_review_invite

Send a customer a review invitation with a review link, from a message template. Access: write, asks the user first. REST: `POST /api/v1/podium/review-invites`. MCP: `podium_write → send_review_invite`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | no | Location ID from list_locations. Needed when your account has more than one location. |
| `to` | string | yes | Phone number or email address of the customer. |
| `template` | string | no | Template name. Default: 'Review Invitation - Default'. |

Sends a review invitation to one phone number or email address, using a messaging template such as Review Invitation - Default or Review Invitation Reminder. Podium limits review invitation links for the same contact to one in 60 days, so a second invite inside that window fails and the agent skips it. Connect your review sites in Podium first. The invite reaches a customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invite_id": "inv_52e8",
  "to": "+15555550142",
  "template": "Review Invitation - Default",
  "status": "sent"
}
```

### reply_to_review

Post a public reply to a Google or Facebook review. Access: write, asks the user first. REST: `POST /api/v1/podium/reviews/{review_id}/replies`. MCP: `podium_write → reply_to_review`.

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

Posts a reply under your business name on the review, like Reply on the Reviews page. It works for Google and Facebook reviews of profiles connected to Podium; on any other site the call fails and the review is left for you. A posted reply is public. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rev_8f21c4",
  "source": "google",
  "status": "posted"
}
```

### update_contact_tags

Add or remove tags on a contact. Access: write. REST: `PATCH /api/v1/podium/contacts/{contact_id}/tags`. MCP: `podium_write → update_contact_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |
| `add` | array | no | Tags to add. |
| `remove` | array | no | Tags to remove. |

Adds the tags in add and removes the tags in remove on one contact, like editing tags on the Contacts page. A tag you add is created if it does not exist. Tags reach no customer and one more call undoes the change, so it does not wait for your OK. Automations that filter by contact tag pick the change up on their next run.

Example response:

```json
{
  "contact_id": "ct_4410",
  "tags": [
    "cleaning",
    "recall-nov"
  ]
}
```

### request_payment

Send a customer a payment request with a link to pay by card. Access: write, asks the user first. REST: `POST /api/v1/podium/payment/request`. MCP: `podium_write → request_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location` | string | no | Location ID from list_locations. Needed when your account has more than one location. |
| `to` | string | yes | Customer phone number or email address. |
| `amount` | number | yes | Amount to request, as you would type it in the request form. |
| `description` | string | no | What the payment is for. |
| `invoice_number` | string | no | Your invoice number, shown on the request. |

Sends a payment request to a phone number or an email address, as Request payment does on the Payments page. The customer gets a payment link by text, or by email when you pass an email address. invoice_number and description appear on the request. The request reaches a customer and asks for money. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "payment_request_id": "pay_3c19",
  "invoice_number": "INV-1042",
  "amount": 480,
  "status": "pending",
  "sent_via": "text"
}
```

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

Connecting Podium takes three steps: sign up, sign in to Podium once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Podium to your agent.

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

2. **Sign in to Podium in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Podium there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

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 Podium 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.

```
Read the new Google reviews of Riverside Dental that nobody replied to. Thank the 4 and 5 star ones by name and mention something they wrote. For 1 to 3 stars, write a calm reply that gives our phone number. Show me each reply before it posts.
```

### Call Podium 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 an endpoint under /api/v1/podium with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/podium/review-invites \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"location":"loc_2b81","to":"+15555550142","template":"Review Invitation - Default"}'
```

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

```
{
  "invite_id": "inv_52e8",
  "to": "+15555550142",
  "template": "Review Invitation - Default",
  "status": "sent"
}
```

## Why use Cotlet for Podium?

**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 Podium yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Podium changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Podium to Cotlet?

Yes. You sign in to Podium yourself, in your own Cloud Browser, and we never save your password. Your agents only get Podium once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Podium integration?**

No, Cotlet is independent of Podium. Podium's own API is open only to approved partners. Cotlet works through your own Podium account, the way you use Podium in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Podium in your console: your agents lose access at once and you stay signed in. Signing out of Podium in the browser works too, and Reset browser deletes the whole profile.

## Is there a Podium MCP server on GitHub?

The realistic option is Zapier. Podium has no official MCP server, and no open-source MCP server for a business account turns up (checked 23 Oct 2026). Podium's Zapier app has six triggers (new campaign, invoice, paid invoice, refunded invoice, review, review invite) and six actions (cancel, create or refund an invoice, send a message, two data feed actions). It has no action to reply to a review, assign a conversation or tag a contact. Cotlet works next to Zapier, n8n and Make: it gives an AI agent the Podium screens as tools.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Add the Podium app in Zapier, authorize it, build a Zap per job | Sign up, sign in to Podium once, add one MCP server or API key |
| What it covers | Six triggers and six actions, mostly invoices, review invites and sending a message | Tools for conversations, reviews, contacts, payment requests and review invites |
| When Podium changes | Zapier maintains the app within what the Podium API allows | Our team tests it daily and fixes it for you; failed calls are free |
| Your Podium session | An OAuth connection held by Zapier | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | You reconnect Podium in Zapier | Your Cloud Browser keeps you signed in; if Podium logs you out, your agent gets a link to sign in again |
| Where it runs | Zapier, on a trigger or a schedule | Hosted: Claude Code, Codex, Cursor, n8n, Make, Zapier and scripts, also on a schedule |
| Price | Your Zapier plan | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### 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 Podium 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 your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Podium API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Podium API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Podium account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Podium yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Podium only after you enable it. When Podium signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Podium, sign out of Podium in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. 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.
- **Podium's terms:** You use your own Podium account and stay responsible for following Podium's terms. Cotlet is independent and not affiliated with Podium. [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?**

Sign up free, open Podium in the console and press Request access. Then you create your API key and connect Podium there.

**Do I need to be technical?**

No. You sign in to Podium once in your Cloud Browser, a normal Chrome you open from the console, 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 it safe to connect Podium to Cotlet?**

Yes. You sign in to Podium yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Podium once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Podium sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Podium cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Podium's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Podium sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Podium login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Podium offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a Podium developer app or API approval?**

No. Cotlet works in your own Podium login and does not use the API, so there is no app to build and no review to wait for. Podium's API route needs a developer app and Podium's approval first. Your Podium role still counts: your agent can do what your login can do in Podium.

**Which review sites can my agent reply on?**

Google and Facebook, when those profiles are connected to Podium. Podium replies directly only on those two. For other sites it can send review invitations but not answer reviews, and Yelp and Trustpilot do not allow third-party integrations. list_reviews marks each review with can_reply.

**Is there a limit on review invites?**

Podium limits review invitation links for the same contact to one in 60 days. A second send_review_invite inside that window fails, and your agent skips the contact and lists it for you.

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

No. Every call to send_message, send_review_invite, reply_to_review or request_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. assign_conversation and update_contact_tags run without asking, because they send nothing to anyone and one call undoes it.

**Can I use the Podium API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/podium from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.