Skip to main content

We host in-person meetings, and want the attendees of the meeting to sign the meeting document via a tablet that gets passed around.  We don’t know who the attendees/signers will be, or how many, but we want them to sign the document within our web application.

  

After a lot of experimentation with Docusign’s APIs, we’ve taken this approach:

  1. We create an envelope (POST to /restapi/v2/accounts/{accountId}/envelopes) with 100 allocated signers (the maximum allowed and hopefully more than will ever attend our meetings).  These are placeholder signers.  Our document also has 100 lines allocated for recording attendee information which feature anchor tags for recording the signature (\s1\, \s2\, etc.), anchor tags for the attendee’s name (\n1\, \n2\, etc.), and anchor tags for recording the attendee’s company (\c1\, \c2\, etc.)
     
  2. As each attendee enters their information on the tablet, we call Docusign’s recipient-update API endpoint (PUT to /restapi/v2/accounts/{accountId}/envelopes/{envelopeId}/recipients), and update the corresponding allocated signer with that attendee’s actual information (Company, First Name, Last Name).  After the attendee enters their information we call Docusign’s recipient-view API (POST to /restapi/v2/accounts/{accountId}/envelopes/{envelopeId}/views/recipient) to get the URL for that signer, which we display in our application and which allows them to sign, and their information is placed at the corresponding anchor tags in the document.
     
  3. When all attendees have entered their information and signed, we call Docusign’s recipient-delete  API endpoint (DELETE to /restapi/v2/accounts/{accountID}/envelopes/{envelopeId}/recipients) and remove any remaining/excess allocated placeholder signers from the envelope, which automatically completes the process, and then we download the completed document.


This all seems to work fairly well, but the problem we’re running into is with step 2.  Docusign is able to update the allocated signer’s name, and use that for the signature very nicely, and it’s able to place both the attendee’s name and signature at the designated anchor tag locations in the document.  But no matter what we try we cannot figure out how to get the attendee’s company to be displayed in the document at the designated company anchor tag. 

 

We’ve tried using text tabs and other types of tags, but the best we’ve been able to do is have Docusign display is a square text box at the company anchor tag, where the attendee then has to type their company name again.

Is there any way to get that anchor tag/field pre-populated and set to the attendee’s company name?


 

@Redbird19 

Have you tried this? https://stackoverflow.com/questions/50379986/populate-docusign-company-tab


Hi ​@JohnSantos,

 

Yes, I’ve tried using Text Tab and providing a value, but it ignores the value provided and just displays a text box for the attendee to enter their company name at the anchor tag location instead of actually setting/using the text/value like it does for the signer’s name.

 

Now, I should mention that if I call the create-envelope API endpoint, and provide values for the recipient signers Text Tabs at that time, then the company name is displayed appropriately (no text box).  But we don’t know who the signers will be at that time so can’t do that, which is why we’re creating placeholder signers and then updating with the real signer information as we collect it from the attendees.  This works great for the signer’s name and signature, but not for Text tabs or Company values, which just displays text box prompt.  

 

Thanks  


@Redbird19 

Don’t place a “company” Text tab in the envelope at create time. Instead, add a Text tab for that recipient after you update the placeholder to the real attendee; using the Create tabs endpoint (which can add tabs to an in‑process envelope). Then lock it so the attendee can’t edit it.


Hi ​@JohnSantos,

 

Thank you so much!  That worked like a charm!

 

Thanks!