Automations

Automation run completion event

HTTP POST payloads that are delivered to your webhook's configured URL endpoint.

postWebhookautomation_run_completion_event

Headers

x-accend-signature-256string required

This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and your api token as the HMAC key.

x-accend-event-typestring required

This header will contain the type of event that triggered the delivery. supported values: 'case-event' for KYC cases completion, 'financial_statement_cases_event' for financial statement cases completion, 'link_sync_completion_event' for link sync completion events, 'automation_run_completion_event' for automation run completion events

x-accend-idempotency-keystring required

This header will contain the idempotency key of the request.

Payload

automation_idstring required

run_idstring required

completed_atstring date-time required

Response

Successful Response

unknown required

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.