> 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 # ISV integration guides > As a Docusign partner, see how to plan and design your integration. The steps and requirements for planning your integration differ depending on how you partner with Docusign. For help determining which type of partner content you need, see [What type of partner are you?](/partner/partner-implementation-overview#what-type-of-partner-are-you) #### Option 1. ISV General Connector eSignature integration guide #### This option is recommended if: * Your company’s business app will connect using its customer’s Docusign account * You do not wish to purchase from Docusign * You want to only integrate and let your customers buy from Docusign * You do not want to incur any cost * You already have customers using Docusign #### Integration steps **Step 1 : Set up your account** Set up your account and familiarize yourself with the Docusign platform. **Step 2: Review and choose the authentication method** Most Docusign APIs are sessionless and require an access token for each call. You can obtain an access token using one of the supported OAuth flows. **Step 3: Envelope creation and sending strategy** Learn about recommendations and best practices around envelope creation and sending strategy. **Step 4: Envelope signing** Depending on how your signers will sign documents, you should use either remote or embedded signing. **Step 5: Envelope notifications** See recommendations and best practices around getting status notifications. [View guide](/partner/isv-connector-implementation) #### Option 2. ISV Embed eSignature integration guide #### This option is recommended if: * Your company's business app will embed Docusign eSignature as a service within your product * Your company will buy from Docusign, will redistribute Docusign transactions on behalf of its clients #### Integration steps **Step 1 : Manage Docusign accounts** Set up your account and familiarize yourself with the Docusign platform. **Step 2: Review and choose the authentication method** Most Docusign APIs are sessionless and require an access token for each call. You can obtain an access token using one of the supported OAuth flows. **Step 3: Envelope creation and sending strategy** Learn about recommendations and best practices around envelope creation and sending strategy. **Step 4: Envelope signing** Depending on how your signers will sign documents, you should use either remote or embedded signing. **Step 5: Envelope notifications** See recommendations and best practices around getting status notifications. [View guide](/partner/isv-embed-implementation) **Note**: If you are building an enterprise solution, get started using [Quickstart](/docs/esign-rest-api/quickstart) instead. If you are also building an extension app, see [Extension apps overview](/extension-apps) instead. > As a Docusign partner, see how to plan and design your integration. ## Docs - [ISV Connector Implementation Plan](https://developers.docusign.com/partner/isv-connector-implementation.md): Learn the general steps and best practices for building and implementing a Docusign integration as an ISV connector. - [ISV Embed Implementation Plan](https://developers.docusign.com/partner/isv-embed-implementation.md): Learn how to implement and embed Docusign eSignature as a service within your product.