Whova

Whova is an award-winning all-in-one event management platform built around a mobile event app that carries the agenda, speaker profiles, attendee networking, live polls, and session Q&A, plus registration, ticketing, name badges, surveys, abstract/speaker management, and exhibitor/sponsor tools. Whova does NOT publish an open, self-serve developer API - there is no public developer portal, no documented REST reference, no OpenAPI definition, and no SDKs. Its only programmatic surface for organizers is a partner/CRM integration layer exposed through Zapier (triggers for attendee, order, and registrant changes plus a create/update-attendee action), reached from the organizer dashboard under Attendees > Integrations > CRM Integration, alongside prebuilt connectors to Eventbrite, Cvent, Constant Contact, RegFox, OpenReview, SharePoint/OneDrive, MailChimp, Wild Apricot, and Google Drive. The API entries below are logical, HONESTLY MODELED views of that integration surface (see endpointsModeled) - they are not sourced from a public Whova API reference, and no base URL, auth scheme, or endpoint paths are published by Whova.

Whova publishes 2 APIs on the APIs.io network. Tagged areas include Events, Event Management, Event App, Registration, and Conferences.

Whova’s developer surface includes documentation, engineering blog, and 6 more developer resources.

12.3/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
AccessFreemium
2 APIs
EventsEvent ManagementEvent AppRegistrationConferencesAttendeesExhibitorsGated APIModeled

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 12.3/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 2.2 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 5.9 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/whova: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

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...

Whova Registration and Orders API (Modeled)

Modeled view of Whova's registration and order surface. The Zapier integration provides a Get Orders trigger (fires on order-list changes) and a Get Registrants trigger (fires w...

Pricing Plans 1

Published pricing tiers and plan structures.

Whova Plans Pricing

2 plans

PLANS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Whova Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Access & Security 1

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: whova
url: https://raw.githubusercontent.com/api-evangelist/whova/refs/heads/main/apis.yml
name: Whova
kind: company
description: Whova is an award-winning all-in-one event management platform built around a mobile event app that carries the
  agenda, speaker profiles, attendee networking, live polls, and session Q&A, plus registration, ticketing, name badges, surveys,
  abstract/speaker management, and exhibitor/sponsor tools. Whova does NOT publish an open, self-serve developer API - there
  is no public developer portal, no documented REST reference, no OpenAPI definition, and no SDKs. Its only programmatic surface
  for organizers is a partner/CRM integration layer exposed through Zapier (triggers for attendee, order, and registrant changes
  plus a create/update-attendee action), reached from the organizer dashboard under Attendees > Integrations > CRM Integration,
  alongside prebuilt connectors to Eventbrite, Cvent, Constant Contact, RegFox, OpenReview, SharePoint/OneDrive, MailChimp,
  Wild Apricot, and Google Drive. The API entries below are logical, HONESTLY MODELED views of that integration surface (see
  endpointsModeled) - they are not sourced from a public Whova API reference, and no base URL, auth scheme, or endpoint paths
  are published by Whova.
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/whova.png
tags:
- Events
- Event Management
- Event App
- Registration
- Conferences
- Attendees
- Exhibitors
- Gated API
- Modeled
created: '2026-07-05'
modified: '2026-07-25'
specificationVersion: '0.19'
apis:
- 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
- aid: whova:whova-registration-api
  name: Whova Registration and Orders API (Modeled)
  tags:
  - Registration
  - Orders
  - Ticketing
  - 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 registration and order surface. The Zapier integration provides a Get Orders trigger
    (fires on order-list changes) and a Get Registrants trigger (fires when a registrant submits their registration question
    form responses). Whova publishes no REST endpoints for registration; these operations are honestly modeled from the Zapier
    connector and prebuilt ticketing integrations (Eventbrite, Cvent, RegFox).
  endpointsModeled:
  - GET /events/{event_id}/orders                (modeled - list orders; Zapier "Get Orders" trigger)
  - GET /events/{event_id}/registrants           (modeled - list registrant form responses; Zapier "Get Registrants" trigger)
  properties:
  - url: https://zapier.com/apps/whova/integrations
    type: Integrations
  - url: https://whova.com/blog/whova-integration-eventbrite-cvent-constant-contact-regfox-zapier/
    type: Documentation
  - url: https://whova.com/blog/registration-integrates-with-platform/
    type: Documentation
common:
- type: DomainSecurity
  url: security/whova-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/whova
- type: Website
  url: https://whova.com/
- type: Documentation
  url: https://whova.zendesk.com/hc/en-us
- type: Integrations
  url: https://zapier.com/apps/whova/integrations
- type: Plans
  url: plans/whova-plans-pricing.yml
- url: https://whova.com/blog/
  type: Blog
- type: ProductPage
  url: https://whova.com/blog/openreview-integration/
- type: ProductPage
  url: https://whova.com/pages/whova-app-exhibitor-guide/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com