The DocuSign connector is a Palantir-provided driver for DocuSign.
To create a new DocuSign source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for DocuSign-specific configuration and networking. For the complete property reference, see the official DocuSign driver documentation ↗.
| Capability | Status |
|---|---|
| Exploration | 🟢 Generally available |
| Batch syncs | 🟢 Generally available |
| Incremental | 🟢 Generally available |
| OAuth 2.0 authentication | 🟢 Generally available |
| Table exports | 🟢 Generally available |
The properties below are mandatory or recommended.
| Property | Required? | Description | Default |
|---|---|---|---|
AuthScheme ↗ | Recommended | The type of authentication to use when connecting to DocuSign. | OAuthJWT |
CallbackURL ↗ | Recommended | The URL users return to after authenticating to DocuSign via OAuth. | http://localhost:33333 |
InitiateOAuth ↗ | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | REFRESH |
OAuthClientId ↗ | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
OAuthClientSecret ↗ | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
OAuthJWTCert ↗ | Recommended | The JWT Certificate store. | — |
OAuthJWTCertType ↗ | Recommended | The type of key store containing the JWT Certificate. | PEMKEY_BLOB |
OAuthJWTIssuer ↗ | Recommended | The issuer of the Java Web Token. | — |
OAuthJWTSubject ↗ | Recommended | The user subject for which the application is requesting delegated access. | <YourUserID> |
The table below lists the domains that the source must be able to access to run.
For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead. The agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.
| Domain | Required |
|---|---|
| account.docusign.com | If UseSandbox=FALSE (default) |
| account-d.docusign.com | Always |
This connector supports OAuth 2.0 authentication. Follow the OAuth 2.0 guidance for Palantir-provided drivers to configure and authorize the connection.
This connector supports table exports. Learn how to set up a table export.