Connectly · AsyncAPI Specification

Connectly Webhooks

Version

View Spec View on GitHub Artificial IntelligencePlatformCustomer EngagementEnterpriseAutomationAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-10-10'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.connectly.ai/webhooks/overview.md
sources:
- https://docs.connectly.ai/webhooks/overview.md
- https://docs.connectly.ai/webhooks/payload-types.md
- https://docs.connectly.ai/webhooks/webhook-keys.md
- https://docs.connectly.ai/webhooks/create-webhook.md
description: Connectly webhooks deliver real‑time WhatsApp events.
events:
- event: messages
  description: Inbound WhatsApp messages sent to your business number by customers.
- event: delivery_status
  description: 'Delivery status updates for messages you sent: sent, delivered, read, or delivery_failed.'
delivery:
  retries: Connectly treats any non‑200 response as a failure and may retry the request.
note: Your endpoint must return HTTP 200 for every event to acknowledge successful delivery; otherwise Connectly will retry.
docs: https://docs.connectly.ai/webhooks/overview.md

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