> 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 # Docusign Developer AI Assistant for VS Code (Beta) > The Docusign Developer AI Assistant for VS Code provides an AI-powered experience to help developers build integrations. > **Note** > > We’re currently running a beta for the Docusign Developer AI Assistant for VS Code, an AI-powered assistant to help developers generate tokens, orchestrate APIs, configure brands, and resolve integration issues faster. Install the extension from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=DocuSign.docusign-copilot). The Docusign Developer AI Assistant for VS Code provides an AI-powered experience to help developers build integrations. * Developers can ask questions to the extension. The extension includes a [question and answer](/tools/visual-studio-code-extension#docusign-Q-and-A) functionality that responds to Docusign-specific questions. * Developers can use the extension to [get an access token](/tools/visual-studio-code-extension#get-an-access-token) that can be used for [authentication](/platform/auth). * Developers can use this extension to [create or update brand](/tools/ai-assistant-vs-code#update-brand-files-using-vs-code-extension) files in a Docusign account. ## Prerequisites Before you can use the Docusign Developer AI Assistant for VS Code, you will need: * A [GitHub Copilot](https://github.com/features/copilot) license or free trial. * A Docusign developer account. You can [create one](https://www.docusign.com/developers/sandbox) for free at the [Developer Center](/). * [Visual Studio Code](https://code.visualstudio.com/download). Be sure to install the [GitHub Copilot extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) in VS Code. ## Docusign Q\&A To ask a question about Docusign, type `@docusign`, followed by your question, in the Copilot chat window. The Developer AI Assistant can answer questions about Docusign integrations, addressing topics such as authentication and how to use [Docusign SDKs](/docs/sdks) ![A screenshot showing the Copilot chat box](/_fern-files/_img/770b4aef68653e1a3ef330a3be18d3964ea5e52bc1ca7427b4c82862eb77250e.webp) ## Get an access token The Docusign Developer AI Assistant for VS Code can also help developers get started with authentication, automating some of the manual configuration that is usually required when setting up an [Integration key](/platform/configure-app#integration-key) (IK). The Developer AI Assistant streamlines the [process of generating an access token](/platform/auth/confidential-authcode-get-token) and lets you generate a token with the simple `/getAccessToken` slash command. ![A screenshot of the Docusign Copilot extension generating an access token](/_fern-files/_img/fb413da7157b0e54d70f154452b6603d881b3ed7138184a43310c2e890c906b4.webp) To invoke Docusign Developer AI Assistant, use Ctrl+Alt+I on Windows and Cmd+Shift+I on Mac. After logging in, you will be asked to answer some questions to help determine the [authentication type](/platform/auth/choose) that your integration will use. Then the Developer AI Assistant will help you to set up an [integration key](/platform/configure-app#integration-key) (IK). Choose whether you want to generate an IK automatically, receive instructions on how to create an IK in the Docusign Admin UI, or use an existing IK. ![A screenshot of the options displayed by Copilot when creating an integration key.](/_fern-files/_img/b68639e81f91540be0831b69f7491138698befdf1040b413b2ee8d6d3a756d0b.webp) If you choose to generate an IK through the Developer AI Assistant, you will be prompted to enter some information about the new IK. Once the IK has been created, you will see a confirmation like the one below in your chat window. In this example, an RSA key pair was generated for use with JWT authentication. If you choose Authorization Code Grant, the output will look slightly different. ![A screenshot of the RSA key pair generated by Copilot](/_fern-files/_img/5914c8a6e73376a6286ed25c82fff2336778b921698a3376181193c2fb1fa937.webp) The Developer AI Assistant will continue to guide you through granting consent and generating an access token that will appear in the **OUTPUT** tab. You can continue to use the Developer AI Assistant to learn how to use this access token to make calls to Docusign APIs including the [eSignature REST API](/docs/esign-rest-api) and [more](/docs). ![A screenshot of the Docusign Visual Studio Code extension after an access token has been generated](/_fern-files/_img/49f096782d19008d11094ada7d4fe50dc4d5b9d8307950e655af9ab5c743215d.webp) ## Update brand files using VS code extension Docusign administrators can manage their brand details either through the Docusign eSignature admin user interface or the Docusign Developer AI Assistant for VS Code extension. Using the VS Code extension, administrators can create, download, and update brand files directly within the Visual Studio Code. This allows administrators to configure brand settings in Visual Studio Code and easily upload the brand files to their Docusign account. For more details on brand functionalities, see [Brands](https://support.docusign.com/s/document-item?bundleId=pik1583277475390\&topicId=lfr1583277366660.html). > **Note** > > Brand file updates using the VS Code extension are now available in demo environments only. This feature is in beta and not currently available in production. Updating brand files directly in Visual Studio Code provides following benefits: * Streamlines brand files management. * Enables real-time editing, previewing, and verification. * Removes manual file handling and uploading steps in the Docusign eSignature administrator interface. Administrators can access these features using the Docusign Developer AI Assistant for VS Code extension via the command palette (**Ctrl+Shift+P** on Windows/Linux or **Cmd+Shift+P** on macOS). With this extension, administrators can update brand XML files, including email templates, headers, footers, colors, fonts, logos, etc. ## Create a New Brand To create a new brand in your Docusign account using VS Code: 1. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and run **Create Docusign Brand.** ![create docusign brand command](/_fern-files/_img/5d0447d52feb67abc04db110dee0d7d2983bbdcd24134ce4f6f78ca3b0435a1b.webp) 2. If prompted, sign in to your Docusign developer account and select your account. 3. Enter a name for the new brand and press Enter. 4. Choose a location to save the brand files. A success message will appear, and the brand files will open in a new VS Code window. You can also verify the new brand in your eSignature [Admin Brand settings](https://apps-d.docusign.com/admin/brands). ## Download a Brand To download files for an existing brand in your Docusign account using VS Code: 1. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and run **Download Docusign Brand**. ![download-docusign-brand](/_fern-files/_img/9224fb8205ab73758b1c81c8e3c70b5fc656224d55ae4a541e7efa904367fa69.webp) 2. If prompted, sign in to your Docusign developer account and select your account. 3. Select a brand from the list. 4. Choose a folder to save the brand files. The brand files will be downloaded and opened in a new VS Code window, including: * **logo/** - contains brand logos * **resources/ -** contains email templates and other assets. For more information, refer [Docusign Signing Resource File Guide](https://support.docusign.com/s/document-item?language=en_US\&bundleId=docusign-signing-resource-file-guide\&topicId=docusign-signing-resource-file-guide.pdf&_LANG=enus). * **brand.json** - contains brand profile information ## Editing Brand Files After you have downloaded the brand files into your preferred directory, the following file and folder structure will appear in your **VS Code** window: | Path | Description | | --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `/logo` | Contains the brand's logo image files. | | `/resources` | Contains email templates and other assets used for brand customization. | | `/resources/email/mockdata/values.yaml` | Lists the placeholder values used across all email templates. Modifying this file allows you to make global changes to your templates simultaneously during the development process. **Note**: The values defined in this file are used **for local testing and development**. They are not uploaded when updating brand files to the server. To make the changes in the server, use [Admin Brand settings](https://apps-d.docusign.com/admin/brands) page. | | `/resources/email/templates/` | Contains the actual email templates available for editing and previewing. | | `brand.json` | Contains brand’s core metadata, including the brand ID, name, and supported languages. | **Real-Time Previewing** You can view your changes instantly without leaving your workspace. As you edit the files in `/resources/email/templates/`, you can open a **live preview** window directly within VS Code. This allows you to visualize layout adjustments, CSS tweaks, and content changes in real time, ensuring your design is perfect before updating the brand files. ![brand files preview in vs code](/_fern-files/docusign.docs.buildwithfern.com/9d93fff97594367755231c00bb4a7b8a3a9a35d6cde658972d2ae88e9c441ecd/assets/img/ctf/2OUiWYIMurijdPjXVi7uuy-brandFilesPreview.gif) **Dynamic Data & Conditional Logic** The values.yaml file contains the following values: * **Placeholder Values:** Use keys from `values.yaml` to inject dynamic content (like brand names or links) throughout your templates. This ensures consistency and makes global updates at once. * **Conditional Logic:** Uses conditional flags in values.yaml to toggle specific sections of an email based on your brand requirements. For example, the `IsEnvelopeContainingSingleDocument` flag controls grammatical plurality: setting it to **true** displays text in the singular form, while **commenting it out** defaults the text to the plural form. **Note:** To disable a condition, you must **comment out** the line in the values.yaml file. Do **not** simply set the value to False, as the system will not recognize this as a disabled state. ![vs code condition](/_fern-files/_img/57f88c1009bede5c20dfc585714fa617e23cab9781eb0e02ab99785c9ac05adb.webp) ## Updating a Brand **Prerequisite:** Make sure your VS Code workspace contains the latest downloaded brand files from your Docusign account. After editing the brand files, you can either: * Update the brand files in your Docusign account, or * Clone the brand files to create a new copy in your account **Update the brand files folder** To update brand files in your Docusign account: 1. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and run **Update Docusign Brand**. ![update-docusign-brand](/_fern-files/_img/bb1ee70fdff6490d99278ecc059988b7ffd9ad02a52c0b2449fef9d6caeedec8.webp) 2. Select Update \ Files. The extension will: * Combine local brand.json, resources, and logos * Push changes to your Docusign account * Update email templates (only **en-US** is supported) and other resources * Upload XML files and brand logos If successful, a confirmation message appears. You can also verify the new brand in your eSignature [Admin Brand settings](https://apps-d.docusign.com/admin/brands). For validation errors, rectify the error and repeat the commands. **Clone the brand files folder** To save modified brand files as a new brand: 1. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and run **Update Docusign Brand**. ![update-docusign-brand](/_fern-files/_img/bb1ee70fdff6490d99278ecc059988b7ffd9ad02a52c0b2449fef9d6caeedec8.webp) 2. Select Clone and Update \ Files. The extension will: * Combine local brand.json, resources, and logos * Push changes to your Docusign account * Update email templates (only en-US is supported) and other resources * Upload XML files and brand logos * Create a new brand with the name suffixed by \_cloned and download the files to your machine A success message will appear, and the cloned brand files will open in a new VS Code window for editing. ## Try it out Check out the Docusign Developer AI Assistant for VS Code for yourself and try the following use cases: * Let the Developer AI Assistant generate an access token to help you get started with your first API integration. * Ask the Developer AI Assistant which authentication type is right for your use case. * Ask the Developer AI Assistant about Docusign features, APIs, and best practices. It’s your personal guide for quick, accurate answers while you work. * Save time by letting the Developer AI Assistant create the necessary boilerplate code for integrating Docusign APIs in your preferred programming language. ## Next steps * Learn more about [Docusign SDKs](/docs/sdks). * Check out our [Postman collections](/tools/postman). * Explore all of the [tools](/tools/overview) available to help developers build integrations.