secret.
A workspace may have a small, fixed number of webhooks configured at once; create returns an error once that limit is reached.
Webhook URLs must use
http:// or https:// and resolve to a public address. Other schemes, and URLs that resolve to a loopback, private, or link-local address (including cloud metadata endpoints), are rejected — both at creation/update time and again at delivery time.Endpoints
The Webhook object
Object type identifier. Always
"webhook" for Webhook objects.Unique identifier (UUID) for this webhook.
The endpoint that receives event deliveries.
Current webhook status. Possible values:
active, inactiveSigning secret used to verify the
x-fngs-signature header on each delivery.Unix timestamp (milliseconds) when the webhook was created.
Unix timestamp (milliseconds) when the webhook was archived.
null if not archived.The Webhook Attempt object
Each delivery attempt — success or failure — is recorded and available via theattempts endpoint.
Object type identifier. Always
"webhook_attempt" for Webhook Attempt objects.Unique identifier (UUID) for this attempt.
Retry sequence number for this delivery.
0 is the first try.HTTP status code returned by the receiving endpoint.
null if the request itself failed (timeout, connection error, blocked URL).The request body that was sent.
The parsed JSON response body, if any.
Unix timestamp (milliseconds) when the attempt was made.
Example response
Related resources
Events
The notification payloads webhooks deliver
Webhook Setup Guide
Configuring and verifying webhook deliveries