Humanitix API and MCP server Let your AI agent run your Humanitix events.

ToolWhat it doesAccess

• list_events Your events with date, status and tickets sold. read

  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.

  MCP callhumanitix_read → list_events

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

  Parameters

  Parameters: list_events

  Name	Type	Description
  cursor string	string	Next page cursor from the previous call.

  Example response

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

• get_event One event with its dates, ticket types and sales. read

  Returns the event page settings you see under Manage: dates, location, ticket types with price and capacity, and whether sales are stopped. Ticket type IDs from here feed create_manual_order and create_discount_code.

  MCP callhumanitix_read → get_event

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

  Parameters

  Parameters: get_event

  Name	Type	Description
  event_id string required	string	Event ID from list_events.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "event_id": "6531a0c4e2b7d4001f3c91a2",
    "name": "Harbour Quiz Night",
    "status": "published",
    "sales_stopped": false,
    "starts_at": "2026-11-14T19:00:00+11:00",
    "ticket_types": [
      {
        "ticket_type_id": "tt_general",
        "name": "General admission",
        "price": 25,
        "capacity": 120,
        "sold": 98
      },
      {
        "ticket_type_id": "tt_concession",
        "name": "Concession",
        "price": 15,
        "capacity": 40,
        "sold": 34
      }
    ]
  }

• list_orders Orders of an event, searchable by order ID, name or email. read

  Does what the orders report does: Humanitix searches orders by Order ID, name or email address. Each row has the order status, the total and the number of tickets. Use get_order for the tickets inside an order.

  MCP callhumanitix_read → list_orders

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

  Parameters

  Parameters: list_orders

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  query string	string	Order ID, buyer name or email address.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "orders": [
      {
        "order_id": "K4TR9WNB",
        "buyer": "Maria Jensen",
        "email": "maria.jensen@example.com",
        "status": "complete",
        "total": 65,
        "currency": "AUD",
        "tickets": 2
      },
      {
        "order_id": "Q8LM2XZD",
        "buyer": "Tom Berg",
        "email": "tom.berg@example.com",
        "status": "complete",
        "total": 25,
        "currency": "AUD",
        "tickets": 1
      }
    ],
    "next_cursor": null
  }

• get_order One order with its tickets and payment details. read

  Returns the buyer, the tickets of the order with ticket type, price and status, and the payment total. Cancelled tickets stay on the order, because Humanitix never deletes an order; they drop out of the attendees report only.

  MCP callhumanitix_read → get_order

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

  Parameters

  Parameters: get_order

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  order_id string required	string	Order ID from list_orders, the short code buyers see, for example K4TR9WNB.

  Example input

  {
    "event_id": "event_8c41d2",
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "K4TR9WNB",
    "buyer": "Maria Jensen",
    "email": "maria.jensen@example.com",
    "status": "complete",
    "currency": "AUD",
    "tickets": [
      {
        "ticket_id": "tk_70211",
        "ticket_type": "General admission",
        "price": 25,
        "status": "valid"
      },
      {
        "ticket_id": "tk_70212",
        "ticket_type": "General admission",
        "price": 25,
        "status": "valid"
      },
      {
        "ticket_id": "tk_70213",
        "ticket_type": "Concession",
        "price": 15,
        "status": "valid"
      }
    ],
    "total": 65
  }

• list_attendees Ticket holders of an event, filtered by ticket type or cancelled tickets. read

  Does what manage attendees > attendees does: one row per ticket holder with ticket type and check-in state. The filters match the ones in the app: ticket type, event date and cancelled tickets. Answers to per-ticket checkout questions appear here, not in the orders report.

  MCP callhumanitix_read → list_attendees

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

  Parameters

  Parameters: list_attendees

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  ticket_type string	string	Only tickets of this ticket type name.
  cancelled boolean	boolean	Only cancelled tickets when true. Default false.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "attendees": [
      {
        "ticket_id": "tk_70211",
        "name": "Maria Jensen",
        "ticket_type": "General admission",
        "checked_in": false
      },
      {
        "ticket_id": "tk_70213",
        "name": "Lena Koch",
        "ticket_type": "Concession",
        "checked_in": false
      }
    ],
    "next_cursor": null
  }

ToolWhat it doesAccess

• refund_tickets Cancel tickets of an order, refund them, or both. writeasks first

  Does what actions > cancel/refund does on an order. By default it cancels the chosen tickets (all if ticket_ids is empty) and refunds their net ticket sale to the card used, which takes 2 to 5 business days. amount overrides the refund: 0 cancels without refunding, a smaller figure is a partial refund. cancel false refunds without cancelling. Cancelled tickets are restocked. Humanitix refunds only if funds are available and never to another card. A swapped ticket cannot be refunded; refund the original order. By default you confirm each call; you can switch that off for this tool.

  MCP callhumanitix_write → refund_tickets

  REST endpointPOST https://cotlet.dev/api/v1/humanitix/events/{event_id}/tickets/refund

  Parameters

  Parameters: refund_tickets

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  order_id string required	string	Order ID from list_orders, the short code buyers see, for example K4TR9WNB.
  ticket_ids array	array	Ticket IDs from get_order. Omit to cancel every ticket of the order.
  amount number	number	Refund amount in the order currency. Default is the net ticket sale of the chosen tickets; 0 cancels without a refund.
  cancel boolean	boolean	Cancel the tickets as well. Default true; false refunds only.

  Example input

  {
    "event_id": "6531a0c4e2b7d4001f3c91a2",
    "order_id": "K4TR9WNB",
    "ticket_ids": [
      "tk_70211",
      "tk_70212"
    ]
  }

  Example response

  {
    "order_id": "K4TR9WNB",
    "cancelled_tickets": [
      "tk_70211",
      "tk_70212"
    ],
    "refunded": 50,
    "currency": "AUD",
    "status": "refund_requested"
  }

• resend_order Email the order confirmation and digital tickets to the buyer again. writeasks first

  Does what actions > resend order does: Humanitix emails the confirmation with the view tickets button to the address on the order. For a mistyped address the order must be corrected first; this tool does not edit the address. Humanitix keeps no log of when an order was resent. By default you confirm each call; you can switch that off for this tool.

  MCP callhumanitix_write → resend_order

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

  Parameters

  Parameters: resend_order

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  order_id string required	string	Order ID from list_orders, the short code buyers see, for example K4TR9WNB.

  Example input

  {
    "event_id": "event_8c41d2",
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "K4TR9WNB",
    "sent_to": "maria.jensen@example.com",
    "status": "sent"
  }

• stop_sales Stop all ticket sales of an event. writeasks first

  Does what "..." > stop sales does. Use it first when an event cannot go ahead, then email buyers, then refund. It stops new orders only; existing tickets stay valid until you cancel them. By default you confirm each call; you can switch that off for this tool.

  MCP callhumanitix_write → stop_sales

  REST endpointPOST https://cotlet.dev/api/v1/humanitix/events/{event_id}/sales/stop

  Parameters

  Parameters: stop_sales

  Name	Type	Description
  event_id string required	string	Event ID from list_events.

  Example input

  {
    "event_id": "event_8c41d2"
  }

  Example response

  {
    "event_id": "6531a0c4e2b7d4001f3c91a2",
    "sales_stopped": true
  }

ToolWhat it doesAccess

• create_manual_order Issue complimentary tickets to a guest through a manual order. writeasks first

  Does what + new manual order with the complimentary payment type does: tickets worth 0 for VIPs, sponsors and guest lists. They count toward capacity and can push sales above it, so check availability with get_event first. skip_emails stops the confirmation email; otherwise the guest gets their digital ticket at once. By default you confirm each call; you can switch that off for this tool.

  MCP callhumanitix_write → create_manual_order

  REST endpointPOST https://cotlet.dev/api/v1/humanitix/events/{event_id}/manual-orders

  Parameters

  Parameters: create_manual_order

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  ticket_type string required	string	Ticket type name from get_event.
  quantity integer required	integer	Number of tickets.
  first_name string required	string	Buyer first name.
  last_name string required	string	Buyer last name.
  email string required	string	Buyer email address.
  skip_emails boolean	boolean	Do not send the order confirmation. Default false.
  note string	string	Internal note on the order.

  Example input

  {
    "event_id": "event_8c41d2",
    "ticket_type": "ticket type",
    "quantity": 1,
    "first_name": "first name",
    "last_name": "last name",
    "email": "jane@example.com"
  }

  Example response

  {
    "order_id": "W3HD7PCA",
    "payment_type": "complimentary",
    "tickets": 2,
    "total": 0,
    "confirmation_sent": true
  }

• create_discount_code Create a percentage or fixed-amount discount code for an event. writeasks first

  Does what promote > discounts > create discount code does. The name is the code buyers type at checkout. The discount applies per ticket, not to a packaged ticket. quantity caps uses across all orders and max_per_order caps discounted tickets in one order. valid_from and valid_to set the timeframe. A code gives buyers a lower price, so each call needs your OK by default; delete or edit it in the app to undo. By default you confirm each call; you can switch that off for this tool.

  MCP callhumanitix_write → create_discount_code

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

  Parameters

  Parameters: create_discount_code

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  code string required	string	The code buyers enter.
  type string required	string	percentage or fixed_amount.
  value number required	number	Percent off, or amount off in the event currency.
  ticket_types array	array	Ticket type names. Omit for all ticket types.
  quantity integer	integer	How many times the code can be used in total.
  max_per_order integer	integer	Most tickets one order can discount.
  valid_from datetime	datetime	Start of the timeframe.
  valid_to datetime	datetime	End of the timeframe.

  Example input

  {
    "event_id": "event_8c41d2",
    "code": "code",
    "type": "type",
    "value": 1
  }

  Example response

  {
    "event_id": "6531a0c4e2b7d4001f3c91a2",
    "code": "CHOIR20",
    "type": "percentage",
    "value": 20,
    "ticket_types": [
      "General admission"
    ],
    "quantity": 30,
    "status": "active"
  }

ToolWhat it doesAccess

• send_email_campaign Email the buyers or attendees of an event now or on a schedule. writeasks first

  Does what email campaigns > new campaign does. recipients is buyers or all (buyers and attendees); attendees only get it if you collected an email per ticket. send_at is now, a date and time, or a number of hours before or after the event; before-event sends repeat for each date of a recurring event. Shortcuts such as @FirstName and @EventName fill in per buyer. Send it before you refund a cancelled event: once tickets are refunded, campaigns can no longer reach those ticket holders. By default you confirm each call; you can switch that off for this tool.

  MCP callhumanitix_write → send_email_campaign

  REST endpointPOST https://cotlet.dev/api/v1/humanitix/email-campaigns

  Parameters

  Parameters: send_email_campaign

  Name	Type	Description
  event_ids array required	array	Event IDs from list_events.
  name string required	string	Internal campaign name.
  subject string required	string	Subject line.
  message string required	string	Message body. Supports @FirstName, @EventName, @EventShortDate, @EventLocation.
  recipients string	string	buyers or all. Default buyers.
  send_at string	string	now, an ISO date and time, or "2 days before" / "1 day after" the event. Default now.

  Example input

  {
    "event_ids": "event ids",
    "name": "Jane Doe",
    "subject": "subject",
    "message": "message"
  }

  Example response

  {
    "campaign": "Quiz night reminder",
    "events": [
      "6531a0c4e2b7d4001f3c91a2"
    ],
    "recipients": "buyers",
    "scheduled_for": "2 days before the event",
    "status": "scheduled"
  }

• duplicate_event Copy an event into a new draft. write

  Does what the "..." menu > duplicate event does. It creates a draft with the event information, dates, ticket types, checkout questions, styling and settings; sales, attendees, access codes, discount codes, sales start and end dates and past dates of a recurring event are not copied. The draft reaches no one and nothing is published, so it needs no approval. Delete the draft in Humanitix to undo it.

  MCP callhumanitix_write → duplicate_event

  REST endpointPOST https://cotlet.dev/api/v1/humanitix/events/{event_id}/duplicate

  Parameters

  Parameters: duplicate_event

  Name	Type	Description
  event_id string required	string	Event ID from list_events.
  name string required	string	Name of the new draft; make it unique, for example "Harbour Quiz Night 2027".

  Example input

  {
    "event_id": "event_8c41d2",
    "name": "Jane Doe"
  }

  Example response

  {
    "source_event_id": "6531a0c4e2b7d4001f3c91a2",
    "event_id": "6531b7f2e2b7d4001f3c9244",
    "name": "Harbour Quiz Night 2027",
    "status": "draft"
  }