Live

Partiful logo

Partiful API and MCP server

partiful.com

Partiful has no public API and no developer docs (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Partiful with 13 endpoints (5 read, 8 write): your AI agent signs in as you and does the work.

Endpoints
13 5 read, 8 write
Updated
How Cotlet connects your agent to Partiful
  1. Your agent

    Claude Code, Codex, Cursor or a script

  2. Cotlet

    MCP server and REST API · 13 endpoints

    cotlet.dev/mcp/v1

  3. Partiful logo

    Partiful

    Signed in as you on partiful.com

You sign in once. We never store your password.

Official API

Does Partiful have an official API?

Partiful has no public API and no developer docs (checked 11 Oct 2026). Its help center documents no webhooks, Zapier or Make connection; guest data leaves Partiful only as a CSV that you export by hand from the guest list with the Export CSV button.

What Partiful's own tools do compared with Cotlet
Task Partiful official Cotlet
Create, edit and duplicate events No Yes
List guests and RSVPs No Yes
Export the guest list with questionnaire answers Partly Manual Export CSV button on the guest list, no automation Yes
Invite past guests or emails No Yes
Approve pending guests No Yes
Check in guests at the door No Yes
Send Text Blasts No Yes

Sources: Partiful Help: How can I export my guest list? · Partiful Help: How do I send a text blast? · Partiful Help: How do I approve all of my Pending guests at once? · Partiful Help: How can I send Partiful invites via email? · Partiful Help: What event reminders do you send? · Partiful Help: Can I set up recurring events?

Common use cases

What can an AI agent do in Partiful?

Cotlet is best for Partiful hosts who run recurring events and want their AI agent to text guests, export RSVPs and handle invites without running or fixing a server.

  • Text guests by RSVP status Runs: Weekly

    Text everyone who is Going or Maybe to my rooftop dinner that the door code is 4512 and we start 30 minutes late. Your agent calls list_events and send_text_blast.

  • Export RSVPs and questionnaire answers to a sheet Runs: Weekly

    Export everyone who is Going to my supper club and add the new people, with their dietary answers, to the members Google Sheet. Your agent calls list_events, export_guest_list and list_guests.

  • Approve pending guests by their answers Runs: Daily

    Approve all pending guests to my launch party who answered the questionnaire with a company name, and list the rest for me. Your agent calls list_guests, get_event and approve_guests.

  • Re-invite past guests to a recurring event Runs: Monthly

    Copy last month's book club for November 14 at 7pm and invite the people who came. Your agent calls list_events, duplicate_event, list_past_guests and invite_guests.

  • Summarize guest questionnaire answers Runs: Weekly

    Who is going to Friday's dinner, and what dietary restrictions did they put in the questionnaire? Your agent calls list_events and list_guests.

Endpoints

What is the Partiful API?

Cotlet's Partiful API exposes 13 endpoints for your own Partiful account: list events, get event, list guests, export guest list, list past guests, create event, update event, duplicate event, invite guests, approve guests, check in guests, send Text Blast and cancel event. The list_events endpoint returns events you host, with date, status and guest counts. Each endpoint takes simple JSON inputs like event_id, limit or cursor and works both as an MCP tool for agents and as a REST call for scripts.

All endpoints · 13 total

missing one? request an endpoint

  • POST

    list_events

    read

    Returns your events with start time, whether the event is canceled and counts of guests by RSVP status. Use event_id from each item in the other tools. Pages hold up to 50 events; pass next_cursor back as cursor for the next page.

    POST /api/v1/partiful/list_events

    Input

    Input: list_events
    Parameter Type Description
    when enum upcoming, past or all. Default: upcoming.
    limit integer 1 to 50. Default: 20.
    cursor string Next page cursor from the previous call.

    Example response

    {
      "events": [
        {
          "event_id": "evt_hK3vQ9xL",
          "title": "Rooftop dinner",
          "start_at": "2026-10-17T19:00:00-04:00",
          "status": "active",
          "guests": {
            "going": 28,
            "maybe": 9,
            "cant_go": 4,
            "invited": 31,
            "pending": 0
          }
        },
        {
          "event_id": "evt_pL8wN2aD",
          "title": "Launch party",
          "start_at": "2026-10-24T20:00:00-04:00",
          "status": "active",
          "guests": {
            "going": 52,
            "maybe": 6,
            "cant_go": 11,
            "invited": 60,
            "pending": 3
          }
        }
      ],
      "next_cursor": null
    }
  • POST

    get_event

    read

    Returns one event with its details and the settings you chose in Event Settings: guest limit, waitlist, Guest Approval and the Guest Questionnaire questions. Use it before update_event to see what is set now.

    POST /api/v1/partiful/get_event

    Input

    Input: get_event
    Parameter Type Description
    event_id required string Event ID from list_events.

    Example response

    {
      "event_id": "evt_hK3vQ9xL",
      "title": "Rooftop dinner",
      "start_at": "2026-10-17T19:00:00-04:00",
      "end_at": "2026-10-17T23:00:00-04:00",
      "location": "21 Mercer St, New York",
      "description": "Bring a drink to share.",
      "rsvp_deadline": "2026-10-15T18:00:00-04:00",
      "max_guests": 60,
      "waitlist": true,
      "guest_approval": false,
      "questions": [
        "Dietary restrictions"
      ],
      "url": "https://partiful.com/e/hK3vQ9xLexample"
    }
  • POST

    list_guests

    read

    Returns the guests of one event, each with RSVP status, whether they are checked in and their answers to your Guest Questionnaire. Filter by status to see only pending guests or only the ones going. Pages hold up to 200 guests; pass next_cursor back as cursor for the next page.

    POST /api/v1/partiful/list_guests

    Input

    Input: list_guests
    Parameter Type Description
    event_id required string Event ID from list_events.
    status enum all, going, maybe, cant_go, invited, waitlist or pending. Default: all.
    checked_in boolean Only guests who are checked in (true) or not (false).
    limit integer 1 to 200. Default: 100.
    cursor string Next page cursor from the previous call.

    Example response

    {
      "guests": [
        {
          "guest_id": "g_41aa",
          "name": "Maya Chen",
          "status": "going",
          "checked_in": false,
          "answers": [
            {
              "question": "Dietary restrictions",
              "answer": "Vegetarian"
            }
          ]
        },
        {
          "guest_id": "g_41ab",
          "name": "Leo Park",
          "status": "going",
          "checked_in": false,
          "answers": [
            {
              "question": "Dietary restrictions",
              "answer": "Peanut allergy"
            }
          ]
        }
      ],
      "next_cursor": null
    }
  • POST

    export_guest_list

    read

    Returns a link to the CSV that Partiful's Export CSV button produces, limited to the RSVP statuses you choose. It includes Guest Questionnaire answers. Your agent or n8n flow reads the file and appends the rows to a sheet or CRM.

    POST /api/v1/partiful/export_guest_list

    Input

    Input: export_guest_list
    Parameter Type Description
    event_id required string Event ID from list_events.
    statuses string[] RSVP statuses to include: going, maybe, cant_go, invited, waitlist, pending. Default: all.

    Example response

    {
      "event_id": "evt_hK3vQ9xL",
      "statuses": [
        "going"
      ],
      "guests": 28,
      "download_url": "https://cotlet.dev/api/v1/files/exports/partiful/evt_hK3vQ9xL-going.csv"
    }
  • POST

    list_past_guests

    read

    Returns people you can invite again: guests who attended your events and mutuals. Filter to one past event to invite only the people who came to it. Use user_id from each item in invite_guests. Pages hold up to 200 people.

    POST /api/v1/partiful/list_past_guests

    Input

    Input: list_past_guests
    Parameter Type Description
    from_event_id string Only people from this past event.
    query string Search by name.
    limit integer 1 to 200. Default: 50.
    cursor string Next page cursor from the previous call.

    Example response

    {
      "people": [
        {
          "user_id": "u_2f81",
          "name": "Maya Chen",
          "attended": 3
        },
        {
          "user_id": "u_2f93",
          "name": "Leo Park",
          "attended": 2
        }
      ],
      "next_cursor": null
    }
  • POST

    create_event

    write

    Creates an event page on your account. Nobody is invited and nothing is sent, so there is no confirmation; one call to update_event or cancel_event changes it. Guest Approval and the Guest Questionnaire are set here, the same way as in Event Settings.

    POST /api/v1/partiful/create_event

    Input

    Input: create_event
    Parameter Type Description
    title required string Event title.
    start_at required datetime ISO 8601 with time zone.
    end_at datetime ISO 8601 with time zone.
    location string Address or place name.
    description string Event details shown on the page.
    rsvp_deadline datetime Last moment guests can RSVP.
    max_guests integer Guest limit; with the waitlist on, extra RSVPs go to the waitlist.
    guest_approval boolean Guests ask to get on the list and you approve them. Default: false.
    questions string[] Guest Questionnaire questions, short answer.

    Example response

    {
      "event_id": "evt_bK7dR3nM",
      "title": "Book club: November",
      "start_at": "2026-11-14T19:00:00-05:00",
      "status": "active",
      "url": "https://partiful.com/e/bK7dR3nMexample"
    }
  • POST

    update_event

    write

    Changes the fields you pass and leaves the rest as it is. It sends nothing itself, so there is no confirmation, and another call restores the old values. Use get_event first to see the current values.

    POST /api/v1/partiful/update_event

    Input

    Input: update_event
    Parameter Type Description
    event_id required string Event ID from list_events.
    fields required object Any of title, start_at, end_at, location, description, rsvp_deadline, max_guests, guest_approval.

    Example response

    {
      "event_id": "evt_hK3vQ9xL",
      "updated": [
        "location"
      ],
      "location": "88 Bleecker St, New York"
    }
  • POST

    duplicate_event

    write

    Does what Clone Event does in Partiful: copies the event details to a new event on the date you give. Guests are not copied, so re-invite them with invite_guests. It sends nothing, so there is no confirmation.

    POST /api/v1/partiful/duplicate_event

    Input

    Input: duplicate_event
    Parameter Type Description
    event_id required string Event ID from list_events.
    start_at required datetime Start of the new event, ISO 8601 with time zone.

    Example response

    {
      "event_id": "evt_bK7dR3nM",
      "copied_from": "evt_aQ4tX9cE",
      "start_at": "2026-11-14T19:00:00-05:00",
      "guests": 0
    }
  • POST

    invite_guests

    write

    Invites people you pick from list_past_guests and sends email invites to the addresses you give. Partiful caps invites per event at 1,000 in total and 500 by email; a call over the cap fails. Invitees reached by email still log in with their phone number to RSVP. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/partiful/invite_guests

    Input

    Input: invite_guests
    Parameter Type Description
    event_id required string Event ID from list_events.
    user_ids string[] People from list_past_guests.
    emails string[] Email addresses to invite.

    Example response

    {
      "event_id": "evt_bK7dR3nM",
      "invited": 2,
      "by_email": 0,
      "status": "sent"
    }
  • POST

    approve_guests

    write

    Marks the guests you name as Approved on an event that has Guest Approval on. Only approved guests have access to the event. Guests you leave alone stay Pending. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/partiful/approve_guests

    Input

    Input: approve_guests
    Parameter Type Description
    event_id required string Event ID from list_events.
    guest_ids required string[] Guest IDs from list_guests.

    Example response

    {
      "event_id": "evt_pL8wN2aD",
      "approved": 2,
      "still_pending": 1
    }
  • POST

    check_in_guests

    write

    Checks in the guests you name, like checking them in manually from the guest list. Guests are not notified, and set undo to true to remove a check-in, so it runs without asking first.

    POST /api/v1/partiful/check_in_guests

    Input

    Input: check_in_guests
    Parameter Type Description
    event_id required string Event ID from list_events.
    guest_ids required string[] Guest IDs from list_guests.
    undo boolean Remove the check-in instead. Default: false.

    Example response

    {
      "event_id": "evt_hK3vQ9xL",
      "checked_in": 2,
      "undo": false
    }
  • POST

    send_text_blast

    write

    Sends one Text Blast to the guests in the statuses you pick, the same as New Blast on the event page. It reaches guests who RSVP'd or were invited directly through Partiful; guests invited by email get it by email until they RSVP. Returns how many people it went to and how many blasts are left. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/partiful/send_text_blast

    Input

    Input: send_text_blast
    Parameter Type Description
    event_id required string Event ID from list_events.
    message required string Message text.
    statuses required string[] Who receives it: going, maybe, cant_go, invited.

    Example response

    {
      "blast_id": "bl_8Fq2Lw0Zr4",
      "event_id": "evt_hK3vQ9xL",
      "recipients": 37,
      "by_status": {
        "going": 28,
        "maybe": 9
      },
      "blasts_left": 7,
      "sent_at": "2026-10-17T18:42:05-04:00"
    }
  • POST

    cancel_event

    write

    Cancels the event the way Cancel Event does in Partiful. Guests are notified; Partiful has no way to cancel without telling them. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/partiful/cancel_event

    Input

    Input: cancel_event
    Parameter Type Description
    event_id required string Event ID from list_events.

    Example response

    {
      "event_id": "evt_hK3vQ9xL",
      "status": "canceled",
      "guests_notified": true
    }

Setup

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

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

Connect Partiful over MCP

  1. 1

    Create an account

    Sign up and add Partiful in the console. Your API key is there too.

  2. 2

    Sign in to Partiful once

    Open the connect page from the console and sign in to Partiful the way you always do. We keep the session, never your password, and you can revoke it anytime.

  3. 3

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

  4. 4

    Ask your agent

    Prompt

    Text everyone who is Going or Maybe to my rooftop dinner that the door code is 4512 and we start 30 minutes late.

    Ask in plain words. Your agent finds the Partiful 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.

Call Partiful over REST

  1. 1

    Export your API key

    Shell

    export COTLET_API_KEY="cotlet_..."

    Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

  2. 2

    Call a tool

    curl

    curl https://cotlet.dev/api/v1/partiful/send_text_blast \
      -H "Authorization: Bearer $COTLET_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"event_id":"evt_hK3vQ9xL","message":"Door code is 4512. We start at 7:30, see you soon!","statuses":["going","maybe"]}'

    Every tool is a POST endpoint at /api/v1/partiful/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

  3. 3

    Read the result

    Example response · send_text_blast

    {
      "blast_id": "bl_8Fq2Lw0Zr4",
      "event_id": "evt_hK3vQ9xL",
      "recipients": 37,
      "by_status": {
        "going": 28,
        "maybe": 9
      },
      "blasts_left": 7,
      "sent_at": "2026-10-17T18:42:05-04:00"
    }

    You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for Partiful? Hosted, safe and kept working.

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

Alternatives

Is there a Partiful MCP server on GitHub?

Yes. Community Partiful MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, copy a login token from your browser, and keep it running yourself; the ones we found only read events and guests. Cotlet hosts the same kind of server for you, and our team keeps it working.

Cotlet compared with a GitHub MCP server
GitHub MCP server Cotlet
Setup Clone or install it, copy a login token from your browser into a config file, add it to each MCP client Request access, sign in to Partiful once, add one MCP server or API key
When Partiful 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 Partiful session A token 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 copy a new token by hand We keep it alive; if Partiful 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 Partiful 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

For AI agents

Cotlet for Partiful in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

  • list_events passing
  • get_event passing
  • list_guests passing
  • export_guest_list passing
  • list_past_guests passing

+ 8 more endpoints

13/13 passing latest check self-healing

partiful.txt

Partiful has no public API and no developer docs (checked 11 Oct 2026). Its help center documents no webhooks, Zapier or Make connection; guest data leaves Partiful only as a CSV that you export by hand from the guest list with the Export CSV button.
Cotlet provides a hosted MCP server and REST API for Partiful: 13 tools (5 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=partiful; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/partiful
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_events, get_event, list_guests, export_guest_list, list_past_guests, create_event, update_event, duplicate_event, invite_guests, approve_guests, check_in_guests, send_text_blast, cancel_event
Confirm      invite_guests, approve_guests, send_text_blast, cancel_event (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/partiful-api-mcp-server.md

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

Automations

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

Yes. Cotlet does not replace your automation platform: it gives it a Partiful 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 text guests by rsvp status, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

Where to run Partiful automations through Cotlet, and how to schedule them
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/partiful/{tool}. Schedule Trigger node.
Make HTTP module: POST https://cotlet.dev/api/v1/partiful/{tool} with an Authorization: Bearer header and a JSON body. Scenario schedule.
Zapier Webhooks by Zapier: POST https://cotlet.dev/api/v1/partiful/{tool} with the same header and body. Schedule by Zapier trigger.
Your own script POST https://cotlet.dev/api/v1/partiful/{tool} with your API key. cron or GitHub Actions.

Pricing & limits

How much does the Partiful API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Partiful 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.

Cotlet plan sizes: price, monthly credits and price per credit
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.

About Cotlet

How Cotlet holds your access

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

Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to Partiful 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 Partiful tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Partiful 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.
Partiful's terms
You use your own Partiful account and stay responsible for following Partiful's terms. Cotlet is independent and not affiliated with Partiful. Terms
Contact
Questions about the company, security or an app: contact@cotlet.dev
About Cotlet

Frequently asked questions

How do I get access?

Request access and pick Partiful. Cotlet reviews each request and emails you your API key.

Do I need to be technical?

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

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

Is there a limit on how many Text Blasts I can send?

Yes. Partiful allows up to 10 Text Blasts per event. send_text_blast returns blasts_left so your agent knows how many remain. Source: Partiful Help, "How do I send a text blast?"

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

No. Every call to invite_guests, approve_guests, send_text_blast or cancel_event waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_event, update_event, duplicate_event, check_in_guests runs without asking, because it sends nothing to anyone and one call undoes it.

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

Give your agent access to Partiful.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.