Send Signature Request
Changed onSend a signature request.
OAuth Scope required: public.workflows.sendSignatureRequests
Note: You can only send a packet out for signature if all signers have an associated signature or initials tag (tag requirements are dependent on the signature provider).
Request
- Base URLhttps://ironcladapp.com/public/api/v1
- URLhttps://ironcladapp.com/public/api/v1/workflows/{id}/sign-status/send-signature-request
- AuthAPI key in header Authorization and OAuth 2Authorization code: https://ironcladapp.com/oauth/authorizeClient credentialsToken URL: https://ironcladapp.com/oauth/token scopes: public.workflows.sendSignatureRequests
Path parameters
The unique identifier or Ironclad ID of a workflow.
Headers
Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-id is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.
Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-email is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.
Response
200
Example response
{
"signers": [
{
"name": "Jane Doe",
"email": "janedoe@example.com",
"roleName": "Counterparty Signer",
"status": "pending",
"delegates": [
{
"name": "Kim Lam",
"email": "kimlam@example.com"
}
],
"routingOrder": 1,
"signsOutsideIronclad": true,
"type": "internal",
"userId": "63d415e0dd0d828c3a878548"
}
],
"routing": "sequential",
"status": "sent",
"provider": "Ironclad Signature"
}Changes
- warning
added the new
Custom Providerenum value to theresponse property for the response status - info
added the optional property
////to the response with the status - info
added the optional property
////to the response with the status
- warning