[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) # Wild Apricot API and MCP server > Yes, Wild Apricot has a REST API with an admin side and a member side, but no official MCP server (checked 23 Oct 2026). Its help center calls the API "intended for use by developers": you authorize an application, get an API key, exchange it for an OAuth token and write the calls yourself. Membership management software for clubs, associations and nonprofits: contacts, membership levels, events, email, invoices and payments, plus the member website. ## What is the Wild Apricot API? Cotlet's Wild Apricot API exposes 12 endpoints for your own Wild Apricot account: list contacts, get a contact, list membership levels, list events, list event registrants, list invoices, approve a membership application, reject a membership application, check in an event registrant, send an email, record a payment on an invoice and register a contact for an event. The list_contacts endpoint returns contacts and members with their level, status and renewal date; filter by name, email or status. Each endpoint takes simple JSON inputs like contact_id, cursor or event_id and works both as an operation of the wild_apricot_read or wild_apricot_write MCP tool for agents and as a REST call for scripts. - **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md) - **Endpoints:** 12 (6 read, 6 write) - **Updated:** 2026-10-19 Yes, Wild Apricot has a REST API with an admin side and a member side, but no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Wild Apricot with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does Wild Apricot have an official API? Yes, Wild Apricot has a REST API with an admin side and a member side, but no official MCP server (checked 23 Oct 2026). Its help center calls the API "intended for use by developers": you authorize an application, get an API key, exchange it for an OAuth token and write the calls yourself. | Task | Wild Apricot official | Cotlet | |---|---|---| | List and search contacts | Yes: Contacts API; 40 contact-list requests per minute | Yes | | Read a contact's membership status and renewal date | Yes: Contacts API; you write the code | Yes | | List events and their registrants | Yes: Events and event registrations calls | Yes | | Approve or reject membership applications | Partly: The Contacts API edits member records; Approve and Reject are buttons on the Membership tab of the admin | Yes | | Check in event registrants | Yes: Registration update; Zapier's app exposes it as an optional checkedIn field | Yes | | Email contacts or an event's registrants | Partly: Sending email by API appears as a suggestion on the Developers forum | Yes | | Read invoices and record payments | Yes: Invoices and Payments admin API calls | Yes | | Register a contact for an event | Yes: Event registrations API; Zapier's app has Add or Update Event Registration | Yes | Sources: [Wild Apricot Help: Using WildApricot's API](https://gethelp.wildapricot.com/en/articles/182-using-wildapricot-s-api), [Wild Apricot Help: Admin API v2 calls](https://gethelp.wildapricot.com/en/categories/32-wild-apricot-admin-api-v2), [Wild Apricot Help: Payments admin API call](https://gethelp.wildapricot.com/en/articles/494-payments-admin-api-call), [Zapier: WildApricot integrations](https://zapier.com/apps/wildapricot/integrations) ## Quick reference ```text Yes, Wild Apricot has a REST API with an admin side and a member side, but no official MCP server (checked 23 Oct 2026). Its help center calls the API "intended for use by developers": you authorize an application, get an API key, exchange it for an OAuth token and write the calls yourself. Cotlet provides a hosted MCP server and REST API for Wild Apricot: 12 tools (6 read, 6 write). Access Sign up at https://cotlet.dev/app/signup?app=wild-apricot, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools wild_apricot_read, wild_apricot_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/wild-apricot, each operation at its own route, e.g. POST /api/v1/wild-apricot/invoices/{invoice_id}/payments Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_contacts, get_contact, list_membership_levels, list_events, list_event_registrants, list_invoices, approve_membership_application, reject_membership_application, check_in_registrant, send_email, record_payment, register_contact_for_event Confirm approve_membership_application, reject_membership_application, send_email, record_payment, register_contact_for_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/wild-apricot-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=wild-apricot, requests Wild Apricot in the Cotlet console and creates an API key there. 2. The user signs in to Wild Apricot once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Wild Apricot 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 Wild Apricot 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 Wild Apricot 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 Wild Apricot 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 Wild Apricot 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 Wild Apricot's terms; Cotlet is not affiliated with Wild Apricot. ``` ## What can an AI agent do in Wild Apricot? Cotlet is best for Wild Apricot administrators at clubs, associations and nonprofits who want an AI agent to approve applications, follow up after events and record payments without running or fixing a server. - **[Approve pending membership applications](https://cotlet.dev/integrations/wild-apricot-api-mcp-server/approve-membership-applications.md)** (runs: daily): "Go through the Pending - New members in my Wild Apricot. Approve applicants who have paid and whose form answers fit our rules, reject obvious spam, and leave the rest for me with a one-line reason." → `list_membership_levels`, `list_contacts`, `get_contact`, `approve_membership_application`, `reject_membership_application` - **[Thank event attendees and follow up with no-shows](https://cotlet.dev/integrations/wild-apricot-api-mcp-server/email-event-attendees-after-event.md)** (runs: weekly): "Find the Wild Apricot event that ended yesterday. Email everyone who was checked in a thank-you with the photo album link, and send a short "sorry we missed you" to registrants who were not checked in." → `list_events`, `list_event_registrants`, `send_email` - **[Record bank transfers against unpaid invoices](https://cotlet.dev/integrations/wild-apricot-api-mcp-server/record-offline-payments-against-invoices.md)** (runs: weekly): "Here are this week's bank transfers. Match each to an unpaid Wild Apricot invoice by payer and amount, record it as a bank transfer payment, and list the ones you could not match." → `list_invoices`, `get_contact`, `record_payment` - **Follow up with lapsed members** (runs: weekly): "List members with the Lapsed status and a renewal date in the last 30 days, and email each one a short personal note with a link to renew." → `list_contacts`, `send_email` - **Register a caller for an event**: "Register Maria Silva for the Autumn volunteer day with the Member ticket, activate it without an invoice and do not send a confirmation yet." → `list_events`, `list_contacts`, `register_contact_for_event` ## Can Wild Apricot automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a Wild Apricot 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 approve pending membership applications, 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/wild-apricot/membership-levels. | 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/wild-apricot/membership-levels with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 12 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 Wild Apricot. ### list_contacts Contacts and members with their level, status and renewal date; filter by name, email or status. Access: read. REST: `GET /api/v1/wild-apricot/contacts`. MCP: `wild_apricot_read → list_contacts`. | Parameter | Type | Required | Description | |---|---|---|---| | `search` | string | no | Part of a name or an email address. | | `membership_status` | enum | no | Active, Lapsed, Pending - New, Pending - Renewal, Pending - Level change or Suspended. | | `membership_level` | string | no | Level name from list_membership_levels. | | `cursor` | string | no | Next page cursor from the previous call. | Returns contacts the way the Contacts list shows them, a page at a time; pass next_cursor back as cursor for the next page. membership_status is one of Active, Lapsed, Pending - New, Pending - Renewal, Pending - Level change or Suspended. A contact who is not a member has no level and no status. member_since and renewal_due come from the Membership tab. Archived contacts are left out. Example response: ```json { "contacts": [ { "contact_id": 48213, "name": "Nora Elwood", "email": "nora@example.com", "membership_level": "Individual", "membership_status": "Pending - New", "member_since": null, "renewal_due": null }, { "contact_id": 47990, "name": "Sam Okafor", "email": "sam@example.com", "membership_level": "Student", "membership_status": "Active", "member_since": "2025-09-04", "renewal_due": "2026-09-04" } ], "next_cursor": "2" } ``` ### get_contact One contact with the application fields, membership tab, balance and event registrations. Access: read. REST: `GET /api/v1/wild-apricot/contacts/{contact_id}`. MCP: `wild_apricot_read → get_contact`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_id` | integer | yes | Contact ID from list_contacts. | Returns the contact record: the fields on the profile, the Membership tab (level, status, member since, renewal due), the contact balance and the event registrations from the Events tab. balance is the amount still owed across open invoices. Use it before approve_membership_application to see whether the applicant has paid. Example response: ```json { "contact_id": 48213, "name": "Nora Elwood", "email": "nora@example.com", "fields": { "Organization": "Elwood Cycles", "City": "Portland" }, "membership": { "level": "Individual", "status": "Pending - New", "member_since": null, "renewal_due": null }, "balance": 0, "event_registrations": [ { "event_id": 7210, "name": "Saturday group ride", "ticket_type": "Member" } ] } ``` ### list_membership_levels Membership levels with their renewal type and whether applications need approval or payment. Access: read. REST: `GET /api/v1/wild-apricot/membership-levels`. MCP: `wild_apricot_read → list_membership_levels`. No parameters. Returns the levels under Members > Levels. renewal_type is Application date, Specific date or Lifetime. approval_required mirrors the setting Membership applications must be approved by administrator, payment_required mirrors Payment has to be received in full, and public mirrors Public can apply for this level. Example response: ```json { "levels": [ { "level_id": 1203, "name": "Individual", "renewal_type": "Specific date", "approval_required": true, "payment_required": true, "public": true }, { "level_id": 1204, "name": "Lifetime", "renewal_type": "Lifetime", "approval_required": false, "payment_required": true, "public": false } ] } ``` ### list_events Events with date, registrants and the attendance Wild Apricot shows. Access: read. REST: `GET /api/v1/wild-apricot/events`. MCP: `wild_apricot_read → list_events`. | Parameter | Type | Required | Description | |---|---|---|---| | `search` | string | no | Part of the event name. | | `starts_after` | date | no | Only events that start on or after this date. | | `starts_before` | date | no | Only events that start on or before this date. | | `cursor` | string | no | Next page cursor from the previous call. | Returns the events from Events > Event list, a page at a time. registered is the number of registrations and checked_in the number of registrants with check-in recorded, which is what the Attendance column counts. Use event_id with list_event_registrants, send_email and register_contact_for_event. Example response: ```json { "events": [ { "event_id": 7210, "name": "Saturday group ride", "start_date": "2026-10-17", "registered": 22, "checked_in": 18 }, { "event_id": 7244, "name": "Autumn volunteer day", "start_date": "2026-11-07", "registered": 9, "checked_in": 0 } ], "next_cursor": null } ``` ### list_event_registrants Registrants of one event with ticket type, guests, payment and check-in; filter by checked in. Access: read. REST: `GET /api/v1/wild-apricot/event-registrants`. MCP: `wild_apricot_read → list_event_registrants`. | Parameter | Type | Required | Description | |---|---|---|---| | `event_id` | integer | yes | Event ID from list_events. | | `checked_in` | boolean | no | true for checked-in registrants, false for the rest. Omit for everyone. | | `cursor` | string | no | Next page cursor from the previous call. | Returns the Registrants & invitees tab of one event, a page at a time. checked_in true shows what the Checked in filter shows; false returns the registrants who were not checked in. paid is false while the registration has an unpaid invoice. counts covers the whole event, not only this page. Example response: ```json { "registrants": [ { "registration_id": 553101, "contact_id": 47990, "name": "Sam Okafor", "email": "sam@example.com", "ticket_type": "Member", "guests": 0, "paid": true, "checked_in": true }, { "registration_id": 553104, "contact_id": 48050, "name": "Lena Ortiz", "email": "lena@example.com", "ticket_type": "Member", "guests": 1, "paid": true, "checked_in": false } ], "counts": { "registered": 22, "checked_in": 18 }, "next_cursor": "2" } ``` ### list_invoices Invoices with contact, amount, open balance and status. Access: read. REST: `GET /api/v1/wild-apricot/invoices`. MCP: `wild_apricot_read → list_invoices`. | Parameter | Type | Required | Description | |---|---|---|---| | `status` | enum | no | unpaid, partially_paid or paid. | | `contact_id` | integer | no | Only invoices of this contact. | | `cursor` | string | no | Next page cursor from the previous call. | Returns invoices a page at a time. status is unpaid, partially_paid or paid. balance is what is still due, so a partially paid invoice shows less than amount. Use invoice_id with record_payment. Amounts are in the currency of your payment settings. Example response: ```json { "invoices": [ { "invoice_id": 90417, "number": "1043", "contact_id": 47990, "contact": "Sam Okafor", "amount": 95, "balance": 95, "status": "unpaid", "created": "2026-10-01" }, { "invoice_id": 90431, "number": "1057", "contact_id": 48050, "contact": "Lena Ortiz", "amount": 120, "balance": 60, "status": "partially_paid", "created": "2026-10-05" } ], "next_cursor": null } ``` ### approve_membership_application Approve a Pending - New application so the membership becomes Active. Access: write, asks the user first. REST: `POST /api/v1/wild-apricot/contacts/{contact_id}/membership-application/approve`. MCP: `wild_apricot_write → approve_membership_application`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_id` | integer | yes | Contact ID from list_contacts. | Opens the contact, goes to the Membership tab and selects Approve. The status becomes Active and Member since is set to the approval date. The applicant can get the Application activation email set on the level. On a recurring monthly level, an approval after the next renewal date makes Wild Apricot charge each month between the application and the approval. Needs a full administrator or a membership manager. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "contact_id": 48213, "name": "Nora Elwood", "membership_level": "Individual", "membership_status": "Active", "member_since": "2026-10-23" } ``` ### reject_membership_application Reject a Pending - New application; the person stays in your database as a contact. Access: write, asks the user first. REST: `POST /api/v1/wild-apricot/contacts/{contact_id}/membership-application/reject`. MCP: `wild_apricot_write → reject_membership_application`. | Parameter | Type | Required | Description | |---|---|---|---| | `contact_id` | integer | yes | Contact ID from list_contacts. | Selects Reject on the Membership tab. Wild Apricot keeps the record as a contact. For a paid application it cancels the application, unsettles the payment and voids the invoice; it does not refund, so the response names the payer and the amount. For an unpaid application the tool voids and deletes the invoice, then cancels. Needs a full administrator or a membership manager. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "contact_id": 48377, "name": "Promo Account", "status": "rejected", "invoice": "voided", "refund_due": null } ``` ### check_in_registrant Record that a registrant attended, or undo it. Reaches no one. Access: write. REST: `POST /api/v1/wild-apricot/registrations/{registration_id}/registrant/check`. MCP: `wild_apricot_write → check_in_registrant`. | Parameter | Type | Required | Description | |---|---|---|---| | `registration_id` | integer | yes | Registration ID from list_event_registrants. | | `checked_in` | boolean | no | false undoes a check-in. Default: true. | | `guests` | integer | no | Number of guests to check in with this registration. Default: 0. | | `check_in_unpaid` | boolean | no | Check in a registrant who has not fully paid. Default: false. | Clicks the Check in circle beside the registrant in Registrants & invitees. guests sets how many of a registration's guests are checked in. A registrant with an unpaid registration is not checked in unless check_in_unpaid is true. Only full administrators and event managers can check in. It sends nothing and is undone by calling it again with checked_in false, so it does not wait for your OK. Example response: ```json { "registration_id": 553104, "name": "Lena Ortiz", "checked_in": true, "guests_checked_in": 1, "paid": true } ``` ### send_email Email chosen contacts or the registrants of an event, now or scheduled. Access: write, asks the user first. REST: `POST /api/v1/wild-apricot/emails`. MCP: `wild_apricot_write → send_email`. | Parameter | Type | Required | Description | |---|---|---|---| | `subject` | string | yes | Subject line. | | `body` | string | yes | Plain text of the message. Links are allowed. | | `contact_ids` | array | no | Contact IDs to email, from list_contacts or list_event_registrants. | | `event_id` | integer | no | Email the registrants of this event, from list_events. | | `checked_in_only` | boolean | no | With event_id, only registrants who were checked in. Default: false. | | `schedule_at` | datetime | no | Deliver later, in your organization's timezone. Omit to send now. | Composes a plain email under Communication > Email. Give contact_ids, or event_id (with checked_in_only for the attendees). Wild Apricot sends one email per unique address and hides other recipients. Attachments are not possible; put a link in the body. Sent now, it waits in Wild Apricot's queue for a few minutes to a few hours. schedule_at uses your organization's timezone. Needs a full administrator, membership manager, events manager or donations manager. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "email_id": 20318, "status": "queued", "recipients": 18, "event_id": 7210, "scheduled_for": null, "subject": "Thank you for riding with us on Saturday" } ``` ### record_payment Record an offline payment against an invoice and settle it. Access: write, asks the user first. REST: `POST /api/v1/wild-apricot/invoices/{invoice_id}/payments`. MCP: `wild_apricot_write → record_payment`. | Parameter | Type | Required | Description | |---|---|---|---| | `invoice_id` | integer | yes | Invoice ID from list_invoices. | | `amount` | number | yes | Amount received, at most the invoice amount. | | `date` | date | yes | Date the payment was received. | | `payment_type` | string | yes | How it was received, one of the payment types in your account, such as check, cash or wire transfer. | Selects Record payment on the invoice, enters the amount, date and payment type and saves. The amount must be equal to or less than the invoice amount. A smaller amount marks the invoice partially paid, the full balance marks it fully paid, and contact balances update. Wild Apricot sends no receipt for a manual payment. Needs a full administrator, membership manager, events manager or donations manager. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "payment_id": 71002, "invoice_id": 90417, "contact": "Sam Okafor", "amount": 95, "date": "2026-10-21", "payment_type": "Bank transfer", "invoice_status": "paid", "balance": 0 } ``` ### register_contact_for_event Add a contact as a registrant of an event, with or without an invoice. Access: write, asks the user first. REST: `POST /api/v1/wild-apricot/events/{event_id}/contacts/{contact_id}/for-event`. MCP: `wild_apricot_write → register_contact_for_event`. | Parameter | Type | Required | Description | |---|---|---|---| | `event_id` | integer | yes | Event ID from list_events. | | `contact_id` | integer | yes | Contact ID from list_contacts. | | `ticket_type` | string | yes | Ticket type name of the event. | | `invoice` | enum | no | generate_invoice or activate_without_invoice. Default: activate_without_invoice. | | `send_notification` | boolean | no | Send the event registration email to the registrant. Default: false. | Uses Add registrant on the event, picks the contact and the ticket type and saves. invoice chooses Generate invoice or Activate without invoice. An administrator can register people after the registration limit is reached. Wild Apricot sends no email for a manual registration, so send_notification is false unless you set it. Needs a full administrator, membership manager or events manager. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "registration_id": 553190, "event_id": 7244, "contact_id": 48050, "ticket_type": "Member", "invoice": "none", "notification_sent": false } ``` ## How do I connect Wild Apricot to Claude Code, Codex or Cursor? Connecting Wild Apricot takes three steps: sign up, sign in to Wild Apricot 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 Wild Apricot to your agent. 1. **Create an account** Sign up and add Wild Apricot in the console. Your API key is there too. 2. **Sign in to Wild Apricot in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Wild Apricot 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 Wild Apricot 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. ``` Go through the Pending - New members in my Wild Apricot. Approve applicants who have paid and whose form answers fit our rules, reject obvious spam, and leave the rest for me with a one-line reason. ``` ### Call Wild Apricot 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/wild-apricot 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/wild-apricot/invoices/90417/payments \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"amount":95,"date":"2026-10-21","payment_type":"Bank transfer"}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "payment_id": 71002, "invoice_id": 90417, "contact": "Sam Okafor", "amount": 95, "date": "2026-10-21", "payment_type": "Bank transfer", "invoice_status": "paid", "balance": 0 } ``` ## Why use Cotlet for Wild Apricot? **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 Wild Apricot 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 Wild Apricot changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect Wild Apricot to Cotlet? Yes. You sign in to Wild Apricot yourself, in your own Cloud Browser, and we never save your password. Your agents only get Wild Apricot 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 Wild Apricot integration?** No, Cotlet is independent of Wild Apricot. Wild Apricot's own API is too limited for this work. Cotlet works through your own Wild Apricot account, the way you use Wild Apricot 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 Wild Apricot in your console: your agents lose access at once and you stay signed in. Signing out of Wild Apricot in the browser works too, and Reset browser deletes the whole profile. ## Is there a Wild Apricot MCP server on GitHub? Wild Apricot has an official app on Zapier and a connector on Make. They react to events such as a new contact, a lapsed or renewed membership or an event registration, and they write contact and registration records. They do not read the admin and decide: an agent that reviews applicants, thanks the people who checked in or matches bank transfers to invoices needs tools it can choose between. Cotlet gives the agent those tools in your own admin session, and works next to Zapier or Make, not instead of them. | | Zapier | Cotlet | |---|---|---| | Setup | Connect your account, then build a Zap for each trigger and action | Sign up, sign in to Wild Apricot once, add one MCP server or API key | | What it does | Fixed triggers and actions: contact created, membership lapsed or renewed, event registration created | Tools your agent picks per request: read, approve, check in, email, record payments | | When Wild Apricot changes | Zapier maintains its WildApricot app | Our team tests it daily and fixes it for you; failed calls are free | | Your access | You authorize the app connection | Your own admin sign-in in a Cloud Browser in the EU, session only, no password stored | | Upkeep | You keep each Zap working | Nothing to host or update | | Where it runs | In Zapier, when a trigger fires | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Zapier's own plans | 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 Wild Apricot 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 Wild Apricot API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the Wild Apricot 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 Wild Apricot 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 Wild Apricot 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 Wild Apricot only after you enable it. When Wild Apricot 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 Wild Apricot, sign out of Wild Apricot 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. - **Wild Apricot's terms:** You use your own Wild Apricot account and stay responsible for following Wild Apricot's terms. Cotlet is independent and not affiliated with Wild Apricot. [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 Wild Apricot in the console and press Request access. Then you create your API key and connect Wild Apricot there. **Do I need to be technical?** No. You sign in to Wild Apricot 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 Wild Apricot to Cotlet?** Yes. You sign in to Wild Apricot yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Wild Apricot 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 Wild Apricot 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 Wild Apricot 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 Wild Apricot's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Wild Apricot 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 Wild Apricot 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?** Wild Apricot 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). **Which Wild Apricot administrator role does my account need?** A full administrator can use every tool. A membership manager can approve applications and record payments, and an events manager can check in registrants (only full administrators and event managers can), email registrants and record payments. Wild Apricot lists these roles on its Account administrators page, and a call without the role fails. **Do Wild Apricot's API limits apply to Cotlet?** Wild Apricot documents API limits of 40 requests per minute for contact lists, 120 for a contact by ID and 400 for other requests, and it requires pagination since 1 Nov 2025. Cotlet works in your signed-in admin session in the Cloud Browser, not through the API, so you need no API key, no application authorization and no OAuth code. **How fast does an email from my agent arrive?** Wild Apricot puts a manual email in its delivery queue, and it can take from a few minutes to a few hours to reach everyone. Use schedule_at to deliver at a set time in your organization's timezone. Wild Apricot sends one email per unique address and cannot attach files. **Can my agent post or send messages in Wild Apricot without asking me?** No. Every call to approve_membership_application, reject_membership_application, send_email, record_payment or register_contact_for_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. check_in_registrant runs without asking, because it sends nothing to anyone and one call undoes it. **Can I use the Wild Apricot 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/wild-apricot 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.