[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.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) # Humanitix API and MCP server: Let your AI agent run your Humanitix events. > Humanitix has a public API (v1.29.3) that reads events, orders, tickets and tags and can check a ticket in or out, but no MCP server and no endpoint to refund, comp, create a discount code or send an email (checked 31 Oct 2026). Cotlet runs 12 Humanitix tools hosted, over MCP for agents and REST for scripts. Refund tickets, issue comps, make discount codes and email buyers in Humanitix. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST. [MCP setup](https://cotlet.dev/integrations/humanitix-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/humanitix-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Humanitix - Page: https://cotlet.dev/integrations/humanitix-api-mcp-server ## What can you automate in Humanitix? - Refund tickets for guests who cannot come - Cancel an event and tell buyers first - Issue complimentary tickets from a guest list - Create discount codes for members - Email a reminder before every event - Resend lost order confirmations ## Does Humanitix have an MCP server or an API? - The API key comes from account > advanced > public API key. A new key breaks the old one, and the limit is 200 requests a minute. - Zapier has 6 Humanitix triggers, from New Order to New Attendee Check-In, and one search, Search Events. It has no action that changes an order. - A community MCP server on GitHub wraps the same API with 9 read-only tools. | What you need | Zapier | Humanitix API | Cotlet | |---|---|---|---| | Read events, orders and tickets | Search events, new-order triggers | Yes | Yes | | Refund or cancel tickets | No | No | Yes, after your OK | | Complimentary tickets | No | No | Yes, after your OK | | Discount codes | No | No | Yes, after your OK | | Email campaigns to buyers | No | No | Yes, after your OK | | Works without writing code | Yes | No | Yes | Checked 31 Oct 2026. Sources: [Humanitix Help: Public API documentation](https://help.humanitix.com/en/articles/8888275-public-api-documentation), [Humanitix Public API: OpenAPI spec](https://api.humanitix.com/v1/documentation/json), [Humanitix on Zapier](https://zapier.com/apps/humanitix/integrations), [Humanitix Help: Zapier](https://help.humanitix.com/en/articles/8906254-use-zapier-to-connect-humanitix-with-your-web-apps-and-crm) ## How does Cotlet connect to Humanitix? 1. **Sign in to Humanitix.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Humanitix password, and no refund, ticket or email goes out until you approve it. ## Connect Humanitix to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Enable Humanitix for agents.** Open a free Cotlet account, log in to Humanitix in its Cloud Browser and press Enable for agents. 2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as a new MCP server or connector in your agent. 3. **Sign the connection.** Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console. Humanitix rides on `https://cotlet.dev/mcp/v1` together with the other apps on your account. If you switch Humanitix on after connecting, refresh the connector to load the ticket and order tools. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-humanitix \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-humanitix": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-humanitix] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: humanitix_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: humanitix_write ``` ## How to use the Humanitix REST API ### Create your Cotlet API key Create a Cotlet API key with access to Humanitix and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Humanitix in Cotlet and enable it for agents. Account access: Your own Humanitix host account (it must open the events, orders and email campaigns your agent works on). ### Make your first Humanitix API request REST: ``` curl https://cotlet.dev/api/v1/humanitix/events \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read events and apply the operation limits A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "humanitix", "tool": "list_events", "result": { "events": [ { "event_id": "6531a0c4e2b7d4001f3c91a2", "name": "Harbour Quiz Night", "starts_at": "2026-11-14T19:00:00+11:00", "status": "published", "tickets_sold": 132 }, { "event_id": "6531a1d8e2b7d4001f3c91b7", "name": "Kids Craft Morning", "starts_at": "2026-11-21T10:00:00+11:00", "status": "published", "tickets_sold": 57 } ], "next_cursor": null } } ``` Lists the events on the events tab. Each row carries the event_id the other tools take, the start date, whether the event is published and the tickets sold. Use `get_event` for ticket types and settings. `cursor`: Next page cursor from the previous call. Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination. ### Humanitix workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Schedule a reminder email to the buyers of each event this week. Use `send_email_campaign`; each call waits for your approval by default. | | Make | HTTP > Make a request | Create a discount code for each member on a sheet. Use `create_discount_code`; each call waits for your approval by default. | | Python or Node.js | REST API | Search the orders of an event by email, name or order ID. Use `list_orders` with the `event_id` from this list. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Humanitix; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/humanitix-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Humanitix API endpoints and MCP tools ### Events, orders and attendees Orders are found by order ID, name or email, the three keys Humanitix searches by. Answers to per-ticket checkout questions sit with the attendees. - **List events** (`list_events`, read): Your events with date, status and tickets sold. - **Get event** (`get_event`, read): One event with its dates, ticket types and sales. - **List orders** (`list_orders`, read): Orders of an event, searchable by order ID, name or email. - **Get order** (`get_order`, read): One order with its tickets and payment details. - **List attendees** (`list_attendees`, read): Ticket holders of an event, filtered by ticket type or cancelled tickets. ### Refunds, resends and stopping sales Refunds go back to the card used and take 2 to 5 business days. A cancelled ticket is restocked. A resend goes to the address on the order. - **Refund or cancel tickets** (`refund_tickets`, write, asks first): Cancel tickets of an order, refund them, or both. - **Resend order confirmation** (`resend_order`, write, asks first): Email the order confirmation and digital tickets to the buyer again. - **Stop ticket sales** (`stop_sales`, write, asks first): Stop all ticket sales of an event. ### Complimentary tickets and codes Comps count toward capacity and can exceed it. A discount code applies per ticket, not to a packaged ticket. - **Create complimentary order** (`create_manual_order`, write, asks first): Issue complimentary tickets to a guest through a manual order. - **Create discount code** (`create_discount_code`, write, asks first): Create a percentage or fixed-amount discount code for an event. ### Emails and copies A campaign reaches buyers, or attendees if you collected an email per ticket. A duplicated event is a draft that nobody sees. - **Send email campaign** (`send_email_campaign`, write, asks first): Email the buyers or attendees of an event now or on a schedule. - **Duplicate event** (`duplicate_event`, write): Copy an event into a new draft. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/humanitix-api-mcp-server#tools ## Who can see my Humanitix session, and how do I revoke it? - **What we store.** Your logged-in Humanitix profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 12 Humanitix tools. Never the cookie or your payout details. - **What the session sees.** What your login opens: events, buyers, emails, answers to checkout questions. - **What no tool touches.** Payouts, bank details, team members, publishing and deleting events. - **Use a narrower login if you like.** Humanitix lists team permissions on every plan. Use a login that opens only the events the agent works on. - **How to cut access.** Disable for agents, reset the browser or delete the API key. Qualys SSL Labs, securityheaders.com and Mozilla Observatory grade our site A+ ([live results](https://cotlet.dev/security.md)). A SOC 2 report or third-party pentest does not exist yet. ## Is it against Humanitix's terms? Account safety > You will not: ... Access, monitor, extract, or copy any Site Content or information of the Websites using any robot, spider, scraper, or other automated means or any manual process for any purpose without Humanitix's express written permission. > > [Humanitix Event Host Terms of Use, last updated 11 Sep 2026, read 31 Oct 2026](https://static.humanitix.com/pdfs/organiser_terms.html) The terms never mention AI agents. The clause is aimed at scraping, yet "other automated means" can be read to cover an agent that works in your own console. The terms also say that if you share login details, Humanitix "will consider their activities to have been authorised by you". We found no public case of a host suspended for automation (checked 31 Oct 2026). Humanitix can suspend an account under its terms, so decide with that risk in view. How we keep your account looking like you: - Your own host login, typed in by you - One Cloud Browser with its own IP and cookies - Refunds, comps, codes and emails wait for your OK - No tool publishes, deletes or pays out - If Humanitix objects, we pause the Humanitix tools for everyone within 24 h > Humanitix's API allows 200 requests a minute. The agent works at the speed of a person in the console, so spread a long refund list over an hour, not a few seconds. ## What happens when Humanitix changes? - **12 h** between tests of the Humanitix order and event reads - **24 h** between tests of refunds and emails buyers would get - **$0** for a call to a Humanitix tool paused for repair When Humanitix reworks the orders report or the refund screen, the fix lands on our side. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Finds the right order.** Buyer email plus event, so a second event of the same buyer stays untouched. 2. **Reads the tickets.** Cancelled tickets and swapped tickets are reported, not refunded twice. 3. **Waits for your OK.** Order, tickets and amount show up in your Cotlet console. 4. **Reports the money.** Amount per order, skipped orders and buyers not found. | Action | Undo | |---|---| | Refund tickets | No, the money goes back to the buyer's card | | Cancel tickets | No, they are restocked for the next buyer | | Resend an order confirmation | No, but a second copy harms nothing | | Create complimentary tickets | Cancel them with a refund of 0 | | Create a discount code | Change it by hand under promote > discounts | | Send an email campaign | No, once it is sent | | Duplicate an event | Delete the draft by hand in Humanitix | | Stop ticket sales | Not by a tool | 6 of the 7 writes ask first: refund_tickets, resend_order, create_manual_order, create_discount_code, send_email_campaign, stop_sales. They move money, email buyers or change the price. duplicate_event makes an unpublished draft, so it runs at once. The 5 reads run at once. Turn the wait off per tool once a nightly run has earned your trust. > Humanitix refunds only if funds are available, and only to the card used. For a cancelled event, send the email campaign first: after refunds the campaign tool no longer reaches those ticket holders. MCP call: ``` { "name": "refund_tickets", "arguments": { "event_id": "6531a0c4e2b7d4001f3c91a2", "order_id": "K4TR9WNB", "ticket_ids": [ "tk_70211", "tk_70212" ] } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/humanitix/events/6531a0c4e2b7d4001f3c91a2/tickets/refund \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"order_id":"K4TR9WNB","ticket_ids":["tk_70211","tk_70212"]}' ``` Response: ``` { "order_id": "K4TR9WNB", "cancelled_tickets": [ "tk_70211", "tk_70212" ], "refunded": 50, "currency": "AUD", "status": "refund_requested" } ``` A cron job or script reaches the same tools over REST at `/api/v1/humanitix`, with the same key and price. A Zapier trigger such as New Order can start that script. The tools table lists the REST path of each tool. ## How much does the Humanitix MCP server cost? **About $13 a month** for a host with 3 events a month, 2,220 credits. Humanitix keeps charging its ticket fee as before. | Job | Calls | Credits | |---|---|---| | Refund a guest who cannot come | 3 × 6 | 180 | | Resend a confirmation that never arrived | 2 × 8 | 160 | | Complimentary ticket for a guest | 2 × 10 | 200 | | Member discount code | 2 × 5 | 100 | | Reminder email, weekly | 2 × 4 | 80 | | Cloud Browser, 30 days | | 1,500 | | Total | | 2,220 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Same price on every plan The month is our example: 3 events, 6 refunds, 8 resends, 10 comps, 5 discount codes and 4 reminders. Humanitix has no subscription; the Standard fee on its Australian page is 4% + $0.99 per paid ticket, excluding GST (31 Oct 2026). Dollars at the $29 pack rate. ## Humanitix MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [kevinnz/humanitix-mcp](https://github.com/kevinnz/humanitix-mcp) | Python MCP server over the Humanitix API, MIT, 9 tools: events, event dates, orders, tickets, check-in count, sales summary. | Read-only, one maintainer, 0 stars, last push 28 Sep 2026. You install it and keep an API key in a local file. | | [Zapier](https://zapier.com/apps/humanitix/integrations) | Triggers for new orders, attendees, check-ins and events; Search Events. | No action that refunds, issues or emails. | | [Rakazo](https://rakazo.com/integrations/humanitix) | An AI agent that fetches paginated events and tags. | Built on the same API, so reads only. | | Your own script on the [Public API](https://help.humanitix.com/en/articles/8888275-public-api-documentation) | All reads, check-in and check-out. | Needs a developer, and no refund, comp, code or email endpoint exists. | Pick Zapier to push new orders into a sheet or CRM. Pick the API if you have a developer and need reads at volume. Pick Cotlet when the agent should answer the guest emails: refund, comp, code and remind. ## Who runs Cotlet Take Group sp. z o.o. builds and runs Cotlet. The company is registered in Poland, EU (VAT PL6342984273), has worked since 2019 and was founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Humanitix tools to contact@cotlet.dev. ## Humanitix API and MCP: questions ### How do I get access? Create a free account at https://cotlet.dev, pick Humanitix under Integrations in the console and log in to Humanitix in its Cloud Browser. Your trial starts at once and asks for no card. ### How do I connect Humanitix to ChatGPT or Claude? Sign up at cotlet.dev, log in to Humanitix once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Humanitix account through Cotlet, in their phone apps too. ### What can ChatGPT do in Humanitix? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Humanitix: refund tickets for guests who cannot come; cancel an event and tell buyers first; issue complimentary tickets from a guest list. You ask in plain words, and anything that reaches other people waits for your OK first. ### Which Humanitix account does my agent need? Your own host login. Refunds, manual orders, discount codes and email campaigns are host screens, so the account must open them for the event. Cotlet does not use the Humanitix API, which needs an API key from account > advanced and returns data only (checked 31 Oct 2026). ### Can my agent refund after the event? Yes, if funds are available. Humanitix says hosts can process refunds and cancellations anytime and are not bound by the event refund policy. Refunds go only to the card used and take 2 to 5 business days. An order is never deleted. ### Does it work in every country? Humanitix runs country sites for Australia, New Zealand, the US, Canada, the UK and Fiji. You log in with the host account you already use, and the tools follow the screens it shows. ### Can the agent publish or delete an event? No. duplicate_event makes an unpublished draft, and you publish it yourself in Humanitix. No tool deletes an event, an order or a guest. ### Is the MCP server different from the REST API? Only the entrance differs. Both carry the same 12 tools, inputs and answers, one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Humanitix? No. Cotlet is independent and not affiliated with Humanitix Limited. ### Can I use the Humanitix API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.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.