docusign-esign-csharp-client
docusign-esign-csharp-client copied to clipboard
ListStatusWithHttpInfo operation in EnvelopesApi.cs
In the operation 'ListStatusWithHttpInfo', the HTTP method is set to 'PUT'. It should be 'GET'. Leaving it as 'PUT' is causing an HTTP status 400 Bad Request
This issue also exists in the 'ListStatusAsyncWithHttpInfo' operation. Could someone please make this change in the next release? This is a highly used operation to list out envelopes sent from a particular user and we can't use it because these operations are trying to perform a PUT method instead of a GET
Hi @jmitola , I think this is what you are looking for https://github.com/docusign/docusign-csharp-client/blob/master/test/SdkNetCoreTests/JwtAuthNetCoreUnitTests.cs#L229 ?
ListStatusChanges
is a GET method
https://developers.docusign.com/docs/esign-rest-api/reference/Envelopes/Envelopes/listStatusChanges/
Thanks Bharat, That did work. However, I still think the ListStatusWithHttpInfo operation should be a GET method. Even the name suggests it and all the other PUT methods are labeled as such. Plus, if you try and call it, it always returns in error because it is trying to do a PUT operation. Thanks for suggesting the alternative though, I will change my code to use the ListStatusChanges operation. Joe Joseph A. Mitola, Information Systems AnalystUniversity of California, BerkeleyIST - Enterprise Applications2195 Hearst Avenue, 250-29Berkeley, CA [email protected] From: Bharat ReleSent: Thursday, October 22, 2020 2:29 PMTo: docusign/docusign-csharp-clientCc: jmitola; MentionSubject: Re: [docusign/docusign-csharp-client] ListStatusWithHttpInfo operation in EnvelopesApi.cs (#301) Hi @jmitola , I think this is what you are looking for https://github.com/docusign/docusign-csharp-client/blob/master/test/SdkNetCoreTests/JwtAuthNetCoreUnitTests.cs#L229 ?ListStatusChanges is a GET methodhttps://developers.docusign.com/docs/esign-rest-api/reference/Envelopes/Envelopes/listStatusChanges/—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.