AirMDR · AsyncAPI Specification

Airmdr Webhooks

Version

View Spec View on GitHub SecurityManaged Detection and ResponseSecurity OperationsAlert TriageIncident ResponseAI AgentsSOC AutomationThreat DetectionMCPA2AAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-09-19'
method: searched
source: https://docs.airmdr.com/api-reference/WebHook, openapi/airmdr-case-manager-openapi.yml (Webhooks tag), https://docs.airmdr.com/changelog/changelog (M28.1)
asyncapi_spec: null
asyncapi_probes:
- url: https://docs.airmdr.com/asyncapi.yaml
  status: 404
- url: https://docs.airmdr.com/asyncapi.json
  status: 404
- url: https://app.airmdr.com/docs/api/asyncapi.yaml
  status: 404
- url: https://airmdr.com/asyncapi.yaml
  status: 404
direction: inbound
summary: >-
  AirMDR's webhook surface is INBOUND only: customers and third-party tools POST alerts INTO AirMDR. AirMDR does not
  publish an outbound event/webhook catalog — notification of case activity is delivered through integrations
  (Slack, MS Teams, PagerDuty, Jira, email) configured inside playbooks, not as subscribable HTTP callbacks, and no
  AsyncAPI document is published anywhere.
webhooks:
- name: Alert ingestion (token-authenticated)
  direction: inbound
  method: POST
  url: https://app.airmdr.com/airmdrapi/alerts
  operationId: createAlertsAPI
  auth: 'Cookie: Session="<API token>"'
  payload:
    alert_content: string (required)
    alert_provider: string (required) — e.g. aws, microsoft_graph, cyberhaven
    organization_code: string (required) — e.g. ASO
    alert_type: string — required for Darryl to auto-investigate
    created_at_source: integer int64 epoch seconds (optional)
  response: 201 with alert_id (ORG-PROVIDER-<seq>), alert_uuid, investigation_status
  docs: https://docs.airmdr.com/api-reference/WebHook
- name: Alert ingestion (URL-secret webhook)
  direction: inbound
  method: POST
  url: https://app.airmdr.com/airmdrapi/webhooks/{webhook_id}/{secret}/alerts
  operationId: createAlertFromWebhookAPI
  auth: webhook_id + secret embedded in the URL path (no headers required)
  payload: the entire request body is the alert content (no wrapper key)
  responses:
    201: alert created
    404: unknown webhook_id or invalid secret
    409: duplicate alert
  management:
    create: createWebhookAPI (POST /webhooks) — Admin/Super Admin only
    list: listWebhooksAPI (GET /webhooks)
    delete: deleteWebhookAPI (DELETE /webhooks/{webhook_id})
  added: M28.1 (2026-09-16) — "Webhook Alert Ingestion Without Custom Authentication Headers"
  controls: authentication verification, duplicate-alert handling and rate limiting per the release notes (no published numbers)
  docs: https://docs.airmdr.com/changelog/changelog
event_states:
  investigation_status:
    0: Created
    5: Submitted
    10: InProgress
    15: Completed
    20: Failed
  note: polled via getAlertAPI; there is no push callback for investigation completion

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/airmdr-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.