> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # Code example launchers > Describes what code launcher projects are, and how to access the launchers for various programming languages. [Code example launchers](https://developers.docusign.com/tools/code-example-launchers) are complete projects that show common API integration functions. They enable you to see how to make API and SDK calls, how the code fits into an application, and how that code runs. You can freely clone, download, and run the launchers from the [Docusign GitHub](https://github.com/docusign). They are available in all of our supported SDK programming languages: C#, Java, Node.js, PHP, Python, and Ruby. Each launcher accesses Docusign APIs through the objects and methods available in its own language’s SDK. If you’d like to access the raw API (not with an SDK), we also have launchers available in Bash and PowerShell. Code launchers provide a web UI that runs locally and enables you to explore and run your desired code example by choosing the appropriate link. Use code example launchers to: * Develop your own integration, using the example as a model * Learn best practices for implementing a scenario * See how [Docusign authentication](/docs/rooms-api/rooms101/auth) works within a sample app ## Examples and languages Each launcher has its own installation instructions, dependencies, and prerequisites. The README file for each launcher contains the specific details: * [Bash](https://github.com/docusign/code-examples-bash) * [C#](https://github.com/docusign/code-examples-csharp) * [Java](https://github.com/docusign/code-examples-java) * [Node.js](https://github.com/docusign/code-examples-node) * [PHP](https://github.com/docusign/code-examples-php) * [PowerShell](https://github.com/docusign/code-examples-powershell) * [Python](https://github.com/docusign/code-examples-python) * [Ruby](https://github.com/docusign/code-examples-ruby) ## Generate test data When executing Monitor API code examples, it’s useful to have test data in your developer account so that the responses contain realistic values. You can use the [MyAPICalls](https://myapicalls.sampleapps.docusign.com/) sample app to generate this test data. MyAPICalls has a collection of *scenarios,* or use cases, each of which includes a series of API requests. Executing a scenario once will generate one or more [tracked events](https://support.docusign.com/s/document-item?bundleId=gso1581445176035\&topicId=crj1659119600990.html) that you can then retrieve using Monitor API requests. You can also configure MyAPICalls to run a scenario repeatedly using unique data each time, enabling you to quickly load a large volume of data into your developer account. This is helpful for testing and demonstrating dashboards that you’ve built with Monitor API calls. MyAPICalls sends API requests to the developer (demo) environment, not production. Below is a list of MyAPICalls scenarios, and the tracked events that each one generates. To run any of the scenarios listed below, you can either access the scenario page directly via the link in the **Scenario** column, or you can visit the [MyAPICalls](https://myapicalls.sampleapps.docusign.com/) home page and select **Try scenario** for any scenario in the list. See the **Running the sample** panel on the scenario page for execution instructions. > **Note:** The envelope signed event will be generated only if you complete the signing process for the envelope that the scenario creates. | Scenario | Events generated | | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | [Remote Signing with Template](https://myapicalls.sampleapps.docusign.com/scenario/1) | Template created Envelope created Envelope sent Envelope signed | | [Embedded Signing](https://myapicalls.sampleapps.docusign.com/scenario/2) | Envelope created Envelope sent Envelope signed | | [Responsive Signing](https://myapicalls.sampleapps.docusign.com/scenario/4) | Envelope created Envelope sent Envelope signed | | [Phone Authentication](https://myapicalls.sampleapps.docusign.com/scenario/5) | Envelope created Envelope sent Envelope signed | | [Create Connect Configuration and Receive Envelope Event](https://myapicalls.sampleapps.docusign.com/scenario/6) | Connect configuration created Envelope created Envelope sent Connect event sent Envelope signed | | [Add a User](https://myapicalls.sampleapps.docusign.com/scenario/7) | Organization member added | | [Composite Templates: Custom Forms with Shared Signature Document](https://myapicalls.sampleapps.docusign.com/scenario/9) | Template created Envelope created Envelope sent Envelope signed |