Whova website screenshot

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 Event, Event Management, Event App, Registration, and Conferences.

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

11.4/100 emerging ▬ flat Agent 0/100 human only Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-04 · rubric v0.23.0
AccessFreemium
2 APIs
EventEvent ManagementEvent AppRegistrationConferencesAttendeesExhibitorsGated APIModeled

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-04 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. 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. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
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:
- Event
- Event Management
- Event App
- Registration
- Conferences
- Attendees
- Exhibitors
- Gated API
- Modeled
tags_raw:
- Events
- Event Management
- Event App
- Registration
- Conferences
- Attendees
- Exhibitors
- Gated API
- Modeled
created: '2026-07-05'
modified: '2026-07-25'
specificationVersion: '0.23'
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
  - Order
  - Ticketing
  - Modeled
  tags_raw:
  - 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

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/whova"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/whova/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/whova/evidence"

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

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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