Buska · AsyncAPI Specification

Buska Io Webhooks

Version

View Spec View on GitHub Social ListeningLead GenerationArtificial IntelligenceB2BMarketingAsyncAPIEvents

AsyncAPI Specification

buska-io-webhooks.yml Raw ↑
generated: '2026-11-03'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://www.buska.io/integrations/webhook
sources:
- https://www.buska.io/integrations/webhook
- https://www.buska.io/docs/integrations/slack
- https://www.buska.io/docs/integrations/discord
- https://www.buska.io/docs/integrations/microsoft-teams
description: Buska sends a JSON payload via HTTP POST right after each scan finds a new buying signal.
events:
- event: new_lead
  description: An HTTP POST is sent with an `event` field set to "new_lead", a timestamp, and a `lead` object containing details such as name,
    channel, intent, score, AI reasoning, ICP match, content, post URL, and timestamps.
delivery:
  auth: No request signing; the webhook URL itself acts as a shared secret and can be restricted by source.
  retries: Buska does not retry a failed webhook delivery and does not keep a replay log.
docs: https://www.buska.io/integrations/webhook

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/buska-io-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.