Changelog

The only difference between authenticating with the Click API and the eSignature API is that when you request an access token for your OAuth2 scenario, you must request a special Click API scope during the authentication process. The click.sign scope enables completing clickwrap agreements from within an application.

Added support for version v2.1-20.3.00 of the Docusign eSignature API and updated the SDK release version. We’ve also fixed a bug with ApiClient SetBasePath which did not update basePath for RestClient.

Custom tabs now support additional tab properties that allow a tab to be shared or edited by all recipients in the envelope: ‘collaborative,’ ‘requireAll,’ and ‘requireInitialOnSharedChange.’ These properties are supported when creating the custom tab using the API, and when creating a recipient tab from a custom tab using the API, and are equivalent to the same properties supported within recipient tabs.Setting ‘collaborative’ to true enables collaboration. Setting ‘requireInitialOnSharedChange’ to true will route the envelope back to recipients who have already completed signing if a collaborative field is changed by a signer who appears later in the routing order.

Introducing Full API support for conditional recipients enabling developers to customize the routing logic for envelope creation.