Algoum · AsyncAPI Specification

Algoum De Webhooks

Version

View Spec View on GitHub CompanyFinanceSECInsider TradingAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-11-12'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://algoum.de/docs/streaming
sources:
- https://algoum.de/docs/streaming
- https://algoum.de/v1/docs/
description: 'Algoum provides two Server‑Sent Events (SSE) streams:'
events:
- event: event
  description: Material company events such as bankruptcies and leadership changes are pushed as JSON objects with an "event_type" field (e.g.
    "bankruptcy", "leadership_change").
- event: cluster_buy
  description: A new insider‑cluster‑buy is pushed when a threshold of distinct insiders is crossed, delivering the full cluster object.
delivery:
  auth: 'Bearer token passed in the Authorization header (e.g. "Authorization: Bearer <key>")'
  retries: If the SSE connection is dropped, clients are expected to reconnect with a growing back‑off (starting at 1 s, doubling up to 60 s).
    Rate‑limit applies to connection attempts and returns 429 with a Retry‑After header.
docs: https://algoum.de/docs/streaming

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/algoum-de-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.