Deliver an external trigger event

POST/v1/webhooks/triggers/{triggerId}

Public delivery endpoint for an enabled trigger. Authentication is performed by the source-specific webhook signature instead of a Computer Agents API key. Generic and custom webhooks use X-Webhook-Signature: sha256=<hex>; GitHub, GitLab, and Slack use their native signature headers.

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
triggerId	path	string	Yes	Trigger ID

Query parameters

None.

Header parameters

Name	Location	Type	Required	Description
X-Webhook-Event	header	string	No	Event name for generic and custom webhook sources.
X-Webhook-Signature	header	string	No	HMAC-SHA256 signature for generic and custom webhook sources.

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.

200Delivery acknowledged and either executed or intentionally skipped.application/json

Field	Type	Required	Description
acknowledged	boolean	Yes	—
executionId	string	No	—
threadId	string	No	Thread ID.
skipped	boolean	No	—
reason	string	No	—
ping	boolean	No	True for a signed GitHub setup ping. If a normal Thread destination is enabled, the ping also starts an isolated verification Thread.

400The signed request body could not be read or parsed for the selected provider.

None.

401The source-specific webhook signature is missing or invalid.

None.

404Trigger not found.

None.

409Trigger is disabled.

None.

500Webhook ingestion failed.

None.

Deliver an external trigger event

Response 200

See the ACP quickstart and SDK flow