Callback Setup with REST API

Just to clarify, there is only one callback url per esignlive account. The functionality and what is returned to you with callbacks is exactly the same whether you set it up from the UI or through code. Setting up callbacks through code can be particularly useful for an OEM or a SaaS type application that has esignatures as a feature and they set up a new account for users (make the process automated). If you're only setting up one account, then going through the UI makes more sense.

Hi David, Indeed, callback event notifications are on an account level. Practically anything you can do through the esignlive UI, you can achieve through the REST API. If you setup callback through code, it will still be on an account level (same functionality). Hope this answers your question :)

Doesn't seem really worth the effort to setup via code then if all that can be done is run once. How do customers handle different applications possibly having different callback urls? Setup multiple eSign accounts? Or send all callbacks to a single url through a client's enterprise service bus? Is there a specific metadata about the package returned with the callback url? Thaanks, David

From the callback json payload contains a packageid. We could associate this package id to the type of eSign request (document sign) and route/redirect to a more granular url endpoint. All this on the client backend side. -David

Yes, once you've received the notification from esignlive, you're free to process the information however you see fit. For example, you might want to listen for the "PACKAGE_COMPLETE" event and download the signed documents as soon as the package/transaction is completed.