GitHub Push and PR Events

GitHub webhook payload example for push and pull_request automation pipelines.

Receives GitHub repository events for CI triggers, deployment gates, and issue automation.

Endpoint URL

Use this endpoint when configuring the webhook sender:

https://hook-gt4z9s.fasthook.io/

Example request (curl)

curl -X POST "https://hook-gt4z9s.fasthook.io/" \
  -H "Content-Type: application/json" \
  -H "X-GitHub-Event: push" \
  -H "X-Hub-Signature-256: sha256=***redacted***" \
  -d '{"ref":"refs/heads/main","repository":{"full_name":"acme/payments-api"}}'

Example headers

{
  "content-type": "application/json",
  "x-github-event": "push",
  "x-hub-signature-256": "sha256=***redacted***",
  "user-agent": "GitHub-Hookshot/*"
}

Example payload (JSON)

{
  "ref": "refs/heads/main",
  "after": "5f6b7a",
  "repository": {
    "full_name": "acme/payments-api"
  },
  "pusher": {
    "name": "dev-user"
  }
}

How this webhook works

  1. Provider sends a POST request to the endpoint URL.
  2. FastHook receives and logs the request envelope.
  3. Handlers validate signature and parse payload.
  4. Failed deliveries can be replayed after fixes.

Common debugging checks

  • Validate x-hub-signature-256 with HMAC SHA-256 and timing-safe compare.
  • Filter noisy events by branch and event type before heavy processing.
  • Track delivery IDs to prevent duplicate workflow execution.

Integration context

This page targets github webhook flows and is optimized for debugging and testing scenarios developers face in production.

Last updated: Apr 21, 2026

Owner tools

Need full request logs and secure controls? Use the private owner view in dashboard for replay, filters, transformations, and access management.

Open private request logs