Banzai · AsyncAPI Specification

Banzai Demio Events

Version

View Spec View on GitHub CompanyMarketingMarketing TechnologyEvent ManagementWebinarsVideoEngagement MarketingDemand GenerationSoftware-as-a-ServiceAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-08-06'
method: searched
source: https://help.demio.com/en/articles/1987449-zapier-triggers
provider: Banzai
providerId: banzai
api: Public Demio API
spec_type: none
asyncapi_published: false
first_party_webhooks: false
description: >-
  Demio has a real event surface — registration, join, no-show and event-update
  notifications — but it does not expose it as a first-party webhook API. The only
  published delivery path is the Demio Zapier app, so an integrator cannot subscribe an
  endpoint of their own without going through Zapier. There is no AsyncAPI document, no
  webhook endpoint registration, no event payload reference, no signature scheme and no
  delivery/retry semantics anywhere on the Demio developer surface. Because these
  events are not addressable by the provider's own contract, no `Webhooks` or
  `AsyncAPI` pointer is wired in apis.yml — recording one would credit Banzai for an
  event surface it does not actually serve.
delivery:
  mechanism: partner-platform
  platform: Zapier
  app_docs: https://help.demio.com/en/articles/3527489-zapier-setup
  customer_visible_endpoint: false
  quota_note: >-
    Zapier traffic consumes the same daily API-call quota as direct API calls (100/day
    on a free trial, 5,000/day for paying customers).
events:
  - name: New Webinar Registration
    trigger: zapier
    fires: When someone registers for a selected Event.
    scope: per-Event (the Event is chosen from a dropdown when the Zap is built)
  - name: Joins Webinar
    trigger: zapier
    fires: When an attendee joins a selected Event.
    scope: per-Event
  - name: Does Not Attend Webinar
    trigger: zapier
    fires: >-
      When a webinar ends and a registrant did not attend. Documented not to fire for
      On-Demand Sessions, where registrants may join at any time and are therefore not
      treated as no-shows.
    scope: per-Event
  - name: Webinar Update
    trigger: zapier
    fires: When a selected Event is updated.
    scope: per-Event
actions:
  - name: Create Registration for Webinar
    platform: zapier
    rest_equivalent: openapi/banzai-demio-openapi.yml#registerForEvent
gaps:
  - No AsyncAPI or event-schema document is published.
  - No customer-registerable webhook endpoints; Zapier is the only subscriber.
  - No payload reference, signature/verification scheme, or retry and ordering guarantees.
  - Triggers are bound to a single Event each — there is no account-wide event stream.
evidence:
  - url: https://help.demio.com/en/articles/1987449-zapier-triggers
    status: 200
  - url: https://help.demio.com/en/articles/1987911-zapier-actions
    status: 200
  - url: https://www.demio.com/openapi.json
    status: 404

Work with this as data

Every AsyncAPI spec 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 asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • 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 AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/banzai-demio-events"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?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.