Skip to main content

DocuSign OAuth setup guide (Ciphr integration)

Steve
Updated
hr-step_4.svg

This guide walks you through how to connect your DocuSign account to Ciphr using secure OAuth authentication.

We use a method called JWT (JSON Web Token), which allows authorised users in Ciphr to send documents via DocuSign on behalf of an admin user. This is secure and fully approved by DocuSign.

Use this guide if you are:

  • Setting up DocuSign integration for the first time
  • Moving from demo (sandbox) to live (production)
  • Switching from the old username/password method
  • Reconnecting after an admin user has been removed or access was revoked

Contents

 

Stage 1: Create a DocuSign integration key

Preparation

  1. Create a simple text file to store details as you go.
  2. Decide which environment you are using:
    • Demo (sandbox): account-d.docusign.com
    • Live (production): account.docusign.com

Steps

  1. Log in to DocuSign as an admin user
  2. Go to Settings → Integrations → Apps and Keys
  3. Copy and save:
    • User ID
    • API Account ID
  4. Click “Add App and Integration Key”
  5. Give your integration a name

Configure the integration

  • Copy the Integration Key into your file
  • Click “Generate RSA”
    • Copy both the Public and Private keys
    • ⚠️ These will not be shown again after closing
  • Under Additional Settings:
    • Add a Redirect URI (e.g. https://www.google.com)
    • Save this URL—you’ll need it later
    • Click Save

 

Stage 2: Grant user consent

This step allows Ciphr to securely send documents via DocuSign on your behalf.

Steps

  1. Build the following URL using your saved values:
https://<OAuth URL>/oauth/auth?response_type=code&scope=signature%20impersonation
&client_id=<Integration Key>
&redirect_uri=<Redirect URI>
  1. Paste the URL into your browser
  2. Log in to DocuSign (as the admin user)
  3. Click Allow / Consent
  4. Once completed - send your saved details securely to Ciphr Customer Care using your SFTP account.  Include the following:
  • OAuth URL
  • User ID
  • Integration Key
  • Public RSA Key
  • Private RSA Key
  • API Account ID

 

Stage 3: Testing the integration

Before going live, DocuSign requires successful testing.

Steps

  1. Send a test letter from Ciphr
  2. Confirm it is received successfully
  3. Check DocuSign for any errors

✅ If successful:

  • Send at least 20 test documents
  • Ask your DocuSign admin to submit the integration for Go Live review

❗ If there are issues:

 

Stage 4: Go live (production setup)

If you started in demo, you’ll need to repeat parts of the setup for production (your live site).

Key differences

  • OAuth URL becomes: account.docusign.com
  • New keys and IDs must be generated

Steps

  1. Log in to production DocuSign
  2. Go to Apps and Keys
  3. Locate your existing Integration Key
  4. Generate (or confirm):
    • RSA key pair
    • Redirect URI
  5. Save everything again in a new file:
    • OAuth URL
    • Integration Key
    • Public/Private Keys
    • User ID
    • API Account ID
  6. Repeat the consent step using the production URL
  7. Send these updated details to Ciphr Customer Care via SFTP

 

Stage 5: Changing the authorised user

If the original admin user leaves or access is removed:

Steps

  1. Log in to DocuSign with a new admin account
  2. Go to Apps and Keys
  3. Find your integration
  4. Copy:
    • User ID
    • Integration Key
    • Redirect URI
  5. Recreate and open the consent URL (as in Stage 2)
  6. Log in and approve access
  7. Send the new User ID to Ciphr Customer Care

 

Footer

 

Comments

0 comments

Article is closed for comments.