Ingest a repository-scoped source-control webhook
POST
/v1/webhooks/github/resource-source-control/{bindingId}Verifies the binding-specific X-Hub-Signature-256, validates the repository identity, deduplicates X-GitHub-Delivery, and dispatches source synchronization and scoped repository automations without exposing the connected user's OAuth credential.
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
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| bindingId | path | string | Yes | — |
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.
400Invalid binding or payload
None.
401Invalid signature or delivery metadata
None.
404Repository connection not found
None.
409Repository identity or delivery conflict
None.
500Processing failed; GitHub may retry the delivery
None.
Ingest a repository-scoped source-control webhook
Loading...
Response 202
Loading...