Whova API and MCP server

• POST

  list_events

  Events you can manage as an organizer, with dates and status.

  read

  Returns every event of your organizer account, newest first. Use event_id from each item in the other tools. Dates are in the time zone of the event.

  POST /api/v1/whova/list_events

  Input

  Input: list_events

  Parameter	Type	Description
  status	enum	upcoming, past or all. Default: upcoming.

  Example response

  {
    "events": [
      {
        "event_id": "284611",
        "name": "Northwind Summit 2026",
        "start": "2026-10-21",
        "end": "2026-10-23",
        "status": "upcoming"
      },
      {
        "event_id": "271905",
        "name": "Northwind Summit 2025",
        "start": "2025-10-14",
        "end": "2025-10-16",
        "status": "past"
      }
    ]
  }

• POST

  list_attendees

  Attendees of an event with email, company, ticket type, audience type and check-in status.

  read

  Lists attendees of one event. Filter by ticket type or audience type, or by check-in status to see who has not arrived. Pages hold up to 500 attendees; pass next_cursor back as cursor for the next page.

  POST /api/v1/whova/list_attendees

  Input

  Input: list_attendees

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  ticket_type	string	Only holders of this ticket type, as named in your event.
  audience_type	string	Only attendees with this audience type, as named in your event.
  checked_in	boolean	true for checked-in attendees, false for those not checked in.
  limit	integer	1 to 500. Default: 100.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "attendees": [
      {
        "attendee_id": "at_5521",
        "first_name": "Maya",
        "last_name": "Ortiz",
        "email": "maya@example.com",
        "company": "Northwind Labs",
        "ticket_type": "Full Pass",
        "audience_type": "Attendee",
        "checked_in": false
      }
    ],
    "next_cursor": null
  }

• POST

  list_registrations

  Registration orders with registrant, ticket type and order date, newest first.

  read

  Lists registration orders of one event, newest first. Filter by date or ticket type to get only what is new since your last check. Pages hold up to 500 orders; pass next_cursor back as cursor.

  POST /api/v1/whova/list_registrations

  Input

  Input: list_registrations

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  since	date	Only orders placed on or after this date.
  ticket_type	string	Only orders with this ticket type.
  limit	integer	1 to 500. Default: 100.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "orders": [
      {
        "order_id": "ord_80231",
        "registrant": "Maya Ortiz",
        "email": "maya@example.com",
        "ticket_type": "Full Pass",
        "ordered_at": "2026-10-10T14:12:00Z"
      },
      {
        "order_id": "ord_80229",
        "registrant": "Leo Brandt",
        "email": "leo@example.com",
        "ticket_type": "Student",
        "ordered_at": "2026-10-10T09:40:00Z"
      }
    ],
    "next_cursor": null
  }

• POST

  list_sessions

  Agenda sessions with time, tracks, speakers and description, in agenda order.

  read

  Lists the sessions of one event in agenda order. Filter by day or track. Use session_id with update_session. Times carry the time zone of the event.

  POST /api/v1/whova/list_sessions

  Input

  Input: list_sessions

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  date	date	Only sessions on this day.
  track	string	Only sessions in this track.

  Example response

  {
    "sessions": [
      {
        "session_id": "s_30871",
        "title": "Breakout: Pricing workshop",
        "start": "2026-10-22T14:00:00-07:00",
        "end": "2026-10-22T15:00:00-07:00",
        "tracks": [
          "Workshops"
        ],
        "speakers": [
          "Jon Pike"
        ]
      }
    ]
  }

• POST

  list_speakers

  Speakers of an event from the Speaker Center, with their sessions.

  read

  Lists the speakers of one event with the sessions each one speaks in. Speakers added to a session appear here automatically. Use it to build the recipient list for message_speakers.

  POST /api/v1/whova/list_speakers

  Input

  Input: list_speakers

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  session_id	string	Only speakers of this session.

  Example response

  {
    "speakers": [
      {
        "speaker_id": "sp_204",
        "name": "Dana Reyes",
        "email": "dana@example.com",
        "sessions": [
          "Opening keynote"
        ]
      }
    ]
  }

• POST

  get_post_event_report

  The post-event report of an event as text sections, available after the event ends.

  read

  Returns the post-event report of one finished event as titled sections with their figures. Pass section to read one part, for example Sponsors and exhibitors. Whova releases the report only after the organizer requests it under Tools > Report; until then the call fails with a not-ready error.

  POST /api/v1/whova/get_post_event_report

  Input

  Input: get_post_event_report

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  section	string	Section title as shown in the report. Default: all sections.

  Example response

  {
    "event_id": "271905",
    "sections": [
      {
        "title": "Sponsors and exhibitors",
        "text": "Total sponsor impressions, exhibitor leads and attendee profile views, then impressions per sponsor."
      }
    ]
  }

• POST

  add_session

  Add a session to the agenda in Session Manager.

  write

  Creates one session in the agenda of one event. Speakers you name also appear in the Speaker Center. The session shows in the event app agenda at once. It reaches no one directly and one update_session or a delete in Whova undoes it, so it runs without asking.

  POST /api/v1/whova/add_session

  Input

  Input: add_session

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  title required	string	Session title.
  start required	datetime	Start, ISO 8601 with time zone.
  end required	datetime	End, ISO 8601 with time zone.
  tracks	string[]	Tracks the session belongs to, as named in your event.
  speakers	string[]	Speaker names.
  description	string	Session description.

  Example response

  {
    "session_id": "s_30902",
    "event_id": "284611",
    "title": "Opening keynote",
    "start": "2026-10-21T09:00:00-07:00",
    "end": "2026-10-21T09:45:00-07:00",
    "tracks": [
      "Main stage"
    ],
    "speakers": [
      "Dana Reyes"
    ],
    "status": "created"
  }

• POST

  update_session

  Change the time, tracks, speakers or description of an existing session.

  write

  Changes the fields you send and leaves the others as they are. Moving a block of sessions means one call per session. It reaches no one directly and one more call restores the old values, so it runs without asking.

  POST /api/v1/whova/update_session

  Input

  Input: update_session

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  session_id required	string	Session ID from list_sessions.
  title	string	New title.
  start	datetime	New start, ISO 8601 with time zone.
  end	datetime	New end, ISO 8601 with time zone.
  tracks	string[]	Replaces the tracks.
  speakers	string[]	Replaces the speakers.
  description	string	New description.

  Example response

  {
    "session_id": "s_30871",
    "event_id": "284611",
    "title": "Breakout: Pricing workshop",
    "start": "2026-10-22T15:00:00-07:00",
    "end": "2026-10-22T16:00:00-07:00",
    "status": "updated"
  }

• POST

  add_attendee

  Create or update one attendee by name and email.

  asks first write

  Creates the attendee, or updates the one with the same email. The attendee appears in the event's attendee list. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/whova/add_attendee

  Input

  Input: add_attendee

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  first_name required	string	First name.
  last_name required	string	Last name.
  email required	string	Attendee email.
  company	string	Company or organization.
  title	string	Job title.
  ticket_type	string	Ticket type, as named in your event.
  audience_type	string	Audience type, as named in your event.

  Example response

  {
    "attendee_id": "at_5530",
    "event_id": "284611",
    "email": "sam@example.com",
    "status": "created"
  }

• POST

  send_announcement

  Post an announcement for the attendees of an event.

  asks first write

  Posts an announcement to the attendees of one event. App users get it as a push notification, and Whova also connects announcements to attendees' email, so people without the app are notified. It reaches every attendee at once. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/whova/send_announcement

  Input

  Input: send_announcement

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  message required	string	Announcement text.

  Example response

  {
    "announcement_id": "ann_90314",
    "event_id": "284611",
    "status": "sent"
  }

• POST

  message_speakers

  Email all speakers of an event, or the ones you list, through Whova.

  asks first write

  Sends an email to speakers through Whova's speaker messaging. Leave speaker_ids out to email all speakers of the event. Speakers receive it from Whova, not from your own address. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/whova/message_speakers

  Input

  Input: message_speakers

  Parameter	Type	Description
  event_id required	string	Event ID from list_events.
  subject required	string	Email subject.
  body required	string	Email body.
  speaker_ids	string[]	Speaker IDs from list_speakers. Default: all speakers.

  Example response

  {
    "message_id": "msg_4107",
    "event_id": "284611",
    "recipients": 18,
    "status": "sent"
  }

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.