Merico · AsyncAPI Specification

Merico Devlake Webhooks

Version

View Spec View on GitHub CompanyDevToolsEngineering IntelligenceDevOpsDORA MetricsSoftware AnalyticsOpen-SourceData PlatformAsyncAPIEvents

AsyncAPI Specification

merico-devlake-webhooks.yml Raw ↑
generated: '2026-07-20'
method: searched
source: https://devlake.apache.org/docs/Plugins/webhook/
spec_type: Webhooks
direction: inbound
summary: >-
  Apache DevLake (the open-source engine behind Merico DevInsight) exposes an
  inbound webhook connector. When no dedicated plugin exists for a DevOps tool,
  users register a webhook in DevLake and actively PUSH issue, deployment, and
  incident data to DevLake's webhook endpoints. This is an ingest/receiver
  webhook surface rather than an outbound event-notification stream.
webhooks:
- name: incident
  description: Push incident open/close events into DevLake for DORA calculation.
  method: POST
  path: /api/plugins/webhook/{connectionId}/issues
- name: deployment
  description: Push deployment/CICD pipeline events into DevLake.
  method: POST
  path: /api/plugins/webhook/{connectionId}/deployments
docs: https://devlake.apache.org/docs/Plugins/webhook/

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/merico-devlake-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.