tiberiuswest's account

Please explain and show example code with sample output how to retrieve by looping 100 at a time. You say you can do it, but there is no documentation that supports what you are saying. The only optional parameters for the completion report is, from and to, and these are dates.

Ok, I will be more specific as to minimize confusion. At this time we have to manually receive a transactions report from eSL on request. But because we need this daily, we need to automate the process. At first, it was eSL's suggestion to use an existing API call to get that same information. So I tried doing that using several different ones, the closest to what we needed was the completion report. But that has a limit of 100. I've used the SDK and also tried directly calling the APIs, but none have return what is needed. Specifically, we are looking for an API that can retrieve by date range (in our example, the prior day) transaction statuses by using the update date. Example: if today is 9/29/2017, I would like to call an API that can retrieve the status information for packages that were updated on 9/28/2017. I don't want to return the entire JSON payload or only package names. We need the fields like we get in the transaction report or the completion report (most importantly needed are the Package Id, Status, and Update Date). I need this for ALL statuses, sent, draft, expired, completed....etc. We have thousands of transactions for any one day of processing, way above the 100 limit. In your response, It seems like you are talking about mixing parameters from different API reports. In my communications with eSL's Sam Habbab, Senior Product Mananger, he is being told from his R&D department that this can not be done and there is not an existing API to do this. He is asking them if they can change the 100 transaction limit. But that being said, I am still hopeful that you indicate that this still may be possible using existing APIs. It's also possible that we are just not on the same page as to what I am requesting and what you are answering. If you do know a way to accomplish this, it would really be appreciated. Let me know if you need more information or if there is a way I can work with you directly. If this forum is the only why to communicate, then that's fine also. Thank you for your attention to this.

Ok, now we are getting somewhere. This looks very promising. I have a question about the &query= parameter. What are all the valid values? I know I can do sent, completed, draft, etc... separately. But, when I put any other value("&query=blah") or even, no value("&query="), then I get all the statuses returned. Do you see a problem with using it this way? Returning all statuses is what I am looking for, so this looks like what I need.

If you refer back to my previous post on this subject, we had worked to successfully get the api working and sending the info that we needed. Everything was working great until recently, it stop working. Did something change there? Something with the authentication? this is my header info: private static string API_KEY = "our app key here"; private static string API_URL = "https://sandbox.esignlive.com/api"; HttpClient httpClient = new HttpClient(); httpClient.DefaultRequestHeaders.Add("Authorization", "Basic " + API_KEY); httpClient.DefaultRequestHeaders.Add("Accept", "application/json"); this is the error it's now returning: System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream. at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult) at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar) --- End of inner exception stack trace --- --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task`1.get_Result() at SDK.Examples.GetPackageData.Main(String[] args) in c:\Git\mytest4\mytest4\Program.cs:line 28 ---> (Inner Exception #0) System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream. at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult) at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar) --- End of inner exception stack trace ---

Thanks for the info. We are using .net 4.5 code. I found this documention and added the SercurityProtocalType.Tls12 before the api connection, this fixed the issue: .NET 4.6 and above. You don’t need to do any additional work to support TLS 1.2, it’s supported by default. .NET 4.5. TLS 1.2 is supported, but it’s not a default protocol. You need to opt-in to use it. The following code will make TLS 1.2 default, make sure to execute it before making a connection to secured resource: ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 .NET 4.0. TLS 1.2 is not supported, but if you have .NET 4.5 (or above) installed on the system then you still can opt in for TLS 1.2 even if your application framework doesn’t support it. The only problem is that SecurityProtocolType in .NET 4.0 doesn’t have an entry for TLS1.2, so we’d have to use a numerical representation of this enum value:ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072; .NET 3.5 or below. TLS 1.2 is not supported (*) and there is no workaround. Upgrade your application to more recent version of the framework.