Weezevent API · unofficial, by Cotlet
Create your own Weezevent API
Weezevent: no self-serve API key; its docs limit access to registered partners and ask you to contact Weezevent for a key (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Weezevent account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Weezevent session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Weezevent. Weezevent is a trademark of its owner. If Weezevent's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-ticket-type" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"event": "Saturday concert"}' const url = "https://cotlet.dev/api/v1/custom/sales-by-ticket-type";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ event: "Saturday concert" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/sales-by-ticket-type",
headers={"Authorization": f"Bearer {key}"},
json={"event": "Saturday concert"},
)
data = res.json()["data"] {
"data": [
{
"ticket_type": "Standing",
"sold": 980,
"capacity": 1200
},
{
"ticket_type": "Student",
"sold": 260,
"capacity": 300
}
]
} 01 Build
How do you build a Weezevent endpoint with Cotlet?
-
Sign in to Weezevent in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "Count the tickets sold for this event, per ticket type, with the capacity left."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as an event or a ticket type, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Weezevent session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Weezevent
Cotlet ships no fixed list of Weezevent endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/sales-by-ticket-type Sales by ticket type
Tickets sold and capacity left for each ticket type of an event
-
POST
/api/v1/custom/checkins-so-far Check-ins so far
Attendees checked in, by ticket type, for a date
-
POST
/api/v1/custom/attendee-list Attendee list
Name, email, ticket type and order of each attendee
-
POST
/api/v1/custom/find-order Find an order
An order and its tickets, by name or email
-
POST
/api/v1/custom/writesadd-invitation Add a free invitation
A guest added to an event on an invitation ticket
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-ticket-type" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"event": "Saturday concert"}' The answer is JSON, with your fields under data:
{
"data": [
{
"ticket_type": "Standing",
"sold": 980,
"capacity": 1200
},
{
"ticket_type": "Student",
"sold": 260,
"capacity": 300
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Weezevent endpoints for?
- Schedule Cotlet endpoint Slack
A daily sales count.
Tickets sold per ticket type, posted to your team chat every morning.
- Every 10 min endpoint Team chat
Live check-in numbers.
Attendees checked in so far, read every 10 minutes during the event.
- Event end endpoint Google Sheets
A sponsor or partner report.
Attendees by ticket type pulled into Google Sheets after the event.
- Your form endpoint invitation
Your guest list form.
Guests from your own form added to the event with a free invitation, after your OK.
04 Access
What can an endpoint see and change?
An endpoint works in your own Weezevent session, so it can read and change only what your Weezevent login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as adding a free invitation, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Weezevent have an official API?
Weezevent: the API docs say "Access to the API is limited to registered partners of Weezevent"; API v3 keys come from Weezevent on request, and the newer APIs use a client ID and secret from Weezevent Support (checked 20 Nov 2026). Organizers can export attendee and order lists as Excel files. The full picture with sources: Does Weezevent have an API or MCP server?
Want ChatGPT or Claude to work in Weezevent instead of code? See the Weezevent MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Weezevent API with Cotlet: questions
Is this an official Weezevent API?
No. Cotlet is independent and not affiliated with Weezevent. The endpoints you build run in your own signed-in Weezevent account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Weezevent changes its screens?
An endpoint works while Weezevent works the way it did when you built it. If Weezevent changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Weezevent endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.