Webhook Callback Description
You need to log in to eSignGlobal, navigate to Settings → Integrations → Webhook, and configure the callback address on the editing page.
- When the HTTP status code returned to eSignGlobal is between 200 and 299, the notification is considered successful. Otherwise, eSignGlobal treats the notification as failed.
- Retry Mechanism:
If a notification fails, the eSignGlobal notification service will retry up to 16 times. Depending on the module, one of the following two retry mechanisms may be used. If a retry attempt is successful, the notification process stops immediately.
- To prevent repeated notifications due to JSON parsing errors in the eSignGlobal notification service, ensure that the returned JSON data does not contain special characters such as spaces or backslashes. We recommend returning {"code":"200","msg":"success"} directly upon successful receipt of the data.
- To ensure the timeliness and reliability of callback notifications, developers should respond to the eSignGlobal notification service with an HTTP status code 200 within 5 seconds of receiving the callback.
- If your application cannot complete the callback-related business processing within 5 seconds, use asynchronous processing for any subsequent business logic.