Weezevent API and MCP server Let your AI agent run your Weezevent back office.

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.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Weezevent
Weezevent logo Weezevent Cloud Browser

13 tools Read and write

Sales to refunds

What can you automate in Weezevent? Use an AI agent, a workflow or a script.

  • 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

Read-only API

Does Weezevent have an MCP server or an API? An API, but it only reads. No MCP server.

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.

  • 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.
The Weezevent API, Zapier and Cotlet compared
What you need Weezevent APIZapierCotlet
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 · Weezevent API fair use · Zapier: Weezevent integrations · Weezevent Help: Refunding participants

Set up once

How does Cotlet connect to Weezevent? One account, two ways to connect.

  1. 1Sign in to Weezevent

    Use your own account in its Cotlet Cloud Browser.

  2. 2Choose MCP or REST

    Connect your agent or create a Cotlet API key.

  3. 3Run 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. Who can see your session

Any MCP client

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. 1

    Enable Weezevent for agents. Sign up, log in to Weezevent in its Cloud Browser, then press Enable for agents.

  2. 2

    Add the Cotlet address. Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent.

  3. 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, <your key>
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: <your key>
Tool: weezevent_write
Scripts and HTTP

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

Weezevent workflows you configure
ToolConnect throughExample workflow
n8nHTTP RequestRead 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.
MakeHTTP > Make a requestRead the discount codes of an event with their rules. Use list_discount_codes to compare codes against your campaign list.
Python or Node.jsREST APIRead a check list after the show. Use get_participation_report to count who passed each access point in your configured report.

Send Authorization: Bearer <your Cotlet API key> 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 lists operations and inputs. The REST API guide explains authentication, errors and approvals.

6 read, 7 write

Weezevent API endpoints and MCP tools

Events, orders and attendees5

Read only. Orders and attendees are per event, so list_events comes first. Deleted tickets show only with the Deleted status.

  • list_events List the events of your account with their dates and sales status. read

    Returns the events your organizer account can open, with the event ID the other tools take. Use it first to get event_id.

    MCP callweezevent_read → list_events

    REST endpointGET https://cotlet.dev/api/v1/weezevent/events

    Parameters

    Parameters: list_events
    NameTypeDescription
    query string string Part of an event name.
    limit integer integer Events per page.
    cursor string string Next page cursor from the previous call.

    Example response

    {
      "events": [
        {
          "event_id": "ev_4410",
          "name": "Autumn concert",
          "start": "2026-11-21T20:00",
          "sales_status": "On sale"
        },
        {
          "event_id": "ev_4388",
          "name": "Saturday show",
          "start": "2026-11-07T19:30",
          "sales_status": "On sale"
        }
      ],
      "next_cursor": null
    }
  • list_orders List the orders of an event, filtered by origin, status, date or refund request. read

    Returns the rows of Attendees > Manage orders with the number of tickets and the amount paid for each order. Tickets sold by distributors appear once they are imported. Reserved means ordered but not yet paid.

    MCP callweezevent_read → list_orders

    REST endpointGET https://cotlet.dev/api/v1/weezevent/events/{event_id}/orders

    Parameters

    Parameters: list_orders
    NameTypeDescription
    event_id string required string Event ID from list_events.
    origin string string Web, Added participants, Box Office, Invitations, Stock Print or Distributor Import.
    status string string Paid, Reserved or Deleted.
    date_from string string First order day, YYYY-MM-DD.
    date_to string string Last order day, YYYY-MM-DD.
    refund_requested boolean boolean true shows only orders with a refund request, false only those without.
    query string string Buyer name, first name, email or order number.
    limit integer integer Orders per page.
    cursor string string Next page cursor from the previous call.

    Example input

    {
      "event_id": "event_8c41d2"
    }

    Example response

    {
      "orders": [
        {
          "order_number": "C26E418207O52913",
          "buyer": "Anna Keller",
          "email": "anna@example.com",
          "origin": "Web",
          "status": "Paid",
          "tickets": 4,
          "amount": 96,
          "currency": "EUR"
        },
        {
          "order_number": "C26E418207O52914",
          "buyer": "Tom Weber",
          "email": "tom@example.com",
          "origin": "Box Office",
          "status": "Reserved",
          "tickets": 2,
          "amount": 48,
          "currency": "EUR"
        }
      ],
      "next_cursor": null
    }
  • get_order Read one order with its tickets, buyer and summary by rate. read

    Returns what the order page shows: order information (number, origin, number of tickets, language), the tickets linked to it, the order summary by rate with the amount paid, and the buyer's first name, last name and email.

    MCP callweezevent_read → get_order

    REST endpointGET https://cotlet.dev/api/v1/weezevent/events/{event_id}/orders/{order_number}

    Parameters

    Parameters: get_order
    NameTypeDescription
    event_id string required string Event ID from list_events.
    order_number string required string Order number from list_orders, starts with C.

    Example input

    {
      "event_id": "event_8c41d2",
      "order_number": "order number"
    }

    Example response

    {
      "order_number": "C26E418207O52913",
      "origin": "Web",
      "status": "Paid",
      "language": "en",
      "buyer": {
        "first_name": "Anna",
        "last_name": "Keller",
        "email": "anna@example.com"
      },
      "summary": [
        {
          "rate": "Standard",
          "tickets": 4,
          "amount": 96
        }
      ],
      "tickets": [
        {
          "ticket_number": "T26E418207-1"
        },
        {
          "ticket_number": "T26E418207-2"
        },
        {
          "ticket_number": "T26E418207-3"
        },
        {
          "ticket_number": "T26E418207-4"
        }
      ],
      "refund_requested": false
    }
  • list_attendees List the attendees of an event with ticket type, source and status. read

    Returns the rows of Attendees > Manage attendees, one per ticket. Never checked-in lists tickets that were not scanned on the day. Deleted tickets are unknown to access control. Filter by promo_code to count how often a discount code was used.

    MCP callweezevent_read → list_attendees

    REST endpointGET https://cotlet.dev/api/v1/weezevent/events/{event_id}/attendees

    Parameters

    Parameters: list_attendees
    NameTypeDescription
    event_id string required string Event ID from list_events.
    source string string Online, Box office, Manual entries, Invitations, Stock printing or Distributors.
    status string string Paid, Unpaid, Never checked-in or Deleted.
    promo_code string string Only tickets that used this discount code.
    date_from string string First order day, YYYY-MM-DD.
    date_to string string Last order day, YYYY-MM-DD.
    query string string Name, first name, email, ticket number or barcode.
    limit integer integer Attendees per page.
    cursor string string Next page cursor from the previous call.

    Example input

    {
      "event_id": "event_8c41d2"
    }

    Example response

    {
      "attendees": [
        {
          "ticket_number": "T26E418207-1",
          "name": "Anna Keller",
          "ticket_type": "Standard",
          "source": "Online",
          "status": "Paid",
          "promo_code": "PARTNER-0007"
        },
        {
          "ticket_number": "T26E418207-2",
          "name": "Jonas Keller",
          "ticket_type": "Standard",
          "source": "Online",
          "status": "Paid",
          "promo_code": "PARTNER-0007"
        }
      ],
      "next_cursor": null
    }
  • get_participation_report Read who passed which access point of a check list. read

    Returns the Participation Report of a check-in list: each participant with the access points they passed. Use it after the event for attendance, or during it to see who is still outside.

    MCP callweezevent_read → get_participation_report

    REST endpointGET https://cotlet.dev/api/v1/weezevent/events/{event_id}/participation-report

    Parameters

    Parameters: get_participation_report
    NameTypeDescription
    event_id string required string Event ID from list_events.
    check_list string required string Check list name as shown under Check lists.

    Example input

    {
      "event_id": "event_8c41d2",
      "check_list": "check list"
    }

    Example response

    {
      "check_list": "Main entrance",
      "participants": [
        {
          "name": "Anna Keller",
          "passes": [
            {
              "access_point": "Gate A",
              "time": "2026-11-21T19:42"
            }
          ]
        },
        {
          "name": "Tom Weber",
          "passes": []
        }
      ]
    }

Discount codes3

Codes apply per ticket, not per order. Automatic creation makes up to 100 codes at once.

  • list_discount_codes List the discount codes of an event with their rules. read

    Returns the codes from Communicate > Discount Codes: the internal name, the code buyers type, the discount, the number of uses allowed, the validity period and whether the code is active. To count how often a code was used, call list_attendees with promo_code.

    MCP callweezevent_read → list_discount_codes

    REST endpointGET https://cotlet.dev/api/v1/weezevent/events/{event_id}/discount-codes

    Parameters

    Parameters: list_discount_codes
    NameTypeDescription
    event_id string required string Event ID from list_events.
    cursor string string Next page cursor from the previous call.

    Example input

    {
      "event_id": "event_8c41d2"
    }

    Example response

    {
      "codes": [
        {
          "name": "Partner 1",
          "code": "PARTNER-0001",
          "discount_type": "percent",
          "value": 10,
          "max_uses": 1,
          "valid_until": "2026-11-15",
          "active": true
        },
        {
          "name": "VIP",
          "code": "VIP2026",
          "discount_type": "amount",
          "value": 15,
          "max_uses": 20,
          "valid_until": null,
          "active": true
        }
      ],
      "next_cursor": null
    }
  • create_discount_codes Create one discount code, or up to 100 with a prefix. writeasks first

    Fills the Add a new code form in Communicate > Discount Codes. Codes apply per ticket, not per order, and not to tickets issued as part of a donation. Each code stops working when its uses are spent. It returns the codes created. A code lowers what buyers pay, so it waits for your OK. Undo it with set_discount_code_active. By default you confirm each call; you can switch that off for this tool.

    MCP callweezevent_write → create_discount_codes

    REST endpointPOST https://cotlet.dev/api/v1/weezevent/events/{event_id}/discount-codes

    Parameters

    Parameters: create_discount_codes
    NameTypeDescription
    event_id string required string Event ID from list_events.
    name string required string Internal name, only you see it.
    mode string required string manual for one code you name, automatic for generated codes.
    code string string The code buyers type. Manual mode only. Codes are case sensitive.
    count integer integer How many codes to generate, up to 100. Automatic mode only.
    prefix string string Prefix of generated codes. Automatic mode only.
    max_uses integer required integer How many times each code can be used.
    discount_type string required string amount for a fixed amount off, percent for a percentage of the ticket price including taxes.
    value number required number The amount or the percentage.
    valid_until string string Last valid day, YYYY-MM-DD. Without it the code has no end date.
    ticket_types array array Ticket types the code works on. Default: all, including ones you add later.

    Example input

    {
      "event_id": "event_8c41d2",
      "name": "Jane Doe",
      "mode": "mode",
      "max_uses": 20,
      "discount_type": "discount type",
      "value": 1
    }

    Example response

    {
      "created": 3,
      "codes": [
        {
          "code": "PARTNER-0001",
          "max_uses": 1,
          "discount_type": "percent",
          "value": 10,
          "valid_until": "2026-11-15"
        },
        {
          "code": "PARTNER-0002",
          "max_uses": 1,
          "discount_type": "percent",
          "value": 10,
          "valid_until": "2026-11-15"
        },
        {
          "code": "PARTNER-0003",
          "max_uses": 1,
          "discount_type": "percent",
          "value": 10,
          "valid_until": "2026-11-15"
        }
      ]
    }
  • set_discount_code_active Activate or deactivate a discount code. writeasks first

    Does what the green symbol next to a code does. A deactivated code stays in the list and keeps its settings, so one call with active true brings it back. Switching a code on gives buyers a discount again. By default you confirm each call; you can switch that off for this tool.

    MCP callweezevent_write → set_discount_code_active

    REST endpointPUT https://cotlet.dev/api/v1/weezevent/events/{event_id}/discount-code-active

    Parameters

    Parameters: set_discount_code_active
    NameTypeDescription
    event_id string required string Event ID from list_events.
    code string required string The code buyers type, as in list_discount_codes.
    active boolean required boolean false stops the code from working, true turns it back on.

    Example input

    {
      "event_id": "event_8c41d2",
      "code": "code",
      "active": true
    }

    Example response

    {
      "code": "VIP2026",
      "active": false
    }

Invitations, refunds and order changes5

Free invitations are capped at 1000 per account and 500 per event. Refund requests cover online orders only.

  • send_invitations Send free tickets to named guests with a custom message. writeasks first

    Uses Communicate > Invitations. You send a ticket, not an invitation to register, and its price is set to 0 even for a paid ticket type. An account can generate 1000 invitations for free, at most 500 per event. With send_email false the invitations appear under Attendees > Manage attendees for you to print. By default you confirm each call; you can switch that off for this tool.

    MCP callweezevent_write → send_invitations

    REST endpointPOST https://cotlet.dev/api/v1/weezevent/events/{event_id}/invitations

    Parameters

    Parameters: send_invitations
    NameTypeDescription
    event_id string required string Event ID from list_events.
    ticket_type string required string Ticket type to send, as named under Configure > Rates and selling.
    recipients array required array Rows with last_name, first_name, email and quantity.
    message string string Custom message in the email.
    send_email boolean boolean false creates the invitations without emailing them. Default true.

    Example input

    {
      "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."
    }

    Example response

    {
      "ticket_type": "Press",
      "invited": 3,
      "emailed": true,
      "recipients": [
        {
          "name": "Mia Novak",
          "quantity": 2
        },
        {
          "name": "Paul Reyes",
          "quantity": 1
        }
      ]
    }
  • request_refund Ask Weezevent to refund the buyer's card for an online order. writeasks first

    Does Actions > Refund Request on the order. It works for online orders only. Weezevent's commission is still owed, plus a re-crediting fee of 2 EUR excluding VAT per refunded order. The buyer usually sees the money in 1 to 3 business days after those invoices are paid. Track it with list_orders and refund_requested true. By default you confirm each call; you can switch that off for this tool.

    MCP callweezevent_write → request_refund

    REST endpointPOST https://cotlet.dev/api/v1/weezevent/events/{event_id}/refund/request

    Parameters

    Parameters: request_refund
    NameTypeDescription
    event_id string required string Event ID from list_events.
    order_number string required string Order number from list_orders, starts with C.
    scope string required string all for every ticket of the order, some for the tickets in ticket_numbers.
    ticket_numbers array array Ticket numbers to refund. Only with scope some.

    Example input

    {
      "event_id": "event_8c41d2",
      "order_number": "order number",
      "scope": "scope"
    }

    Example response

    {
      "order_number": "C26E418207O52913",
      "scope": "all",
      "tickets_refunded": 4,
      "status": "Refund requested"
    }
  • resend_order Email the order and its tickets to the buyer again. writeasks first

    Does Send the order from the Actions menu of the order, which emails the tickets to the address on the order. Use it when a buyer lost the email. It changes nothing in the order. By default you confirm each call; you can switch that off for this tool.

    MCP callweezevent_write → resend_order

    REST endpointPOST https://cotlet.dev/api/v1/weezevent/events/{event_id}/orders/{order_number}/resend

    Parameters

    Parameters: resend_order
    NameTypeDescription
    event_id string required string Event ID from list_events.
    order_number string required string Order number from list_orders, starts with C.

    Example input

    {
      "event_id": "event_8c41d2",
      "order_number": "order number"
    }

    Example response

    {
      "order_number": "C26E418207O52913",
      "sent_to": "anna@example.com"
    }
  • mark_order_paid Turn a reservation into a paid order. writeasks first

    Changes the payment status of an order that is a reservation, as the Actions menu does, after you received the money by another route. It is a manual record, not a bank check. By default you confirm each call; you can switch that off for this tool.

    MCP callweezevent_write → mark_order_paid

    REST endpointPOST https://cotlet.dev/api/v1/weezevent/events/{event_id}/orders/{order_number}/paid/mark

    Parameters

    Parameters: mark_order_paid
    NameTypeDescription
    event_id string required string Event ID from list_events.
    order_number string required string Order number from list_orders, starts with C.

    Example input

    {
      "event_id": "event_8c41d2",
      "order_number": "order number"
    }

    Example response

    {
      "order_number": "C26E418207O52914",
      "status": "Paid"
    }
  • delete_ticket Remove a ticket from the attendees database so it can be sold again. writeasks first

    Moves the ticket to Deleted in Attendees > Manage attendees. Access control no longer knows it. It does not refund the buyer's card: use request_refund for that. You can restore a deleted ticket in the back office. By default you confirm each call; you can switch that off for this tool.

    MCP callweezevent_write → delete_ticket

    REST endpointDELETE https://cotlet.dev/api/v1/weezevent/events/{event_id}/tickets/{ticket_number}

    Parameters

    Parameters: delete_ticket
    NameTypeDescription
    event_id string required string Event ID from list_events.
    ticket_number string required string Ticket number from list_attendees.

    Example input

    {
      "event_id": "event_8c41d2",
      "ticket_number": "ticket number"
    }

    Example response

    {
      "ticket_number": "T26E418207-4",
      "status": "Deleted"
    }
Encrypted, revocable

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). There is no SOC 2 report or third-party pentest yet.

Account risk

Is it against Weezevent's terms? Account safety The organizer terms do not mention automation.

"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

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.

Tested every 12 h

What happens when Weezevent changes? We repair the tool; your prompts stay the same.

between tests of the Weezevent reads
12 h
for a call to a Weezevent tool paused for repair
$0

When Weezevent moves a button or renames a menu, the fix happens on our side and your prompts keep working. status.cotlet.dev watches the site, console and API every 3 minutes.

7 of 13 tools ask first

Approvals, undo and mistakes Buyers and guests hear nothing until you say so.

  1. 01 Reads the order Online orders only; a reservation or box office order stops the refund.
  2. 02 Lists what it will do Every order and ticket count, before anything is sent.
  3. 03 Waits for your OK The request shows up in your Cotlet console first.
  4. 04 Reports the result Orders refunded, tickets covered, anything that failed.
Which Weezevent actions can be undone
ActionUndo
Create discount codesDeactivate them; they stay in the list
Send invitationsNo, the email is out; delete the tickets by hand
Request a refundNo, Weezevent processes it and its fees apply
Resend an orderNo, the email is out
Mark an order paidChange the status back in the back office
Delete a ticketRestore 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.

Pay per call

How much does the Weezevent MCP server cost?

About $13 a monthfor an organizer running about 6 events a month, 2,180 credits. Weezevent's own commission is billed by Weezevent as before.

A month of Weezevent jobs for one organizer, in credits
JobCallsCredits
Weekly sales and check-in recap3 × 4120
Partner discount codes2 × 480
Invitations for guests and press2 × 6120
Refunds after a cancelled show12 × 1120
Reservations marked as paid6 × 4240
Cloud Browser, 30 days1,500
Total2,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.

Cotlet credit packs: price, credits and calls at 10 credits each
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.

Other options

Weezevent MCP server on GitHub, Zapier or hosted: which to use Nobody else offers one yet.

Other Weezevent tools on GitHub and elsewhere, checked 31 Oct 2026
OptionWhat it doesWhere it stops
ZapierOfficial 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 APIYour 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-weezeventPHP 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 wrappersLibraries 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.

EU company, since 2019

Who runs Cotlet A company you can look up.

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 agent access to Weezevent.

Free 7-day trial with 2,000 credits, no card needed.