WordPress - DocuSign integration

Summary: The offeror requires code to accomplish a server-side integration between their WordPress instance and the DocuSign RESTful web-services, using DocuSign’s published API. The website uses WordPress version 5.8.3, packaged by Bitnami, with around a dozen plugins, running on an AWS LightSail instance (EC2, Debian instance). Data storage is provided by an on-instance MySql (10.3.31) with plans to migrate this to RDS in the near-future. A comparable AWS instance will be provided for the developer to work with. The integration is to occur between the WordPress instance and the published DocuSign eSignature API. Since DocuSign’s webservices are RESTful, any computer language could possibly meet the requirements, however, PHP is preferred as it is used extensively within WordPress. Proposals for other languages to be used will be considered if the bidder makes a convincing case that the code will function cleanly within the WordPress framework. The code must accomplish the following: it will take as the input 10 – 20 http variables, accumulated through a sequence of pages and on submit of a final form, pass them to a DocuSign PowerForm, to populate the form and display the result to the user for a sign-off. Several of these variables will include the names and email addresses of the customer and additional, witness, signers, which may create complications within the DocuSign framework, as the signing sequence will include asynchronous actions by all signing parties. A further requirement is that at each signing event, a PDF version of the document must be returned and saved within the offeror’s MySQL database. Accomplishing this is part of the task, the DocuSign API might not make this easy. The deliverable must function within the WordPress framework, must be installable in an appropriate place within a WordPress instance (ie, an area set aside for custom PHP calls) and ideally should not depend on WordPress plugins. If a plugin is an anticipated element of the solution, the bidder shall let the offeror know as soon as possible for compatibility review. An adequate level of documentation is required for acceptance and the bidder will conduct a code walk-through with the offeror’s CTO, expected to be 90 minutes, but not to exceed 240 minutes.