Whova Attendees API (Modeled)

Modeled view of Whova's attendee integration surface. Whova exposes attendee data to organizers only through the Zapier CRM integration - a Get Attendees trigger that fires when the attendee list changes and a Create or Update Attendee action (name, email, title, company, location, ticket type, attendance mode). No public REST endpoints, base URL, or auth scheme are documented by Whova; the operations below are honestly modeled from the Zapier connector, not sourced from an API reference.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/whova-attendees-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: whova:whova-attendees-api
name: Whova Attendees API (Modeled)
tags:
- Attendees
- Networking
- CRM
- Modeled
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://zapier.com/apps/whova/integrations
description: Modeled view of Whova's attendee integration surface. Whova exposes attendee data to organizers
  only through the Zapier CRM integration - a Get Attendees trigger that fires when the attendee list
  changes and a Create or Update Attendee action (name, email, title, company, location, ticket type,
  attendance mode). No public REST endpoints, base URL, or auth scheme are documented by Whova; the operations
  below are honestly modeled from the Zapier connector, not sourced from an API reference.
endpointsModeled:
- GET  /events/{event_id}/attendees            (modeled - list attendees; surfaced via Zapier "Get Attendees"
  trigger)
- POST /events/{event_id}/attendees            (modeled - create attendee; Zapier "Create or Update Attendee"
  action)
- PATCH /events/{event_id}/attendees/{id}       (modeled - update attendee; Zapier upsert action)
properties:
- url: https://zapier.com/apps/whova/integrations
  type: Integrations
- url: https://whova.zendesk.com/hc/en-us/articles/28473285536795-How-do-I-integrate-CRM-via-Zapier
  type: Documentation
- url: https://whova.zendesk.com/hc/en-us/categories/200398767-Event-Attendees
  type: HelpCenter