Skip to main content
This topic has been closed for replies.
Correct answer SimonATS

I cannot work with a document with text tags. I'm creating the pdf automatically in my system. The end user just need to sign it.

If I open the PDF in Acrobat it doesn't show anything in the signature panel

I tried setting the content type as SIGNATURE but it didn't worked..

Could you please verify (it's ok if you can look next week).

Thank you.

Martino


Hi Martino,

I received confirmation from our product teams that digital signature field creation via the api is not supported.

2 alternative approaches which work if they ar epractical for you

-when creating the pdf, inject the digital signature text tag:

{{digsig1_es_:signer1:digitalsignature}}

https://helpx.adobe.com/content/dam/help/en/sign/adobesign_text_tags_guide.pdf#page=19

If your pdf creation solution lets you add acrobat form fields, you could also add an acroform text field with the name:

digsig1_es_:signer1:digitalsignature

- Make   use of field layer templates. If your PDF output is consistent (in number of pages and page size and location of page elements) form layer templates are an option as well. To make use of this, take a sample pdf output and use this to create a library template via the webportal. When doing this you are given the option to make it a form field layer template. (or use the api to create one)

When creating this template, place the required fields on the document.

Then when the time comes you can use this layer template to 'stamp' the field on the pdf you upload. So you only get the field place in the same location.

In your api call to create the agreement, instead of specifying each field, simply refer to the form field layer template. (again use the API to retrieve the Agreement/templateId first)

1 reply

S
SimonATS
Legend
October 6, 2017

yes, though you need to add a dig sig field to your document.

martinobordin
martinobordinAuthor
Participant
October 6, 2017

Hi Simon, thanks for the reply.

What is the right way to do it using the API?

I explain the problem better and what I did till now.

In this Pastebin you can see the request I have submitted: [JSON] Adobe Sign Sample Rest Request - Pastebin.com

As you can see, I pass a field of type "PDF_SIGNATURE" (that seems not supported by the API)

However, I received the email and if I open the link I can see that the  field for the sign with a certificate is present:

Then I select to download the file and sign it with a local certificate (sorry, the UI is in Italian)

When I open the downloaded file, I can see my signature, but there's no more the digital signature field

What am I doing wrong? Is it supported only if I have a full account? Right now I'm still evaluating the service but I will buy it if this scenario is supported.

Please let me know.

Martino

S
SimonATS
Legend
October 6, 2017

unfortunately i don't have time to look into this before the weekend, but how does it compare to when you use the webportal to send and agreement with a digital signature field that way?

Mostly the experience you describe seems expected, bar the last step i'm not sure about. If you open the pdf in acrobat and open the signature panel do you see your cert signature there

one thing, try setting the content type to Signature as well as the input type of PDF signature.

An alternative would be to work with a document with text tags (which usually is an easier way to add fields rather than creating them via the api)

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices