BugTape · AsyncAPI Specification

Bugtape Ai Webhooks

Version

View Spec View on GitHub CompanyError TrackingAI AgentsDeveloper ToolsSoftware-as-a-ServiceAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-11-03'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://bugtape.ai/guides/stripe-webhook-signature-verification-failed/
sources:
- https://bugtape.ai/guides/stripe-webhook-signature-verification-failed/
- https://bugtape.ai/docs/webhooks/
- https://bugtape.ai/docs/webhooks/
- https://bugtape.ai/docs/webhooks.md
description: BugTape webhooks deliver JSON payloads for various bug‑related events.
events:
- event: new_bug
  description: A new issue is delivered; the payload contains details such as title, severity, reportCount, release, bugId, evidence, and timestamp.
- event: regression
  description: A previously seen issue that has re‑occurred is delivered.
- event: status_change
  description: A change in the status of an existing issue (e.g., open → resolved) is delivered.
- event: agent_notify
  description: A handoff event that notifies an agent; the body matches new_bug plus a "trigger" field set to "auto" or "manual".
- event: agent_update
  description: Progress updates for an agent, containing fields like "agentAction" ("working" or "pr_opened"), "agentActor", and optional "prUrl".
- event: comment
  description: A comment added to an issue is delivered.
- event: assigned
  description: An assignment change for an issue is delivered.
- event: recommended_bug
  description: A bug that BugTape recommends for attention is delivered.
- event: test
  description: A test event generated by the Send test button is delivered.
delivery:
  signature: 'X-BugTape-Signature-256: t=<unix seconds>,v1=<hex> (HMAC‑SHA256 of "<t>.<raw body>" with the signing secret). Older header X-BugTape-Signature:
    sha256=<hex> (HMAC‑SHA256 of raw body only).'
  retries: 'When a capture webhook is sent: 10 s, 1 min, 5 min, 30 min, then 2 h (six attempts total). A 401, 403 or other client rejection (except
    408, 425, 429) stops retries immediately; network errors, 408, 425, 429, or 5xx trigger the next delay. Non‑capture destinations (Slack, Discord,
    etc.) use one attempt then 4 exponential retries (10 s, then back‑off) before moving to webhook‑dlq.'
note: 'All webhook and agent POSTs include Content‑Type: application/json, X‑BugTape‑Event (event name), User-Agent (BugTape‑Webhook/1.0 or BugTape‑AgentWebhook/1.0),
  optional Authorization: Bearer <token>, and X‑BugTape‑Event‑Id / X‑BugTape‑Delivery‑Id when tied to a domain event.'
docs: https://bugtape.ai/guides/stripe-webhook-signature-verification-failed/

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/bugtape-ai-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.