Send Signature Request
This operation initiates the signature workflow by sending out notifications to all participants (signers, approvers, CCs) configured in the request. Once triggered, the request becomes active, and recipients can start interacting with the document based on their assigned roles.
Request URL
POST
/_apis/sign/api/v2/requests/requestId/send
To start the signing process for a signature request previously created using type=0
. Once sent, signers will receive an email or SMS (depending on configuration), and the document becomes available for interaction.
Required Headers
These headers must be included to authenticate the request.
Authorization
✅ Yes
Bearer token obtained from the OAuth 2.0 flow.
Request Body
This endpoint does not require a request body.
A valid requestId
and authenticated token are sufficient to trigger the request.
Successful Response
{
"requestId": "f742655b-7b27-43e1-9e4b-330246b140e6",
"embeddedSigningUrl": null
}
Possible Errors and How to Handle Them
400
Bad Request
The request ID may be missing or malformed.
401
Unauthorized
The access token is missing, expired, or invalid.
404
Request not found
The specified requestId
does not exist or has already been sent.
Last updated
Was this helpful?