Skip to main content

Customer ODD Status

This event is triggered when the compliance status, as a result of the KYB process, is anything other than complete for a client.

https://<customerHost:Port>/webhook
FieldDescription
Content-Typeapplication/json

Request example

example webhook when oddStatus is odd_due

curl --location --request POST 'https://<customerHost:Port>/webhook' \
-H 'content-type: application/json' \
-d '{
"clientHashId": "86ce8d7b-f3fa-46d5-8d1c-53212aade5b5",
"customerHashId":"857dc08e-dffa-4e9a-ad96-79041c8a7025",
"oddStatus":"odd_due",
"template": "CUSTOMER_ODD_STATUS_WEBHOOK",
"customerType":"corporate"
}'

Request body

FieldDescriptionType
clientHashIdThis is the clientHashId of the client.UUID
customerHashIdThis field contains the unique customer identifier generated at the time of customer creation.UUID
oddStatusThis field contains the status of the odd process. Possible values of oddStatus: odd_due, odd_initiated, odd_completedString
customerTypeThis field contains the status of the customer. The possible values is: corporateString
templateThe value for this field is CUSTOMER_ODD_STATUS_WEBHOOK.String