Joy has no public API, no developer program and no Zapier app (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Joy with 15 endpoints (7 read, 8 write): your AI agent signs in as you and does the work.
Joy has no public API, no developer program and no Zapier app (checked 11 Oct 2026). Guests, RSVPs and the registry are managed in the Joy dashboard, and the guest list leaves Joy only as a CSV file you download by hand.
Cotlet is best for couples and planners who keep their Joy guest list, RSVPs and registry up to date through an AI agent without running or fixing a server.
Check who has not RSVPed Runs: Weekly
How many guests are coming, and who still has not replied to the RSVP? Your agent calls list_events, get_rsvp_summary and list_guests.
Compare our "Wedding guests" Google Sheet with the Joy guest list: add the new rows as guests with their party and tags, update changed emails and phone numbers, and list anything you are not sure about. Your agent calls list_events, list_guests, add_guest, update_guest and assign_guest_tags.
Our RSVP deadline is May 15. Tell me how many guests are coming, then email an RSVP reminder to every party that has not answered and list the ones you cannot reach. Your agent calls list_events, get_rsvp_summary, list_guests and send_rsvp_reminder.
RSVPs are closed. Give the caterer the number of each meal for everyone attending the reception, plus a list of dietary notes by guest name, and flag anyone with no meal answer. Your agent calls get_rsvp_summary, list_guests and get_guest.
Announce a schedule change
Move the welcome dinner to 7 pm and email the guests about the change. Your agent calls list_schedule, update_schedule_event and send_email_message.
Go through every gift in our Joy registry tracker since the wedding, draft a thank-you for each giver that names what they gave, and send them in batches of ten after I read them. Your agent calls list_received_gifts and send_thank_you_note.
Endpoints
What is the Joy API?
Cotlet's Joy API exposes 15 endpoints for your own Joy account: list events, list guests, get guest, get RSVP summary, list schedule, list registry gifts, list received gifts, add guest, update guest, assign guest tags, update schedule event, add registry gift, send RSVP reminder, send email message and send thank-you note. The list_events endpoint returns Joy events you own or collaborate on, with name, date and website URL. Each endpoint takes simple JSON inputs like event_id, guest_ids or subject and works both as an MCP tool for agents and as a REST call for scripts.
Guest list with party, plus-ones, tags, contact details and RSVP answers per question.
read
Returns guests in guest list order with their party, tags and answers to each RSVP question. Filter by RSVP status, tag or name to narrow it down. Pages hold up to 500 guests; pass next_cursor back as cursor.
POST /api/v1/joy/list_guests
Input
Input: list_guests
Parameter
Type
Description
event_id required
string
Event ID from list_events.
rsvp
enum
all, attending, declined or no_response. Default: all.
Attending, declined and pending counts, with a breakdown of answers to each RSVP question.
read
Returns counts of guests who are attending, declined or have not responded, and for each RSVP question how many guests gave each answer. The counts match the Guest List screen.
Events on your Schedule page with time, time zone, venue, dress code and privacy.
read
Returns the events on your Schedule page in time order. Privacy says whether everyone or only specific guests see an event. Use schedule_item_id with update_schedule_event.
Registry items and cash funds with price, quantity, Our Most Wanted flag and purchased or reserved status.
read
Returns everything on your registry: gifts from any store and cash funds. Each item shows how many are still wanted and whether any were purchased or reserved.
The gift tracker: who bought each gift, order info, cash fund contributions and whether you sent a thank-you.
read
Returns what the Track tab of your Registry shows: the guest who bought each physical gift, the quantity and order info, and what each guest put into a cash fund. Each row says whether a thank-you was sent.
Add a guest to the guest list, optionally into a party with blank plus-ones. Sends nothing.
write
Adds one guest to the guest list. Guests with the same party value are grouped and can RSVP for each other. It sends nothing to the guest and is undone by removing the guest, so it runs without asking.
POST /api/v1/joy/add_guest
Input
Input: add_guest
Parameter
Type
Description
event_id required
string
Event ID from list_events.
first_name required
string
First name, no symbols.
last_name
string
Last name, no symbols.
email
string
Needed for digital cards and email messages.
phone
string
Mobile number, for text messages with Messaging Plus.
party
string
Party name. Guests with the same party are grouped and can RSVP for each other.
plus_ones
integer
Number of blank plus-ones. Default: 0.
name_on_envelope
string
How the party is addressed on envelopes, e.g. The Porter Family.
Change contact details, party or plus-ones, or set or remove an RSVP answer for a guest.
write
Changes the fields you pass and leaves the rest. Setting rsvp_answers records the answer as if the guest gave it; null removes an answer. It sends nothing to the guest and one more call reverts it, so it runs without asking.
POST /api/v1/joy/update_guest
Input
Input: update_guest
Parameter
Type
Description
event_id required
string
Event ID from list_events.
guest_id required
string
Guest ID from list_guests.
fields required
object
Any of first_name, last_name, email, phone, party, plus_ones, name_on_envelope, rsvp_answers ({question: answer or null to remove}).
Add or remove guest tags on several guests at once. Tags control private events and RSVP questions.
write
Adds or removes tags on many guests in one call. New tags are created. Tags can limit who sees a private event or an RSVP question, so check them before the next send. It sends nothing and is undone with one call.
Change an event on your Schedule page. Guests see it on your website right away.
asks first write
Changes the fields you pass on one Schedule event. The new time or venue shows on your public website at once, so guests can see it before any email goes out. By default you confirm each call; you can switch that off for this tool.
POST /api/v1/joy/update_schedule_event
Input
Input: update_schedule_event
Parameter
Type
Description
event_id required
string
Event ID from list_events.
schedule_item_id required
string
Schedule item ID from list_schedule.
fields required
object
Any of name, description, start, end, time_zone, venue, dress_code, privacy (everyone or specific_guests).
Add a gift from any store by product URL. Joy fills in the title and price when it can.
write
Adds a gift to your registry from a product page. Joy reads the title and price from the page when it can; set them yourself otherwise. Mark it Our Most Wanted to highlight it. It reaches no one directly and one removal undoes it, so it runs without asking.
RSVP reminder with a link to your RSVP page, by default to every guest who has not responded.
asks first write
Sends the Joy RSVP reminder. Without guest_ids it goes to every guest with no response. Guests with no email are skipped and counted in the response. Email is free; text needs Messaging Plus. By default you confirm each call; you can switch that off for this tool.
POST /api/v1/joy/send_rsvp_reminder
Input
Input: send_rsvp_reminder
Parameter
Type
Description
event_id required
string
Event ID from list_events.
guest_ids
string[]
Recipients. Default: guests with no response.
delivery
enum
email, text or both. Text needs Messaging Plus. Default: email.
Email update to selected guests or tags, with a button linking to your event website.
asks first write
Sends a freeform email to the guests you pick by ID or tag, with a button to your event website. Guests without an email address do not get it. Scheduling for later needs Messaging Plus. By default you confirm each call; you can switch that off for this tool.
POST /api/v1/joy/send_email_message
Input
Input: send_email_message
Parameter
Type
Description
event_id required
string
Event ID from list_events.
guest_ids
string[]
Recipients by guest ID.
tags
string[]
Recipients by guest tag. Use guest_ids or tags.
subject required
string
Email subject line.
message required
string
Message body.
send_at
datetime
Schedule for later, ISO 8601. Needs Messaging Plus. Default: now.
Digital thank-you email to the guest who gave a gift, sent from the gift tracker.
asks first write
Sends one thank-you to the guest who gave the gift, and marks the gift as thanked in the tracker. By default you confirm each call; you can switch that off for this tool.
How do I connect Joy to Claude Code, Codex or Cursor?
Connecting Joy takes three steps: request access, sign in to Joy once, then add one MCP server or call the REST API with the same key.
Connect Joy over MCP
1
Create an account
Sign up and add Joy in the console. Your API key is there too.
2
Sign in to Joy once
Open the connect page from the console and sign in to Joy the way you always do. We keep the session, never your password, and you can revoke it anytime.
Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
4
Ask your agent
Prompt
How many guests are coming, and who still has not replied to the RSVP?
Ask in plain words. Your agent finds the Joy 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 Joy over REST
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
Call a tool
curl
curl https://cotlet.dev/api/v1/joy/send_rsvp_reminder \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"event_id":"evt_8KQ2mZ","delivery":"email","subject":"Two weeks left to RSVP"}'
Every tool is a POST endpoint at /api/v1/joy/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.
You get plain JSON back, ready for your script. A failed call costs nothing.
Why Cotlet
Why use Cotlet for Joy? 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 Joy 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 Joy changes, the tool pauses until we fix it.
Failed calls cost nothing.
Alternatives
Is there a Joy MCP server on GitHub?
Open-source export scripts exist on GitHub. They are usually maintained by one person, log in to Joy with a headless browser, click Export All Guests and only read the guest list. You run and fix them yourself; Cotlet hosts the same kind of access for you, adds writes, and our team keeps it working.
Cotlet compared with a GitHub export script
GitHub export script
Cotlet
Setup
Clone the repo, install it, store your Joy login in a config file
Request access, sign in to Joy once, add one MCP server or API key
When Joy 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 Joy session
Your password in a file on your machine
Only the session, encrypted in an EU vault, revoked in one click
When the session expires
The script fails or logs in again with the stored password
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 machine or server, on a cron
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 Joy 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 Joy in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.
Endpoint health
verified 2h ago
list_eventspassing
list_guestspassing
get_guestpassing
get_rsvp_summarypassing
list_schedulepassing
+ 10 more endpoints
15/15 passing latest checkself-healing
joy.txt
Joy has no public API, no developer program and no Zapier app (checked 11 Oct 2026). Guests, RSVPs and the registry are managed in the Joy dashboard, and the guest list leaves Joy only as a CSV file you download by hand.
Cotlet provides a hosted MCP server and REST API for Joy: 15 tools (7 read, 8 write).
Access Request access at https://cotlet.dev/app/signup?app=joy; we email the API key.
MCP server https://cotlet.dev/mcp/v1
REST base https://cotlet.dev/api/v1/joy
Auth Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools list_events, list_guests, get_guest, get_rsvp_summary, list_schedule, list_registry_gifts, list_received_gifts, add_guest, update_guest, assign_guest_tags, update_schedule_event, add_registry_gift, send_rsvp_reminder, send_email_message, send_thank_you_note
Confirm update_schedule_event, send_rsvp_reminder, send_email_message, send_thank_you_note (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/joy-api-mcp-server.md
How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=joy (Joy is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Joy 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 Joy 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 Joy 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 Joy's terms; Cotlet is not affiliated with Joy.
Can Joy automations run on a schedule in n8n, Make or Zapier?
Yes. Cotlet does not replace your automation platform: it gives it a Joy 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 check who has not rsvped, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.
Where to run Joy 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/joy/{tool}.
Schedule Trigger node.
Make
HTTP module: POST https://cotlet.dev/api/v1/joy/{tool} with an Authorization: Bearer header and a JSON body.
Scenario schedule.
Zapier
Webhooks by Zapier: POST https://cotlet.dev/api/v1/joy/{tool} with the same header and body.
Schedule by Zapier trigger.
Your own script
POST https://cotlet.dev/api/v1/joy/{tool} with your API key.
cron or GitHub Actions.
Pricing & limits
How much does the Joy API cost?
Free 7-day trial with 5,000 credits, no card needed. After that, the Joy 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 Joy 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 Joy 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 Joy tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Joy 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.
Joy's terms
You use your own Joy account and stay responsible for following Joy's terms. Cotlet is independent and not affiliated with Joy. Terms
Request access and pick Joy. Cotlet reviews each request and emails you your API key.
Do I need to be technical?
No. You sign in to Joy 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 Joy session would leave my computer.
Cotlet keeps your Joy session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.
Do I need Messaging Plus?
Only for text messages and scheduled sends. Email reminders and email messages sent now work without it, as in the Joy dashboard (Joy Help, checked 11 Oct 2026).
Do collaborators on my event work too?
Cotlet acts as the Joy account you sign in with, so it can do what that account can do in the dashboard. Joy shows events you own or collaborate on.
Can my agent post or send messages in Joy without asking me?
No. Every call to update_schedule_event, send_rsvp_reminder, send_email_message or send_thank_you_note waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_guest, update_guest, assign_guest_tags, add_registry_gift runs without asking, because it sends nothing to anyone and one call undoes it.
Can I use the Joy 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/joy/{tool} from the HTTP Request node.
