How to respond to notification events
Tuesday, August 30, 2016 at 11:55amI have created a .Net web application to receive posts from the eSignLive server to handle event notifications (PACKAGE_CREATED, DOCUMENT_SIGNED, etc.) I am successfully receiving the events, parsing the Json posted to me, and handling the events. My post method is returning an HttpResposeMessage with a Status of 'OK', but for some reason, the eSignLive server is sending me emails telling me that the callback failed because it failed to contact the callback server. It certainly did contact my server, so I'm assuming that it might be expecting something more from me in the HttpResponseMessage, in order for the server to know that I received and handled the post. What do I need to do in order to correctly respond to these eSignLive event notification posts, so that I do not get these failure emails? I am currently testing using the sandbox server, if that matters.
Reply to: How to respond to notification events
Wednesday, August 31, 2016 at 06:26amReply to: How to respond to notification events
Wednesday, August 31, 2016 at 06:56amReply to: How to respond to notification events
Wednesday, August 31, 2016 at 07:10amReply to: How to respond to notification events
Friday, September 2, 2016 at 07:17amReply to: How to respond to notification events
Friday, September 2, 2016 at 10:44am- receive the json payload from esignlive
- use the info in the json to do some other tasks
- when all tasks are completed, send the 200 OK response back to esignlive
If this indeed the case, then definitely the request times out after x number of seconds. For obvious reasons, esignlive will not wait indefinitely for you to send a 200 OK response back. I would advise you to send the response back to esignlive as soon as you receive the json payload and then subsequently complete whatever tasks need be done.Reply to: How to respond to notification events
Wednesday, September 28, 2016 at 06:00amReply to: How to respond to notification events
Wednesday, September 28, 2016 at 06:24amReply to: HeythereThatis
Thursday, July 23, 2020 at 10:14amI've noticed you set this up on Heroku. Can you tell me if there is an add-on or other type of configuration I need to set up to get the listener working on Heroku?
**EDIT**
Disregard. I was using my registered domain instead of heroku's "myapp.heroku.com". Once I started using that, the service worked.