Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring basic authentication details for DocuSign envelope requests

Updated on April 6, 2022

Although OAuth 2.0 is a more robust and secure authentication method for your DocuSign API calls, you can use basic authentication for development environments or proof-of-concept use case scenarios because this method requires less configuration.

Before you begin:
  • For the authentication configuration in this data transform to take effect, ensure that the Value field for the target production level in the pyDocuSignauthProfile application setting is empty. For more information, see Updating the DocuSign connection details.
    Important: If you selected an Oath 2.0 authentication profile instance in the pyDocuSignAuthProfile application setting, then that configuration takes precedence over the settings for basic authentication.
  • Save the pySetEnvelopeCredentials data transform rule as part of your application ruleset, in the case type class that integrates the DocuSign services.
  • Ensure that step 2.2 in the pyPrepareNewEnvelope data transform is enabled. For more information, see Preparing a DocuSign envelope.
  1. Find and open the pySetEnvelopeCredentials data transform.
  2. In step 2 of the data transform, set the .pyRequest.pyXDSAuth property value equal to the following expression:
    "{\"Username\": \"your_docusign_username\",\"Password\": \"your_docusign_password\",\"IntegratorKey\":\"your_integration_key\"}"
  3. If you are not using a void envelope flow, disable step 3 of the data transform.
  4. Confirm your settings by clicking Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us