You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I noticed when trying to create a template using the DocuSign.eSign.dll 4.1.1 nuget package that all of the properties on the TemplateSummary response are null like so:
I hit the rest endpoint, https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/templates, in docusign via Postman doing a POST request and got back the following response:
Thank you for the bug report. I've investigated it, and I believe that the problem is that the Swagger file produced by our core platform group is incorrectly specifying that the API call returns a TemplateSummary.
But the reality is that an array (of length 1) is being returned. I've filed internal bug EC-1876
At this point, I doubt that we'll change the API. But we should document the result correctly in the Swagger file. Once that's done, the next time the C# SDK is rebuilt, it will be fixed, along with the documentation. (They're both generated from the Swagger file.)
A question for you: in my test, the result was a 1 element array with an object that had templateId, uri, and name attributes. But your POSTMAN test doesn't show the latter. Did you leave it out? Did you test with API v2 or v2.1? (I used v2.1.)
That was just a quick test that I ran against 2.1 sending an empty post body to see the response structure. Below is the curl for that request to get that response.
Hey, I noticed when trying to create a template using the DocuSign.eSign.dll 4.1.1 nuget package that all of the properties on the
TemplateSummary
response are null like so:I hit the rest endpoint,
https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/templates
, in docusign via Postman doing a POST request and got back the following response:I believe that the TemplateSummary properties aren't mapping correctly from the response, do we think this could be true?
The text was updated successfully, but these errors were encountered: