Financials

Financial statement case process completion event

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

postWebhookfinancial_statement_cases_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 ID in our system

document_idsstring[] required

List of document IDs for the case

customer_idstring nullable

Customer ID in our system for the customer the case belongs to

asset_idstring nullable

Asset ID in our system for the asset the case belongs to

external_customer_idstring nullable

external customer id for the customer the case belongs to

case_namestring nullable

Case name

case_priorityinteger nullable

Case priority

case_status'pending' | 'processing' | 'waiting_on_client' | 'completed' | 'cancelled' | 'waiting_on_end_customer' required

Case status

review_type'initiation' | 'monthly' | 'quarterly' | 'semi_annually' | 'annually' | 'ad-hoc' nullable
created_atstring date-time required

Case creation time

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.