Skip to main content
arrow-left Back to Docusign.com

Bonjour,

Je vous contacte concernant un dysfonctionnement observé lors de l'envoi de documents XML via l'API DocuSign.

Jusqu’à récemment, nous pouvions transmettre des fichiers au format .xml dans une enveloppe, et ceux-ci étaient correctement interprétés et affichés de manière lisible dans l'interface DocuSign.
Cependant, depuis peu, bien que l’appel à l’API (POST /envelopes) retourne un code 201 (Created), le document XML n’est plus converti ni affiché correctement. Il apparaît désormais sous forme brute (texte XML non rendu) pour les signataires, ce qui nuit à la lisibilité et à l’expérience utilisateur.

Je souhaiterais savoir :

  • Si ce changement est volontaire (ex. : mise à jour du moteur de rendu DocuSign)

  • Ou s’il est possible de restaurer le comportement antérieur via une configuration spécifique

Dans l’attente de votre retour,

 

Hi Envi,

 

This is Alice, Developer Support Engineer at Docusign. It is nice to meet you.
 

The Docusign API, given its nature, will not run a rendering engine but itself but, rather, use the document binary information received to pass to it. This means the document rendering pass is the same between using Docusign Web and the API as we try to provide via API an experience as close to the whole core Docusign experience as possible.

With that said, try uploading the XML document to Docusign directly, as it goes through the same document rendering process. If there is a discrepancy, something may have happened on passing the document binary information via API.

 

Overall we will need to review the actual XML document, envelope, and the API call for a more contextualized follow up, so please feel free to open a case with us at any time here and we will be there: https://support.docusign.com/s/cases

 

I hope that helps!

 

Best regards,

 

Alice Goglione (she/her) | Developer Support Engineer II

NPikcCCy65KbqEI-Qwh7_-2s-pMm9JQ0NWFuBi_87cbSqVm1ezaRscPxxxn8hNpSDIntAJY_Df2XcFQnyrz2xpyCN7Almg7rZJJa3P3UjP7pKPmIUPLHMjSgigZnQcgQfxtGOcR1EW4EQ-9RuoTfLA

 

​
Hello,

I have the same problem described by @envi.

We have been using the Docusign API to create documents for almost 3 years and the application has worked very well during that time.
But since the beginning of June, we have been receiving many complaints from our customers because the XML we send to create the envelope is no longer converted.
The document ends up being displayed as pure XML, which makes customers suspicious about inserting the signature on the documents.
Has there been any change in the technology, or in the way these XMLs sent to create envelopes are interpreted?
Because our system has not been updated in the last 6 months, so there is no possibility of it being an error in it.

Hi,

We will need to investigate this further. My suggestion on testing the XML upload against Docusign web directly might seem a bit "generic” but actually contextualize possibly unwanted changes and at which step, so we can take action.

This is very important when discussing the impact scope of the issue, given your report as well. 

 

Following up, likewise, please open a support case with us as we will need to check the files involved, envelope, and API in more details: https://support.docusign.com/s/cases

 

Best regards,

 

Alice Goglione (she/her) | Developer Support Engineer II

NPikcCCy65KbqEI-Qwh7_-2s-pMm9JQ0NWFuBi_87cbSqVm1ezaRscPxxxn8hNpSDIntAJY_Df2XcFQnyrz2xpyCN7Almg7rZJJa3P3UjP7pKPmIUPLHMjSgigZnQcgQfxtGOcR1EW4EQ-9RuoTfLA

Reply


Code of Conduct

Docusign Community

Code of Conduct