> 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 # Register an extension app > Learn how to supply Docusign with technical and descriptive information about an extension app. When you register an extension app in the [Developer Console](/extension-apps/developer-console-overview), you configure parameters that determine how the app functions as well as metadata that describes the app. These settings include: * The [extensions](/extension-apps/extension-apps-101/supported-extensions) the extension app uses * Parameters required to obtain [authorization](/extension-apps/build-an-extension-app/it-infrastructure/authorization) and connect to external API endpoints * The distribution type: [public or private](/extension-apps/extension-apps-101/choosing-private-distribution) * The description, icon, screenshots, and other details that appear in the extension app's [Docusign App Center](/extension-apps/extension-apps-101/app-center) listing You have two options for app registration: * [Use a guided form-based UI](/extension-apps/build-an-extension-app/register/use-form): This process enables you to register an extension app by filling out fields in the Developer Console. * [Use an app manifest file](/extension-apps/build-an-extension-app/register/use-manifest): In this process, you register the extension app by populating values in a JSON file that you upload or paste into the Developer Console app manifest editor. ## Form-based and app manifest method comparison This table shows which extension app registration method is more useful in various scenarios. | If you want to | Select this method | Because | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Register an extension app using the easiest method | Form-based | This method presents all required fields in a user-friendly UI and guides you through the process of populating the fields. | | Spend less time troubleshooting | Form-based | This method ensures that you can only supply valid values for extension app settings, and it automatically populates some values to reduce the risk of errors. | | Enable non-technical users in your organization to define App Center listing details | Form-based | The Developer Console has a dedicated page where the description, icon, screenshots, and other App Center listing details can be defined, and it's separate from the technical settings related to authorization and API endpoints. | | Register a new extension app by copying an existing app's details | App manifest file | This method enables you to download the app manifest file for an existing extension app, modify it, and register a new extension app by uploading the modified file. | | Update multiple settings via a search and replace | App manifest file | This method enables you to quickly replace multiple values either directly in the app manifest editor or by downloading the manifest, replacing values, and uploading the new version. | | Test an extension app using a [reference implementation](https://www.docusign.com/blog/developers/fast-track-your-extension-apps-with-reference-implementations) that Docusign provides on GitHub | App manifest file | The GitHub repos include preconfigured manifest files that require only minor modifications to work with a local copy of a reference implementation. You can upload your modified file to register a sample extension app that enables you to test with the reference implementation. | ## Manifest is created regardless of registration method When you register an extension app via a form, the Developer Console saves the app details in a manifest file. You can update app details by editing this file or using the form-based UI. Similarly, extension apps registered via a manifest file can be updated through either the form-based UI or by editing the manifest file directly. See [Update an extension app registration](/extension-apps/build-an-extension-app/update-registration) for details about how to use each method. ## Prerequisites for registering an extension app These prerequisites apply for both the form-based and app manifest file methods for registering an extension app: * You will need a Docusign [developer account](https://www.docusign.com/developers/sandbox) with admin privileges. * If your app will use external API service endpoints that don’t conform to the Docusign [Action schema](/extension-apps/extension-app-reference/app-manifest-reference/action), you may need to set up an [API proxy](/extension-apps/build-an-extension-app/it-infrastructure/api-proxy) to translate the external API’s requests and responses to the format that Docusign expects. * You will need to obtain the external service, identity provider, and API proxy information that you will need to configure your extension app. This includes endpoint URLs, [authorization](/extension-apps/build-an-extension-app/it-infrastructure/authorization) details, and required parameters in requests to the endpoints and in the responses. ## Next steps * Learn how to register an extension app [using a form](/extension-apps/build-an-extension-app/register/use-form). * Find out how to register an extension app [using an app manifest file](/extension-apps/build-an-extension-app/register/use-manifest). * Review the options for [updating extension app registration details](/extension-apps/build-an-extension-app/update-registration). > Learn how to supply Docusign with technical and descriptive information about an extension app. ## Docs - [Use a form to register an extension app](https://developers.docusign.com/extension-apps/build-an-extension-app/register/use-form.md): Learn how to register an extension app using a guided form-based UI. - [Update integration details](https://developers.docusign.com/extension-apps/build-an-extension-app/register/use-form/integration-details.md): Learn how to define extension app settings required to obtain authorization and connect to endpoints in the external API service. - [Update App Center listing](https://developers.docusign.com/extension-apps/build-an-extension-app/register/use-form/app-center-listing.md): Learn how to define the text and images that appear in an extension app listing in the Docusign App Center. - [Use a manifest file to register an extension app](https://developers.docusign.com/extension-apps/build-an-extension-app/register/use-manifest.md): This guide describes the steps for registering an extension app by building a JSON app manifest file.