Ironflow · AsyncAPI Specification

Ironflow Sh Webhooks

Version

View Spec View on GitHub CompanyData APITradingSandboxHyperliquidMCPAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-11-12'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.ironflow.sh/guides/liquidation-alerts.md
sources:
- https://docs.ironflow.sh/guides/liquidation-alerts.md
- https://docs.ironflow.sh/api-reference/analytics/user-ledger.md
description: Ironflow provides liquidation alert webhooks.
events:
- event: liquidations
  description: Sent when one or more Hyperliquid liquidations match the alert criteria; includes an array of liquidation objects.
- event: test
  description: 'Sent in response to a test request; payload contains "type": "test".'
delivery:
  signature: 'X-Ironflow-Signature: t=<unix seconds>,v1=<hex>'
  retries: A failed delivery is retried once after 5 seconds; after 20 consecutive failures the alert is disabled.
note: Authentication is via the API key used when creating the alert; the webhook itself is secured by the HMAC‑SHA256 signature.
docs: https://docs.ironflow.sh/guides/liquidation-alerts.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/ironflow-sh-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.