> 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

# Update integration details

> Learn how to define extension app settings required to obtain authorization and connect to endpoints in the external API service.

This procedure enables you to use a form to define settings required to obtain [authorization](/extension-apps/build-an-extension-app/it-infrastructure/authorization) and connect to endpoints in the external API service. Instead of using a form, you can define the settings by [creating](/extension-apps/build-an-extension-app/register/use-manifest) or [updating](/extension-apps/build-an-extension-app/update-registration/use-manifest) a JSON app manifest file.

## Access integrations details for an extension app

To access an extension app’s integration details:

1. Log in to the [Developer Console](https://devconsole.docusign.com).
2. On the **My Extension Apps** page, locate the row for the extension app you want to update.
3. Select the app to open the **Overview** page.
4. In the left navigation, select **Integration Details**.

![Integration details](/_fern-files/_img/191c0a686b5bb6696a80f2df9770cfdba02c48edc47fd05913138a5b6fe2d16a.webp)

If the extension app registration is newly created, define both the [connection settings](/extension-apps/build-an-extension-app/register/use-form/integration-details#update-connection-settings) and the [extension and action settings](/extension-apps/build-an-extension-app/register/use-form/integration-details#update-extension-and-action-settings).

If you are updating an existing extension app registration, you can modify only the settings you want to change.

## Update connection settings

[Connection](/extension-apps/extension-apps-101/concepts/connections) settings enable an extension app to obtain authorization from the external API service or identity provider.

To update an extension app’s connection settings:

1. [Access the Integration Details page](/extension-apps/build-an-extension-app/register/use-form/integration-details#access-integrations-details-for-an-extension-app).
2. Under **Connection**, select **Edit**.
3. Enter or update these values:

   ![Connection name and description](/_fern-files/_img/107bc71205e8994c4fe2573e46555e094e075163f2b8e4f45872d9bab7c4b6d9.webp)

   1. **Connection name.** The name of the connection. This value must be unique. This name will appear in these locations: the Developer Console [integration tests](/extension-apps/build-an-extension-app/test/integration-tests) page; the Docusign App Center page where users [install and connect](https://support.docusign.com/s/document-item?bundleId=ous1698169987748\&topicId=ctg1698170340729.html) your extension app; and the Workflow Builder workflow step configuration page, for extensions that can be used in a workflow.
   2. **Description.** A description for the connection.

      ![Scopes, Client ID, Client Secret](/_fern-files/_img/6dd4bcaa49e411a7096151482fd8e2bd035147c80306d5643d81c82be5b0db09.webp)
   3. **Scopes.** Any scopes that are required for authorization. See [Scopes](/extension-apps/build-an-extension-app/it-infrastructure/authorization#scopes) for more information. If you are supplying more than one scope, separate them with spaces.
   4. **Client ID.** The client ID that is required for [authorization](/extension-apps/build-an-extension-app/it-infrastructure/authorization) with the external platform.
   5. **Client secret.** The client secret that is required for authorization with the external platform.

      ![Authorization URL, Token URL, Authorization Method](/_fern-files/_img/0fd902bd8e51cfe238ea82027856d43b6676b434916b7068ff96fed3f63cabb3.webp)
   6. **Authorization URL.** The OAuth 2.0 authorization endpoint. When the Docusign platform makes a request to this endpoint, the external service returns an authorization code. The URL’s top-level domain must be one of the following: `.com`, `.net`, `.org`, `.app`, or `.cloud`. Do not include `docusign.` in the domain. If the OAuth 2.0 grant type is Client Credentials, this setting does not appear.
   7. **Token URL.** The OAuth 2.0 token endpoint. When the Docusign platform provides an authorization code in a request to this endpoint, the external service returns an access token that will be included in all subsequent API requests from the extension app to the external service.
   8. **Authorization method.** If you set this value to **header**, when Docusign makes a request to the authorization URL, the client ID and client secret will be sent in the request header. If you set this to **body**, they will be sent in the request body.

      ![Auth Params](/_fern-files/_img/ed06219fb862717b6f804201556f8f87a255a7305ef5ac90b718b5ff91260ae5.webp)
   9. **Auth params.** A set of query parameters required for the authorization URL. If the OAuth 2.0 grant type is Client Credentials, this setting does not appear.
4. Select **Save**.
5. If prompted, re-enter the client secret and select **Save**.

## Update extension and action settings

> **Note**
>
> For the [file IO extensions](/extension-apps/extension-apps-101/supported-extensions), you can add or remove [capabilities](/extension-apps/extension-apps-101/concepts/capabilities) only by [editing the app manifest file](/extension-apps/build-an-extension-app/update-registration/use-manifest). After you've added capabilities via the manifest file, you can edit them on the Integration Details page.

[Extension](/extension-apps/extension-apps-101/concepts/extensions-and-extension-points) and [action](/extension-apps/extension-apps-101/concepts/actions) settings determine which functionality the extension app offers, such as importing files from or writing files to cloud storage, reading data from or writing it to a system of record, or verifying customer information such as a bank account. These settings also provide the information that the Docusign platform uses to send requests to the external API endpoints that provide this functionality.

To update an extension app’s extension and action settings:

1. [Access the Integration Details page](/extension-apps/build-an-extension-app/register/use-form/integration-details#access-integrations-details-for-an-extension-app).
2. Under **Extensions & Actions**, locate the extension whose settings you want to define.
3. Select **Edit**.
4. Enter or update these values:

   ![Extension Name and Description](/_fern-files/_img/0e62cce8e612655cd3992a160b182d8a040a1842fb0cb96558c21c2076da24b2.webp)

   1. **Extension name.** A name for the extension. For file input cloud storage extensions, the name will appear in a list of document sources on the Agreement Manager **Upload Documents** window. For file output cloud storage and file output system of record extensions, the name will appear on the Workflow Builder workflow step selection and step configuration screens.
   2. **Description.** A description for the extension. For file output cloud storage, file output system of record, and data IO extensions, this description will appear on the Workflow Builder workflow step selection screen.
5. For each of the extension's actions, enter or update these values:

   ![Action Name, Description, URI](/_fern-files/_img/919982e6453f507d2a30ebbde77f4f6275f6cd20a3d7fd2aee0dcc48aa5154e7.webp)

   1. **Name.** A name for the action. This name will appear on the Developer Console [integration tests](/extension-apps/build-an-extension-app/test/integration-tests) page. For file IO extensions, the name is not editable.
   2. **Description.** A description for the action.
   3. **Params URI.** The URI of the external API endpoint that will be called by the action.
6. Select **Save**.

## Add an extension

To add an extension to an extension app registration:

1. [Access the Integration Details page](/extension-apps/build-an-extension-app/register/use-form/integration-details#access-integrations-details-for-an-extension-app).
2. Under **Extensions & Actions**, select **Add Extension**.

   ![Add an extension](/_fern-files/_img/d2d8ff5215c0c16d0fdf1935d62f667918f20d3ebe745776327f68528b10d341.webp)
3. Select an extension type and select **Next**. For information about the available types and the associated extensions, see [Supported extensions](/extension-apps/extension-apps-101/supported-extensions).
4. Depending on the extension type you select, you may be presented with additional choices. For example, these choices are available for data IO:

   ![Data IO types](/_fern-files/_img/5ead6a5d784e5a6459039a96fb544f7fd2067b6310af535ee141c7d69b90189a.webp)

   Make a selection, and select **Finish**.
5. Populate the extension and action values. See [Update extension and action settings](/extension-apps/build-an-extension-app/register/use-form/integration-details#update-extension-and-action-settings) for descriptions of the values.
6. Select **Save**.

## Delete an extension

To delete an extension from an extension app registration:

1. [Access the Integration Details page](/extension-apps/build-an-extension-app/register/use-form/integration-details#access-integrations-details-for-an-extension-app).
2. Under **Extensions & Actions**, locate the extension you want to remove.
3. Select **Delete**.
4. Select **Delete** on the confirmation window.

## Next steps

* Review the procedure to [update the App Center listing](/extension-apps/build-an-extension-app/register/use-form/app-center-listing) for an extension app.
* See how to update an extension app registration by [editing the app manifest file](/extension-apps/build-an-extension-app/update-registration/use-manifest).