Whova API · unofficial, by Cotlet

Create your own Whova API

Whova: no public API or developer docs found on whova.com (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Whova 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 Whova session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Whova. Whova is a trademark of its owner. If Whova's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/checkins-by-ticket" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_day": "2026-11-20"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/checkins-by-ticket";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ event_day: "2026-11-20" }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/checkins-by-ticket",
    headers={"Authorization": f"Bearer {key}"},
    json={"event_day": "2026-11-20"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "ticket_type": "General",
      "registered": 320,
      "checked_in": 214
    },
    {
      "ticket_type": "VIP",
      "registered": 92,
      "checked_in": 54
    }
  ]
}

01 Build

How do you build a Whova endpoint with Cotlet?

  1. Sign in to Whova in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "How many attendees have checked in today, by ticket type?"

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as an event day or a ticket type, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in Whova session.

02 Endpoints

Example endpoints you could build for Whova

Cotlet ships no fixed list of Whova endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/checkins-by-ticket

    Check-ins by ticket type

    Registered and checked-in counts for each ticket type

  • POST /api/v1/custom/sessions-for-day

    Sessions for a day

    Time, room and speakers of each session

  • POST /api/v1/custom/attendee-list

    Attendee list

    Name, company and job title of each attendee

  • POST /api/v1/custom/session-attendance

    Session attendance

    Attendees per session for a day

  • POST /api/v1/custom/add-attendee writes

    Add an attendee

    A new attendee with name, email and ticket type

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/checkins-by-ticket" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_day": "2026-11-20"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "ticket_type": "General",
      "registered": 320,
      "checked_in": 214
    },
    {
      "ticket_type": "VIP",
      "registered": 92,
      "checked_in": 54
    }
  ]
}

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 Whova endpoints for?

  • Every hour Cotlet endpoint Slack

    Live numbers in your team chat.

    Check-ins by ticket type, posted to Slack every hour of the event.

  • Day end endpoint Google Sheets

    A sponsor report.

    Attendees and session attendance pulled into Google Sheets after each day.

  • Every 10 min endpoint Lobby screen

    A screen at the venue.

    The next sessions and rooms, read from Whova for a lobby display.

  • Chat agent endpoint agenda

    Your own event assistant.

    A chat agent that reads the agenda before it answers attendee questions.

04 Access

What can an endpoint see and change?

An endpoint works in your own Whova session, so it can read and change only what your Whova 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 an attendee, 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 Whova have an official API?

Whova: no public API or developer docs found on whova.com (checked 20 Nov 2026). Whova's Zapier app syncs attendees, registrants and orders. The full picture with sources: Does Whova have an API or MCP server?

Want ChatGPT or Claude to work in Whova instead of code? See the Whova 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.

Whova API with Cotlet: questions

Is this an official Whova API?

No. Cotlet is independent and not affiliated with Whova. The endpoints you build run in your own signed-in Whova 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 Whova changes its screens?

An endpoint works while Whova works the way it did when you built it. If Whova 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 Whova endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.