From bf638829b580acf98f5c88947624a59a7c2b869f Mon Sep 17 00:00:00 2001 From: Luisina Santos Date: Thu, 27 Aug 2026 17:19:45 -0300 Subject: [PATCH 1/3] docs: document C1 redirect URI and integration key classification Setup docs told every reader to enter an arbitrary redirect URI, which only works for the self-hosted flow. Cloud-hosted (demo environment) setups need C1's actual OAuth callback registered on the DocuSign app or the authorization request is rejected. The integration key classification choice, which affects billing and can't be changed later, also had no guidance. --- docs/connector.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/connector.mdx b/docs/connector.mdx index 5959b622..abe833be 100644 --- a/docs/connector.mdx +++ b/docs/connector.mdx @@ -60,12 +60,18 @@ A user with access to the **Docusign Admin console** must perform this task. On the app configuration screen, carefully copy and save the **Client ID** (also called an integration key). + + You'll be asked to classify the integration key. This choice affects production billing and [can't be changed later](https://developers.docusign.com/platform/go-live/#ik-classifications): + - Choose **Private custom integration** if this app will only be used internally by your organization — the typical case for a self-hosted connector. + - Choose **Third-party integration key** if you're using this app with C1's **Custom App (Demo Environment)** field group and connecting third-party (C1) infrastructure to your DocuSign account. Click **Add Secret Key**, then carefully copy and save the client secret. - In the **Redirect URI** field, enter any URI of your choice (such as http://example.com/callback) and click **Add**. + In the **Redirect URI** field: + - If you're configuring a **self-hosted** connector, enter any URI of your choice (such as http://example.com/callback) and click **Add**. The `--configure` flow prints an authorization URL and reads the resulting code from the terminal — it never receives a redirect, so this value is never actually used. + - If you're configuring a **Cloud-hosted (demo environment)** connector, enter `https://accounts.conductor.one/oauth/callback` and click **Add**. C1 completes the OAuth flow through this URL; DocuSign rejects the authorization request if it isn't registered here. Under **Authentication**, enable **Authorization Code Grant**. From f544efc00e378c221c5a102a4c0a5df9e763d7dc Mon Sep 17 00:00:00 2001 From: Luisina Santos Date: Fri, 28 Aug 2026 11:52:40 -0300 Subject: [PATCH 2/3] docs: fix inaccurate claim about self-hosted redirect URI MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The self-hosted redirect URI is not unused — DocuSign does redirect the browser there and sends it as redirect_uri in the token exchange, so the registered value must match --redirect-uri/BATON_REDIRECT_URI. --- docs/connector.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/connector.mdx b/docs/connector.mdx index abe833be..58bfd085 100644 --- a/docs/connector.mdx +++ b/docs/connector.mdx @@ -70,7 +70,7 @@ A user with access to the **Docusign Admin console** must perform this task. In the **Redirect URI** field: - - If you're configuring a **self-hosted** connector, enter any URI of your choice (such as http://example.com/callback) and click **Add**. The `--configure` flow prints an authorization URL and reads the resulting code from the terminal — it never receives a redirect, so this value is never actually used. + - If you're configuring a **self-hosted** connector, enter any URI of your choice (such as http://example.com/callback) and click **Add**. Nothing needs to be listening at that address — the `--configure` flow prints an authorization URL, and after you authorize, DocuSign redirects your browser there; copy the `code` parameter from the resulting (unreachable) URL and paste it when prompted. Whatever value you register here must also be passed as `--redirect-uri` / `BATON_REDIRECT_URI`, or the authorization and token exchange will fail. - If you're configuring a **Cloud-hosted (demo environment)** connector, enter `https://accounts.conductor.one/oauth/callback` and click **Add**. C1 completes the OAuth flow through this URL; DocuSign rejects the authorization request if it isn't registered here. From 8e68a992a56c96d3d14abbecfcc822d9ca2ba48b Mon Sep 17 00:00:00 2001 From: Luisina Santos Date: Fri, 28 Aug 2026 15:33:40 -0300 Subject: [PATCH 3/3] docs: soften integration key classification guidance The prior wording split the classification choice cleanly by hosting mode, but DocuSign's classification is about who owns/distributes the app, not who runs the connector -- the key is created and used against the customer's own account in both cases. State it as DocuSign's own criteria plus a case worth double-checking, not a rule. --- docs/connector.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/connector.mdx b/docs/connector.mdx index 58bfd085..e42cd073 100644 --- a/docs/connector.mdx +++ b/docs/connector.mdx @@ -61,9 +61,7 @@ A user with access to the **Docusign Admin console** must perform this task. On the app configuration screen, carefully copy and save the **Client ID** (also called an integration key). - You'll be asked to classify the integration key. This choice affects production billing and [can't be changed later](https://developers.docusign.com/platform/go-live/#ik-classifications): - - Choose **Private custom integration** if this app will only be used internally by your organization — the typical case for a self-hosted connector. - - Choose **Third-party integration key** if you're using this app with C1's **Custom App (Demo Environment)** field group and connecting third-party (C1) infrastructure to your DocuSign account. + You'll be asked to classify the integration key. This choice affects production billing and [can't be changed later](https://developers.docusign.com/platform/go-live/#ik-classifications). The key is created and used against your own DocuSign account in both hosting modes, so **Private custom integration** — DocuSign's description is *"used internally by your employees or your customers' employees"* — matches most setups. If you're going through C1's **Custom App (Demo Environment)** field group, you may instead consider **Third-party integration key** — *"using a partner integration that requires your own integration key"* — since C1 is the party invoking it on your behalf; confirm with DocuSign which classification fits your situation before proceeding, since it isn't reversible. Click **Add Secret Key**, then carefully copy and save the client secret.