Content signing send

post/signing/requests

Send a PDF from the drive for signature to up to ten people, together or one after another. The file's fingerprint is taken now; if the file changes, nobody can sign it.

Before you call

Credential: Authorization: Bearer $KEY
Scope: content:write
Sdk: content.signing.send
Cli: content signing send

Request bodyapplication/json, required

assetIdstring (uuid)required
titlestringrequired
At most 200 characters.
messagestring
Default: . At most 2000 characters.
signerslist of objectrequired
- namestringrequired
  At most 200 characters.
- emailstring (email)required
  At most 254 characters.
orderedboolean
Default: false.
expiresDaysinteger
Default: 30. At least 1. At most 90.

Responses

201application/json
Success
400application/json
The request was malformed
- errorstringrequired
- messagestring
401application/json
No valid credential
- errorstringrequired
- messagestring
403application/json
The credential lacks the scope, origin or address
- errorstringrequired
- messagestring
429application/json
Over the key's rate limit; see Retry-After
- errorstringrequired
- messagestring

Example request

curl -X POST 'https://api.rivier.ai/signing/requests' \
  -H 'Authorization: Bearer $KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "assetId": "string",
  "title": "string",
  "signers": [
    {
      "name": "string",
      "email": "name@example.com"
    }
  ]
}'

$KEY stands for your own key. No key is shown or kept on this site.

This page as Markdown