Trending Topics: Latest from our forums (November 2024)

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of November 2024. To make sure we see your questions on Stack Overflow, use the tag docusignapi.

Thread: Docusign envelopesApi.ListDocuments failing with a valid header and settings

https://stackoverflow.com/questions/79208251/docusign-envelopesapi-listdocuments-failing-with-a-valid-header-and-settings

Summary: The developer is trying to call the EnvelopeDocuments: list endpoint through the C# SDK in the production environment and getting the following error: 

PARTNER_AUTHENTICATION_FAILED The specified Integrator Key was not found or is disabled. An Integrator key was not specified

When they try to call the same endpoint in the demo environment, it’s working for them.

Answer: This error was appearing because the developer was authenticating with a production integration key while still making API calls using the base path for the demo environment. The SDK defaults to using the demo base paths, and that needs to be updated when making API calls in the production environment. To find the correct base path for the production environment, you can call the user info endpoint.

Thread: Docusign Checkbox model

https://community.docusign.com/sdks-71/docusign-checkbox-model-21435

Summary: This developer is creating a document with checkbox tabs that allow the user to select “Yes” or “No.” They only want to allow the developer to select one checkbox and would prefer not to use radio groups. 

Answer: You can enforce rules around how many checkboxes a recipient can select by grouping the checkboxes in a tab group. The groupRule property is used to set a rule for the tab group, and the minimumRequired and maximumAllowed properties determine how that rule is applied. In this case you would set the group rule to SelectExactly, which means that the recipient is required to select an exact number of checkboxes. The values of minimumRequired and maximumAllowed further specify that the recipient must select no more and no less than one checkbox.

The snippet below demonstrates how to do this with the C# SDK.

Checkbox checkbox1 = new Checkbox
{
    TabLabel = "LionTab",
    DocumentId = "1",
    PageNumber = "1",
    RecipientId = "1",
    XPosition = "200",
    YPosition = "300",
    TabGroupLabels = new List<string>
    {
        "checkboxgroup1"
    }
};
Checkbox checkbox2 = new Checkbox
{
    TabLabel = "TigerTab",
    DocumentId = "1",
    PageNumber = "1",
    RecipientId = "1",
    XPosition = "220",
    YPosition = "300",
    TabGroupLabels = new List<string>
    {
        "checkboxgroup1"
    }
};
TabGroup checkboxTabGroup = new TabGroup
{
    GroupLabel = "checkboxgroup1",
    ValidationMessage = "Please check a box",
    GroupRule = "SelectExactly",
    MinimumRequired = "1",
    MaximumAllowed = "1",
    RecipientId = "1",
    DocumentId = "1",
    PageNumber = "1",
    XPosition = "0",
    YPosition = "0",
    TabScope = "Document", // or "envelope"
    TabType = "tabgroup"
};

Tabs signer1Tabs = new Tabs
{
    SignHereTabs = new List<SignHere> { signHere1 },
    CheckboxTabs = new List<Checkbox> { checkbox1, checkbox2 },
    TabGroups = new List<TabGroup> { checkboxTabGroup }
};

signer1.Tabs = signer1Tabs;

Thread: Creating an "InPersonSigner" and struggling with UNKNOWN_ENVELOPE_RECIPIENT

https://community.docusign.com/embedded-signing-68/creating-an-inpersonsigner-and-struggling-with-unknown-envelope-recipient-21547

Summary: The developer is trying to create an envelope with an in person signer. When they create the recipient view, they are seeing the following error:

UNKNOWN_ENVELOPE_RECIPIENT The recipient you have identified is not a valid recipient of the specified envelope.

Answer: This error indicates that the recipient information in the request body of the EnvelopeViews: createRecipient endpoint does not match the recipient information in the request body of the Envelopes: create endpoint. If there is a mismatch in the userName, email, or clientUserId properties across those two request bodies, it will result in an error. In this developer’s case, they had included the clientUserId when creating the recipient view but they had not included it in their envelope definition; so they could resolve this by removing the property from the recipient view request body or adding the property to the create envelope request body. 

Additional resources

• Docusign Developer Center

• Docusign Developers Community

• @DocusignDevs on X

• Docusign for Developers on LinkedIn

• Docusign for Developers on YouTube

• Docusign Developer Newsletter