Sourcegraph

Sourcegraph Webhooks

Sourcegraph instances expose three distinct webhook surfaces. Outgoing webhooks (Site Admin > Configuration > Outgoing webhooks) push batch_change, changeset, and user:create events to external HTTP endpoints. The code monitoring webhook action delivers per-monitor JSON POSTs when a saved search returns new results. Incoming webhooks (Site Admin > Integrations > Incoming webhooks) receive push, batch-change, and permission events from GitHub, GitLab, Bitbucket Server, Bitbucket Cloud, and Azure DevOps.

GitHub

Documentation

📖
Documentation
https://sourcegraph.com/docs/admin/config/webhooks
📖
Documentation
https://sourcegraph.com/docs/admin/config/webhooks/outgoing
📖
Documentation
https://sourcegraph.com/docs/admin/config/webhooks/incoming
📖
Documentation
https://sourcegraph.com/docs/code_monitoring

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/sourcegraph-webhooks"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: sourcegraph:sourcegraph-webhooks
name: Sourcegraph Webhooks
description: Sourcegraph instances expose three distinct webhook surfaces. Outgoing webhooks (Site Admin
  > Configuration > Outgoing webhooks) push batch_change, changeset, and user:create events to external
  HTTP endpoints. The code monitoring webhook action delivers per-monitor JSON POSTs when a saved search
  returns new results. Incoming webhooks (Site Admin > Integrations > Incoming webhooks) receive push,
  batch-change, and permission events from GitHub, GitLab, Bitbucket Server, Bitbucket Cloud, and Azure
  DevOps.
humanURL: https://sourcegraph.com/docs/admin/config/webhooks
tags:
- Webhook
- Event
- Outgoing Webhooks
- Incoming Webhooks
- Code Monitoring
tags_raw:
- Webhooks
- Events
- Outgoing Webhooks
- Incoming Webhooks
- Code Monitoring
properties:
- type: Documentation
  url: https://sourcegraph.com/docs/admin/config/webhooks
- type: Documentation
  url: https://sourcegraph.com/docs/admin/config/webhooks/outgoing
  name: Outgoing Webhooks
- type: Documentation
  url: https://sourcegraph.com/docs/admin/config/webhooks/incoming
  name: Incoming Webhooks
- type: Documentation
  url: https://sourcegraph.com/docs/code_monitoring
  name: Code Monitoring Webhook Action