Building extension apps requires developers to have a sound understanding of HTTP protocols, server-side programming languages (for example, Python or Node.js), cloud hosting platforms, OAuth authorization protocols, and more. They will need to set up a publicly accessible endpoint (URL) to receive incoming extension payloads, parse and process JSON data, and execute actions or workflows. For more information, please read the extension app documentation.

Thanks for posting your question on the Docusign Community!

️ Welcome Scavenger Hunt participants! 

Now that you know about Extension Apps, you may be wondering what technical skills are needed to write your own – see the post above and get started! (BUT, before you do… Clue #3 is below) 

Another recent Docusign launch to help you break out of the Agreement Trap is Maestro Workflows. This lets you build solutions with no-code, powered by the Maestro API. You can leverage the Maestro interface to quickly build & configure complex workflows and invoke them with a single call to the API. Maestro also supports connecting those workflows with Extension Apps, so with or without code, not only can you create your own Docusign workflows, but also connect them with the power of 3rd-party apps & services!

Read and learn more about Maestro in the Maestro API 101 docs.  

Now that you’re becoming an expert, your next question could be: “Can I combine Maestro Workflows with the Maestro API?” (Hint: Find out somewhere on the Maestro API Discussion page.)