Skip to main content
POST
/
v1
/
sign
Sign
curl --request POST \
  --url https://api.superdoc.dev/v1/sign \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "document": {
    "base64": "aSDinaTvuI8gbWludGxpZnk="
  },
  "signer": {
    "email": "jane@example.com",
    "name": "Jane Smith",
    "ip": "203.0.113.42",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36"
  },
  "auditTrail": [
    {
      "type": "ready",
      "timestamp": "2023-11-07T05:31:56Z",
      "data": {}
    }
  ],
  "eventId": "<string>",
  "metadata": {},
  "certificate": {
    "enabled": true
  }
}
'
{
  "document": {
    "base64": "<string>",
    "contentType": "<string>"
  }
}

Authorizations

Authorization
string
header
required

API key authentication. Keys start with sd_

Body

application/json
document
base64 · object
required

PDF or DOCX input. Provide exactly one of base64 or url.

signer
object
required

Details of the person applying the signature. email and name are required; ip and userAgent are optional and recorded in the audit trail / certificate page when provided. No other fields are accepted — use metadata for application-specific context.

auditTrail
object[]
required

Complete event trail of user interactions. Must include at least one submit event for e-signature compliance.

Minimum array length: 1
eventId
string

Unique identifier for this signing event

metadata
object

Optional application-specific metadata. Free-form object for any context you want to attach to the signing event (e.g. tenantId, contractId, custom audit fields).

certificate
object

Configuration for the audit trail certificate page that is appended to the signed PDF.

Response

Default Response

document
object
required