If you want to embed the DocuSign esigning experience into your application, your web service calls to DocuSign API will require a tighter level of security. In addition to the user name token in the SOAP headers, you will need to provide an X509 signature. For an example of a SOAP call [...]

A lot of business applications today are starting to use commercial web services. The ubiquity of connectivity allows us to move mission critical business processes outside of our internal firewalls to cut down on maintenance, increase reliability, create more feature rich applications and get instant updates.

Whether or not your application is installed or delivered as a service, integration with web services such as the ones delivered by DocuSign requires a shift in user interface, support and architecture.

The cost of adopting the new paradigms are often less then the benefits you receive by utilizing the services oriented architecture (SOA). In this post we will examine the benefits, architecture considerations, implementation guidelines and support for an application integrated with DocuSign web services.

The target audience of this post are enterprise software architects and technical project managers that are designing an integration with DocuSign web services.