How to pause a signature workflow
This topic demonstrates how to create an envelope where the workflow is paused before the envelope is sent to a second recipient. For information on resuming a workflow, see How to unpause a signature workflow.
Run this code example from our Quickstart or launcher projects: Bash, C#, Java, Node.js, PHP, PowerShell, Python, or Ruby.
Required data
Running the code in this how-to requires this data:
Step 1. Obtain your OAuth token
To make the API call shown in this how-to, you need a valid OAuth access token. Docusign supports access tokens for three different recommended OAuth grant types: Public Authorization Code Grant, Confidential Authorization Code Grant, and JSON Web Token (JWT) Grant. Choose the OAuth grant type appropriate for your scenario.
See Confidential Authorization Code Grant for guidance on your options to get an Confidential Authorization Code Grant OAuth token.
Step 2. Construct your API headers
After you have a valid OAuth access token, you are ready to construct the API headers that you will pass to the API call. Construct your headers like this, but make sure to substitute your valid OAuth access token for {ACCESS_TOKEN}.
Step 3. Construct the request body
Next, create the request body. To create an envelope using the eSignature API, you need to construct an envelope body in JSON format. Replace {SIGNER1_EMAIL}, {SIGNER1_NAME}, {SIGNER2_EMAIL}, and {SIGNER2_NAME} with your recipients’ data in the JSON request body.
The workflow section contains the information necessary to determine the action; in this case, pause_before, and the trigger routing_order, will cause the workflow to pause before the envelope is sent to the second recipient.
Step 4. Call the eSignature REST API
Now that you have constructed your API headers and request body, you can make a request to the eSignature REST API endpoint and include the JSON body to create a new envelope. Here’s how you make the call, but make sure to substitute your API account ID for {ACCOUNT_ID}.
Expected response
If you run this code example from our Quickstart or launcher projects, you should see a JSON response similar to the code shown.
Next steps
- Run this code example from our Quickstart or launcher projects: Bash, C#, Java, Node.js, PHP, PowerShell, Python, or Ruby.
- Learn more about Advanced Recipient Routing (ARR).
- See How to unpause a signature workflow.
- See How to use conditional recipients.
- See how to Go-Live with a completed app and find the base path for API calls in the production environment.