I am not able to find out the issue while reading received json? How can I debug ?
For UAT you may create a temporary public endpoint on websites like https://requestbin.com/, update your webhook endpoint on Digio Enterprise Dashboard (Profile section) and perform a transaction where webhook is triggered. These public endpoint show the received data (Headers and Body) in readable format.
Observe received headers and Body and fix the issue in your code
Related Articles
I am not able to identify why my webhook is failing, is there a way to find out what error Digio is receiving while hitting my webhook?
Yes. When an email notification is sent about webhook failure, it contains HTTP Error code, Error message received and The Entity id (eg. Document id or Mandate id) for which the webhook attempt is continuously failing.
'No User Found' error occurs during first-factor authentication on the SDK. What could be causing this issue?
This issue may arise when the identifier used during request creation differs from the one utilized to invoke the SDK.
I have received 20+ webhook calls for the same webhook event, but none for any other - what does this mean?
A queue is maintained for each account, event on top is reattempted till a 200 response is received. If your endpoint is not returning a 200 http response you might observe multiple attempts on the same object, till webhooks are disabled or a 200 ...
'You are not authorized to take this action' error occurs when invoking the JS SDK. What could be causing this issue?
Typically, this issue arises due to an incorrect user identifier passed in the digio.esign function. Kindly recheck the identifier(DID) with respect to the document you have generated.
Where can I find the document ID?
The document ID can be located in two places: In the response of the API call. In the dashboard, navigate to the "sent" section, click on the document you want to preview, and the document ID will be visible in the URL starting with "DID*"