bytedev's account

Thanks for the thoughts. Again, my listener is receiving post requests just fine. it is serializing the Json received just fine. It is processing them just fine. All I need to know is whether the ESignLive servers are expecting Json back in the Content property of the HttpResponseMessage, and in what form that Json needs to be in, so that I can properly inform their servers that I handled the request, so I don't get the 'Failed to communicate with server' messages. The server did NOT fail to communicate with me. I just need to know how (apparently) to tell the server that. If no Json is required in the response, then I will have to start looking elsewhere, but this seemed the most likely answer to the problem. So, to restate, all I am looking for is the answer to the question of whether the ESignLive servers are expecting Json back on the Content property of the HttpResponseMessage class, and in what form that Json would take.

So is the server timing out waiting for my response then? If so, is there any example code you can point me to that would demonstrate how to set up a web application (.Net) controller with the correct type of asynchronous methods? The reason I asked the above question is because I have another vendor who DOES expect to get Json back in the response. Since not all of my requests are causing the eSignLive servers to send me a failure email, I'm thinking that it is taking too long for me to respond, and that is the cause. But I have found no example code that would point me in the right direction on how to define my controller methods properly to handle the requests asynchronously (if that is what is required).