[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) # Weezevent API and MCP server: Let your AI agent run your Weezevent back office. > Weezevent has a REST API for events, tickets and participants, documented for registered partners, and no MCP server (checked 31 Oct 2026). It cannot create discount codes, send invitations or request refunds. Cotlet runs 13 Weezevent tools hosted, over MCP for agents and REST for scripts. Orders, attendees, discount codes, invitations and refund requests for your Weezevent events. 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/weezevent-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/weezevent-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Weezevent - Page: https://cotlet.dev/integrations/weezevent-api-mcp-server ## What can you automate in Weezevent? - Read orders and reservations - List attendees by ticket and source - Create partner discount codes - Send invitations to guests - Request refunds after a cancellation - Report who came through the gates ## Does Weezevent have an MCP server or an API? - The API key sits in the back office under Tools > API Keys. The only writes in the API are scanner settings and control point names. - Zapier has an official Weezevent app: two triggers, New Event and New Transaction, and one action, Add New Attendee. - The API bans keys over 600 requests a minute for 30 minutes and asks apps to store what they read. | What you need | Weezevent API | Zapier | Cotlet | |---|---|---|---| | Read events and attendees | Yes | New Event trigger | Yes | | Read orders and buyers | No order endpoints | New Transaction trigger | Yes | | Create discount codes | No | No | Yes, after your OK | | Send invitations | No | No | Yes, after your OK | | Request a refund or resend an order | No | No | Yes, after your OK | | Add one attendee by email | Not documented | Add New Attendee | Invitations only | | Offered by Weezevent | Yes, for partners | Yes, official app | Uses the back office | Checked 31 Oct 2026. Sources: [Weezevent API documentation](https://api.weezevent.com/), [Weezevent API fair use](https://api.weezevent.com/doc/fair-use), [Zapier: Weezevent integrations](https://zapier.com/apps/weezevent-da56471/integrations), [Weezevent Help: Refunding participants](https://help.weezevent.com/en/articles/13408120-refunding-participants) ## How does Cotlet connect to Weezevent? 1. **Sign in to Weezevent.** 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 Weezevent password, and no refund, invitation or discount code goes out until you approve it. ## Connect Weezevent 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 Weezevent for agents.** Sign up, log in to Weezevent in its Cloud Browser, then press Enable for agents. 2. **Add the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent. 3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console. One shared address, `https://cotlet.dev/mcp/v1`, also carries Weezevent next to your other apps. If you enable Weezevent after connecting, refresh the connector so the new tools show up. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-weezevent \ 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-weezevent": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-weezevent] 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: weezevent_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: weezevent_write ``` ## How to use the Weezevent REST API ### Create your Cotlet API key Create a Cotlet API key with access to Weezevent and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Weezevent in Cotlet and enable it for agents. Account access: Your own Weezevent organizer account, the one you use in the back office. ### Make your first Weezevent API request REST: ``` curl "https://cotlet.dev/api/v1/weezevent/events/ev_4410/orders?status=Reserved&limit=25" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read orders 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": "weezevent", "tool": "list_orders", "result": { "orders": [ { "order_number": "C26E418207O52914", "buyer": "Tom Weber", "email": "tom@example.com", "origin": "Box Office", "status": "Reserved", "tickets": 2, "amount": 48, "currency": "EUR" } ], "next_cursor": null } } ``` Returns the rows of Attendees > Manage orders with the number of tickets and the amount paid for each order. Reserved means ordered but not yet paid. Orders are per event, so call `list_events` first to get the `event_id`. Replace `ev_4410` with your own event ID. Filter by `origin`, `status`, `date_from`, `date_to` or `refund_requested` to narrow the list. Pass `result.next_cursor` unchanged as `cursor` until it is null, and keep the same filters while paging. Compare order status as well as order numbers when refreshing your destination. ### Weezevent workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Read the attendees of an event with their source and promo code. Use `list_attendees` to build a daily sales sheet in your configured business report. | | Make | HTTP > Make a request | Read the discount codes of an event with their rules. Use `list_discount_codes` to compare codes against your campaign list. | | Python or Node.js | REST API | Read a check list after the show. Use `get_participation_report` to count who passed each access point in your configured report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Weezevent; 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/weezevent-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Weezevent API endpoints and MCP tools ### Events, orders and attendees Read only. Orders and attendees are per event, so list_events comes first. Deleted tickets show only with the Deleted status. - **List events** (`list_events`, read): List the events of your account with their dates and sales status. - **List orders** (`list_orders`, read): List the orders of an event, filtered by origin, status, date or refund request. - **Get order** (`get_order`, read): Read one order with its tickets, buyer and summary by rate. - **List attendees** (`list_attendees`, read): List the attendees of an event with ticket type, source and status. - **Get participation report** (`get_participation_report`, read): Read who passed which access point of a check list. ### Discount codes Codes apply per ticket, not per order. Automatic creation makes up to 100 codes at once. - **List discount codes** (`list_discount_codes`, read): List the discount codes of an event with their rules. - **Create discount codes** (`create_discount_codes`, write, asks first): Create one discount code, or up to 100 with a prefix. - **Switch a discount code on or off** (`set_discount_code_active`, write, asks first): Activate or deactivate a discount code. ### Invitations, refunds and order changes Free invitations are capped at 1000 per account and 500 per event. Refund requests cover online orders only. - **Send invitations** (`send_invitations`, write, asks first): Send free tickets to named guests with a custom message. - **Request refund** (`request_refund`, write, asks first): Ask Weezevent to refund the buyer's card for an online order. - **Resend order** (`resend_order`, write, asks first): Email the order and its tickets to the buyer again. - **Mark order paid** (`mark_order_paid`, write, asks first): Turn a reservation into a paid order. - **Delete ticket** (`delete_ticket`, write, asks first): Remove a ticket from the attendees database so it can be sold again. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/weezevent-api-mcp-server#tools ## Who can see my Weezevent session, and how do I revoke it? - **What we store.** Your logged-in Weezevent profile, encrypted with AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 13 Weezevent tools. Never the cookie or your login. - **What the session sees.** Your events: orders, buyer emails, attendees, discount codes. - **What no tool touches.** Payouts, bank details, ticket prices, password and deleting events. - **If Weezevent asks to verify.** A code goes to you. You type it in, we never do. - **How to cut access.** Disable for agents, reset the browser, or change your Weezevent password. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). There is no SOC 2 report or third-party pentest yet. ## Is it against Weezevent's terms? Account safety > The Organiser is required to keep its login details and the password used to set up the event secret and under no circumstances may WEEZEVENT be held liable in the event of fraudulent use thereof. > > [Weezevent organizer terms, General Requirements, read 31 Oct 2026](https://weezevent.com/en-gb/terms-of-use/) The same terms let Weezevent suspend parts of the agreement "in the event of misuse of its services". They name no bots, scraping or AI agents, and we found no public case of a Weezevent account closed for automation (checked 31 Oct 2026). The API's fair-use page limits keys, not back-office logins. Cotlet works through the back office, and Weezevent could still read it as automation. How we keep your account looking like you: - Your own organizer account, logged in by you - One Cloud Browser with its own IP and cookies, so no new-device check every call - Refunds, invitations, codes and order mail wait for your OK - No tool changes prices, payouts or bank details - If Weezevent objects, we pause the Weezevent tools for everyone within 24 h > Send invitations to people who agreed to receive them, and send a big list over a few days. ## What happens when Weezevent changes? - **12 h** between tests of the Weezevent reads - **$0** for a call to a Weezevent tool paused for repair When Weezevent moves a button or renames a menu, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the order.** Online orders only; a reservation or box office order stops the refund. 2. **Lists what it will do.** Every order and ticket count, before anything is sent. 3. **Waits for your OK.** The request shows up in your Cotlet console first. 4. **Reports the result.** Orders refunded, tickets covered, anything that failed. | Action | Undo | |---|---| | Create discount codes | Deactivate them; they stay in the list | | Send invitations | No, the email is out; delete the tickets by hand | | Request a refund | No, Weezevent processes it and its fees apply | | Resend an order | No, the email is out | | Mark an order paid | Change the status back in the back office | | Delete a ticket | Restore it in the back office | 7 of 13 tools ask first: every write, because each reaches a buyer, a guest or your revenue. The reads run at once. Switch the wait off per tool for a scheduled run. > Weezevent keeps its commission on a refunded order and adds 2 EUR excluding VAT per order for re-crediting. MCP call: ``` { "name": "send_invitations", "arguments": { "event_id": "ev_4410", "ticket_type": "Press", "recipients": [ { "last_name": "Novak", "first_name": "Mia", "email": "mia@example.com", "quantity": 2 }, { "last_name": "Reyes", "first_name": "Paul", "email": "paul@example.com", "quantity": 1 } ], "message": "Looking forward to seeing you on the 21st." } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/weezevent/events/ev_4410/invitations \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_type":"Press","recipients":[{"last_name":"Novak","first_name":"Mia","email":"mia@example.com","quantity":2},{"last_name":"Reyes","first_name":"Paul","email":"paul@example.com","quantity":1}],"message":"Looking forward to seeing you on the 21st."}' ``` Tool output: ``` { "ticket_type": "Press", "invited": 3, "emailed": true, "recipients": [ { "name": "Mia Novak", "quantity": 2 }, { "name": "Paul Reyes", "quantity": 1 } ] } ``` Scripts and cron jobs reach the same tools over REST at `/api/v1/weezevent`, with the same key and price. A call the account cannot do in the back office fails, and a failed call costs nothing. REST answers 202 with a call ID while a write waits for your OK. The tools table lists the REST path of each tool. ## How much does the Weezevent MCP server cost? **About $13 a month** for an organizer running about 6 events a month, 2,180 credits. Weezevent's own commission is billed by Weezevent as before. | Job | Calls | Credits | |---|---|---| | Weekly sales and check-in recap | 3 × 4 | 120 | | Partner discount codes | 2 × 4 | 80 | | Invitations for guests and press | 2 × 6 | 120 | | Refunds after a cancelled show | 12 × 1 | 120 | | Reservations marked as paid | 6 × 4 | 240 | | Cloud Browser, 30 days | | 1,500 | | Total | | 2,180 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No Weezevent plan to buy: it works in your organizer account The month is our example: weekly recaps, 4 partner code batches, 6 invitation runs, one cancelled show with 10 refunds and daily reservation checks. Weezevent publishes no typical account size. Dollars at the $29 pack rate. ## Weezevent MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [Zapier](https://zapier.com/apps/weezevent-da56471/integrations) | Official Weezevent app: triggers for a new event and a new transaction, and an action that adds an attendee. | No discount codes, invitations, refunds or order mail. Polling every 15 min on the free plan. | | [Weezevent API](https://api.weezevent.com/) | Your own script on the REST API with a partner key: events, price categories, participants, scan statistics. | Reads only, plus scanner settings. You store the data and stay under 600 requests a minute. | | [glitchr-omnisense/omniticket-weezevent](https://github.com/glitchr-omnisense/omniticket-weezevent) | PHP code for read-only calls to the API: events, rates, participants, a barcode check. 0 stars, last commit 26 Oct 2026. | Not an MCP server and no writes. | | Older API wrappers | Libraries in PHP, Python and Java, last commits 2015 to 2018. | Abandoned, and they wrap the same read-only API. | There is no Weezevent MCP server on GitHub and no hosted one besides ours. Zapier covers new orders and one write. A script on the API covers reads. For codes, invitations and refunds you work by hand in the back office, or Cotlet does it with your OK. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Weezevent tools. ## Weezevent API and MCP: questions ### How do I get access? Create a free account at https://cotlet.dev, open Weezevent under Integrations in the console and log in to Weezevent in its Cloud Browser. The trial starts with your first app, no card asked. ### How do I connect Weezevent to ChatGPT or Claude? Sign up at cotlet.dev, log in to Weezevent 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 Weezevent account through Cotlet, in their phone apps too. ### What can ChatGPT do in Weezevent? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Weezevent: weekly sales and check-in recap; create discount codes for a partner; send invitations to guests and press. You ask in plain words, and anything that reaches other people waits for your OK first. ### Which Weezevent account do I need? Your own organizer account, the login you use in the Weezevent back office. Cotlet does what that account can do there. A call the account cannot do in the back office fails. You do not need a partner API key. ### Does a refund request return the money at once? No. request_refund asks Weezevent to refund the buyer's card for an online order. Weezevent's commission is still owed, plus 2 EUR excluding VAT per refunded order for re-crediting, and the refund usually reaches the buyer 1 to 3 business days after those invoices are paid. Weezevent never refunds without the organizer's consent, which is your confirmation of the call. ### How many invitations can I send? A Weezevent account can generate 1000 invitations for free and at most 500 per event. More invitations need Weezevent's Premium configuration. Cotlet follows the same limits because it uses the same Communicate > Invitations tool. ### Does Weezevent have webhooks? Its API documentation lists none (checked 31 Oct 2026). Zapier polls for new transactions. Run your agent on a schedule instead, for example a daily list_orders pass with date_from set to yesterday. ### Can it add a single attendee by email? Not as such. send_invitations sends a free ticket to a named guest. Zapier's Weezevent app has an Add New Attendee action that takes an event ID, a rate ID and an email. ### Is the MCP server different from the REST API? Only the door is different. Both expose the same 13 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Weezevent? No. Cotlet is independent and not affiliated with Weezevent. ### Can I use the Weezevent 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.