Ingest a signed GitHub App webhook
POST
/v1/webhooks/github/securityVerifies X-Hub-Signature-256 against the unmodified request body, deduplicates X-GitHub-Delivery, persists only a minimized event projection, and queues exact-SHA runs for matching policies.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
None.
Query parameters
None.
Header parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| X-Hub-Signature-256 | header | string | Yes | — |
| X-GitHub-Delivery | header | string | Yes | — |
| X-GitHub-Event | header | string | Yes | — |
Body schema
Content type: application/json · Required
None.
What the API returns
Each response code below includes the documented payload shape for the ACP API.
202Webhook acknowledged
None.
401Invalid signature or delivery metadata
None.
500Processing failed; GitHub may retry the delivery
None.
Ingest a signed GitHub App webhook
Loading...
Response 202
Loading...