We’ve been using the DocGen API (https://developers.docusign.com/docs/docgensend-api/) to create pre-populated documents using a word template. In our word-template we’ve been using a custom font family Ciutadella.
We’ve been having mixed success with some generated documents (pdf output) looking accurate, and some seemingly using a different font or have issues with spacing or alignment.
Are custom fonts support by this API / Docusign, and if so what steps do we need to take to ensure it can be successfully used?
Thanks!
Best answer by Michael.Rave
@John H
Docusign eSignature does not support custom fonts, so all form fields can only be from the available fonts in eSignature. This was already answered here:
It may work with document generation, if the font is correctly embedded into the Word document. You need to test what output format this works. If you upload a PDF to eSignature the fonts should not be changed, but as stated above fields added in eSignature will only support the available fonts and no custom fonts.
Docusign eSignature does not support custom fonts, so all form fields can only be from the available fonts in eSignature. This was already answered here:
It may work with document generation, if the font is correctly embedded into the Word document. You need to test what output format this works. If you upload a PDF to eSignature the fonts should not be changed, but as stated above fields added in eSignature will only support the available fonts and no custom fonts.
You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.
You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.