wbiztool-com · AsyncAPI Specification

Wbiztool Com Webhooks

Version

View Spec View on GitHub CompanyWhatsAppMessagingAutomationBusinessAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-10-31'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://wbiztool.com/docs/guides/webhook-listeners/
sources:
- https://wbiztool.com/docs/guides/webhook-listeners/
- https://wbiztool.com/docs/api/v2/webhooks/
- https://wbiztool.com/docs/api/v2/
- https://wbiztool.com/docs/guides/webhook-listeners/
description: WbizTool provides two webhook systems. The older Inbox‑number webhooks post a signed JSON payload for each message and support the
  event types message_received (for incoming messages) and message_sent (for outgoing messages). The newer API v2 webhook endpoints deliver events
  of type message.sent, message.failed, message.cancelled, message.expired and a test ping event.
events:
- event: message_received
  description: Posted for each new incoming WhatsApp message received by an inbox number.
- event: message_sent
  description: Posted for each outgoing WhatsApp message sent from an inbox number (including messages sent via the phone, WhatsApp Web, campaigns,
    API or reminders).
- event: message.sent
  description: A message went out from your number.
- event: message.failed
  description: A message couldn't be sent; the payload includes an error.message explaining why.
- event: message.cancelled
  description: A waiting message was cancelled (via API, dashboard, or because its number or campaign was removed).
- event: message.expired
  description: A message wasn't sent before its expires_at timestamp.
- event: ping
  description: A test event you can request to verify the endpoint.
delivery:
  signature: Each request is signed with a secret (32‑character alphanumeric string for inbox webhooks, 64‑hexadecimal characters for API v2).
    The signature is included in the request headers (the documentation refers to “signed JSON” and a “webhook secret” that you verify on receipt).
  retries: If a delivery fails due to a timeout, connection error, HTTP 429 or any 5xx response, WbizTool retries up to three times with back‑off
    intervals of 30 seconds, 1 minute, and 2 minutes. Other responses (e.g., 400, 404, invalid TLS) are not retried. A 410 Gone response disables
    the webhook (URL and secret are removed).
docs: https://wbiztool.com/docs/guides/webhook-listeners/

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/wbiztool-com-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.