> 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

# How to obtain individual consent

> Demonstrates how to obtain individual consent for an app to act on their behalf in the eSignature API.

The most straightforward way to obtain consent for your application to act on a user’s behalf is to directly ask that user, getting their individual consent.

When an application authenticates to perform actions on behalf of a user, that user will be asked to grant consent for the set of [scopes](/platform/auth/reference/scopes) (sets of permissions) that the application has requested, unless they have previously granted that consent.

**Video walkthrough**

You can also see a video walkthrough of how to obtain individual consent, shown below:

## Prerequisites

To grant individual consent, you must meet the following prerequisites:

| Data element                                                                                                                                                                        | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You have defined an integration key.                                                                                                                                                | An [integration key](/platform/configure-app#integration-key) identifies your integration and links to its configuration values. To create an **integration key**: 1. Open the [Apps and Keys](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) Page. 2. Under **My Apps / Integration Keys**, select **Add App / Integration Key**, then give it a name.                                                                                                            |
| You have defined a [redirect URI](/platform/configure-app#redirect-uri) for your [integration key](/platform/configure-app#integration-key)[.](/platform/configure-app#integration) | The redirect URI is the URI (URL) to which Docusign will redirect the browser after authentication. To define a **redirect URI:** 1. Open the [Apps and Keys](https://admindemo.docusign.com/authenticate?goTo=appsAndKeys) page. 2. Under **My Apps / Integration Keys**, choose the integration key to use, then select **Actions**, then **Edit**. In the **Additional Settings** section, select **Add URI**. 3. Enter the new redirect URI. This can be a localhost address. |

## Step 1. Open the Docusign authorization URI

To begin authentication and obtain consent, your app will open a constructed Docusign authorization URI. Note that this is not a standard GET request and cannot be directly sent by the application. Instead, the browser will open the authorization request URI and the request is sent from there to the account server.

Typically, your application can provide this URI to the user as a link to select or via an email.

| Environment | API Base URI                                  | Web Site Login URL               |
| ----------- | --------------------------------------------- | -------------------------------- |
| Developer   | `https://account-d.docusign.com``/oauth/auth` | `https://account-d.docusign.com` |
| Production  | `https://account.docusign.com/oauth/auth`     | `https://account.docusign.com`   |

The authorization request includes several parameters used with the base URL to configure specific authentication options. The following parameters are required:

| Parameter       | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `response_type` | The type of grant to be used. This value should be `code`. **Note:** Your integration's settings in the Apps and Keys page should be configured to Authorization Code Grant, or you may receive an error.                                                                                                                                                                                                                                                                                                                         |
| `scope`         | The scope of the permissions being requested for the client. Typically, for users explicitly using individual consent, this value should be `signature%20impersonation`. If your application needs additional scopes, add them to the list.                                                                                                                                                                                                                                                                                       |
| `client_id`     | Your application's integration key.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| `redirect_uri`  | The URI to which Docusign will redirect the browser after authorization has been granted by the user. Typically, this will simply be a page thanking the user for granting consent. This page should be provided by the application. The redirect URI must match one of those pre-registered for the integration key in your Docusign account. This determines where to redirect the user after they successfully authenticate. **Note**: If you include query parameters in your redirect URI, the redirect must be url-encoded. |

Your application should open the resulting URI in a web browser to initiate the authentication process. You can test the process by pasting your URI string into a browser window.

**`Authorization URI syntax`**

```bash title="Authorization URI syntax"
https://account-d.docusign.com/oauth/auth?
response_type=YOUR_RESPONSE_TYPE
    &scope=YOUR_REQUESTED_SCOPES
    &client_id=YOUR_INTEGRATION_KEY
    &redirect_uri=YOUR_REDIRECT_URI
```

**`Example authorization URI`**

```bash title="Example authorization URI"
https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=7c2b8d7e-xxxx-xxxx-xxxx-cda8a50dd73f&redirect_uri=http://example.com/callback/
```

## Step 2. Obtain consent

If the user hasn’t already given consent (or if consent has been revoked by the user or an admin) they are notified that they must give consent to the application for the requested scopes.

After the user chooses **Accept,** consent is granted. The Docusign authentication service verifies that the client application is valid and has access to the requested scope. If so, it redirects the access token to the provided callback URI in a hash fragment.

Once a user has granted consent to an application, they will no longer be prompted to do so again unless [consent is revoked](/platform/auth/consent).

![Authorization Code Grant permission screen](/_fern-files/_img/38b6ab685d020669110bafe30aaae2b07f6c41372897d71ed86b0463d4abf1fa.webp)

## Next steps

* Every Docusign workflow requires that your user grant explicit consent for your application to act on their behalf. See [Obtain and revoke consent](/platform/auth/consent) for details and a description of each way to get consent from your users.
* Learn more about [authentication](/platform/auth).
* See the list of [scopes](/platform/auth/reference/scopes).