> 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

# Your Extension App Starter Kit

> Explore Docusign API capabilities and ISV Embed program features, create your proof of concept, and accelerate your ISV embed solution development.

# Your Extension App Starter Kit

## Kit Contents

### Get Started

Use the tools and resources in this kit to discover extension app features such as extension types, extension points, and actions. Then, get started building your own extension apps.

### Contents

#### [Extension Apps Documentation](/extension-apps)

Get familiar with extension types, extension points, and actions. Then see how extension apps are used to extend workflows by interacting with external services.

#### [Sample Implementation](/tools/reference-implementations)

See sample reference implementations that demonstrate how to implement and use various types of extension apps.

#### [Extension Apps Glossary](/extension-apps/glossary)

Get definitions for core elements of extension apps to better understand how to use them in your development projects.

#### [Extension App Schema Reference](/extension-apps/extension-app-reference)

Extension apps use a JSON manifest file and the schema reference is useful to customize the manifest file.

Follow these steps to launch your own extension apps project.

1. **Sign up for a developer account**
   If you haven’t already got one, sign up for your FREE [developer account](https://www.docusign.com/developers/sandbox?postActivateUrl=https://developers.docusign.com/&_gl=1*1d3gman*_gcl_au*ODczOTUxNTUwLjE3MjcyOTgwNDc.). The developer account gives you full access to build and test your integrations in our developer environment.
2. **Read the extension apps documentation**
   Review the [Extension apps](/extension-apps) documentation to determine the type of extension app you would like to build. Also, make an assessment of whether your app will be [public or private](/extension-apps/extension-apps-101/choosing-private-distribution) .
3. **Access the Developer Console**
   Go to the [Developer Console](https://devconsole.docusign.com) to create your first extension app. You can use the form based approach or directly customize the sample JSON manifest file.
4. **Assess whether an API Proxy is required**
   An API proxy serves as an intermediary between a Docusign extension app and an external API service, transforming requests and responses to the required formats. If the API’s requests and responses meet the Docusign specifications, you will not need to build and host an API proxy. See [Use an API proxy](/extension-apps/build-an-extension-app/it-infrastructure/api-proxy) to learn more.
5. **Test your extension app**
   Make sure you [test your extension app](/extension-apps/build-an-extension-app/test) on both the demo and production environments ensure that the extension app is working as expected.
6. **Submit for review and publish**
   After you have tested your app, [submit your app for review](/extension-apps/build-an-extension-app/publish). Once it's approved, the app can be published on the App center (public app) or shared with other private accounts (private app).
7. **Monitor usage**
   Once the app has been published or shared, you can monitor the App Dashboard within the Developer Console to view usage metrics. This feature is currently available in beta.
8. **Ask the community**
   If you have any questions as you build, please feel free to ask the [Docusign Developer Community](https://community.docusign.com/developer-59). You can also join the [API Office Hours](/developer-events) for a demo and live Q and A for additional information.

Has this Starter Kit been helpful? Let us know what you think! Take our quick [survey](https://docusign.co1.qualtrics.com/jfe/form/SV_0lDgnZEACCwuDBk)