KYC

Case Process Completion Event

HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers:

x-accend-signature-256: 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-type: This header will contain the type of event that triggered the delivery.

x-accend-idempotency-key: This header will contain the idempotency key of the request.

postWebhookcase-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

case_idstring required
case_titlestring required
company_legal_namestring required
company_namestring required
assignee_idstring nullable
assignee_namestring nullable
priority'High' | 'Medium' | 'Low' required
status'Open' | 'Closed' | 'Approved' | 'In Progress' | 'Awaiting Information' | 'Declined' required
created_atstring required
updated_atstring required
completedboolean

Whether the case analysis is completed

case_type'Onboarding' | 'Periodic' | 'Ad Hoc' nullable

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.