AsyncAPI channel · GitLab
· GitLab Webhooks
/webhook
The endpoint that receives all GitLab webhook event deliveries. The specific event type is identified by the X-Gitlab-Event header.
Channel address
/webhook
Operations
publish
receiveGitLabWebhookEvent
Receive a GitLab webhook event
Messages
PushEvent
Triggered when code is pushed to a repository branch.
Content-Type:
TagPushEvent
Triggered when a tag is created or deleted.
Content-Type:
MergeRequestEvent
Triggered when a merge request is created, updated, or closed.
Content-Type:
IssueEvent
Triggered when an issue is created, updated, or closed.
Content-Type:
NoteEvent
Triggered when a comment is added on a commit, MR, issue, or snippet.
Content-Type:
PipelineEvent
Triggered when a CI/CD pipeline changes status.
Content-Type:
JobEvent
Triggered when a CI/CD job changes status.
Content-Type:
DeploymentEvent
Triggered when a deployment starts, succeeds, fails, or is canceled.
Content-Type:
ReleaseEvent
Triggered when a release is created, updated, or deleted.
Content-Type:
MemberEvent
Triggered when a group member is added, removed, or changes access level.
Content-Type:
WikiPageEvent
Triggered when a wiki page is created, updated, or deleted.
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.