Truffle Security · AsyncAPI Specification

Truffle Security Webhooks

Version

View Spec View on GitHub CompanySecuritySecrets DetectionSecrets ScanningDevSecOpsApplication SecurityCredential ScanningTruffleHogOpen-SourceAsyncAPIEvents

AsyncAPI Specification

truffle-security-webhooks.yml Raw ↑
generated: '2026-07-21'
method: searched
source: https://trufflesecurity.com/docs/webhook.md
spec_type: Webhooks
summary: >-
  TruffleHog Enterprise can deliver scan findings to external systems via outbound webhook
  notifications. The "Webhook" destination and the "Notify results" configuration document HTTP
  callbacks that push detected/verified secret findings to a configured endpoint. No public
  AsyncAPI document is published; this captures the documented webhook (event push) surface only.
docs:
- https://trufflesecurity.com/docs/webhook.md
- https://trufflesecurity.com/docs/notify-results.md
channels:
- name: scan-result-notification
  direction: outbound
  transport: http
  description: >-
    Scan results / findings are pushed to a customer-configured webhook endpoint as a
    notification destination. Payload schema is not published in the public docs index.

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/truffle-security-webhooks"
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 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.