Skip to main content
arrow-left Back to Docusign.com 
{
    "emailSubject": "Please DocuSign This NDA for ABC Company",
    "emailBlurb": "Please let us know if you have any questions.",
    "status": "sent",
    "templateId": "{{NDA Template}}",
    "customFields": {
        "textCustomFields": [{
          "name": "entityID",
          "value": "1234"
        }]
      },
    "templateRoles": [
        {
            "roleName": "Customer",
            "email": "{{Signer Email}}",
            "name": "{{Signer Name}}",
            "tabs": {
                "textTabs": [
                    {
                        "tabLabel": "company",
                        "value": "ABC Company"
                    }
                ]
            }
        }
    ]
}

 

Hi ​@Kapilsharma888,

If you’re facing an issue with populating a custom text field using the REST API, it’s worth double-checking a few things in your request:

  1. Field Configuration: Ensure that the custom field entityID is correctly configured in your DocuSign account as a text field. Custom text fields must be predefined in your account settings to work as expected.

  2. Case Sensitivity: The name of the custom field is case-sensitive. Verify that the field is named exactly as "entityID" in your account.

  3. Placement of customFields: Confirm that the customFields section is in the correct location within your request body. For envelopes, it must be included as you’ve done, but ensure there are no typos or formatting issues in your payload.

  4. API Version and Endpoint: Check that you’re using the correct API endpoint and the latest API version. Compatibility issues could cause unexpected behavior.

If everything appears correct but the issue persists, you can enable API logging in DocuSign and review the logs to identify what might be going wrong. Logs often provide valuable insights into missing configurations or invalid data.

Reply


Code of Conduct

Docusign Community

Code of Conduct