Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.iru.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About Docusign

Iru calls the eSignature REST API using OAuth 2.0 JWT Grant: you register an Integration Key (client ID), upload an RSA public key, grant impersonation consent for a service user, and Iru exchanges a signed JWT for access tokens. This suits server-to-server automation without interactive consent each hour.

​
How it works

DetailValue
CategoryE-signatures
AuthenticationOAuth 2.0 JWT Grant
High-level steps: Apps and Keys → create Integration Key → JWT auth → generate or upload RSA → capture Integration Key, impersonated user GUID, account base URI, and private key per Iru’s wizard. Official references: Platform auth, JWT Grant, Build integration, eSignature REST.

​
Prerequisites

  • Administrator access in Docusign.
  • developers.docusign.com access to manage integrations.
  • Clear choice of demo vs production keys and OAuth hosts (account-d.docusign.com vs account.docusign.com).

​
Connect Docusign to Iru

​
Docusign

1

Create an integration key and RSA keys

In Apps and Keys, create an app, enable JWT Grant, Generate RSA (or upload public key), download and vault the private key once.
2

Grant consent once

Open the consent URL Docusign documents for JWT (scopes typically include signature and impersonation), sign in as the user to impersonate, and Allow. Complete any redirect requirements your app registration defines.

​
Iru Compliance

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

Turn on Docusign

Find Docusign (use Category or Search by name or description). On that card, turn on the toggle. A browser tab or window may open for the connector wizard.
3

Enter OAuth and account details

In the wizard, supply the Integration Key, impersonated user ID (GUID), private key, and REST base URI for your account (for example https://na4.docusign.net/restapi). If you are unsure of the base URI, discover it via /oauth/userinfo as Docusign documents.
4

Confirm the source is Active

Submit until the Docusign card shows Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Private key matches uploaded public key; server clock accurate.
Resolve regional restapi host from Docusign account metadata.
Keys and OAuth hosts must match the environment.

​
Considerations

Access tokens expire about hourly: JWT Grant re-runs…

Access tokens expire about hourly - JWT Grant re-runs automatically; protect the RSA private key like a production secret.

​
See also