Bring your own editor UI. Use SuperDoc as the document engine underneath. Read the announcement →
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>"
}
}Sign a PDF or DOCX document with a cryptographic signature.
Send a JSON request body with:
document (required): object containing either base64 or urlsigner (required): signer details — email and name are required; ip and userAgent are optional and, when provided, are recorded in the audit trail certificate. No other signer fields are accepted; use metadata for anything application-specific.auditTrail (required): array of signing events. Must include at least one submit event for e-signature compliance.eventId (optional): unique identifier for the signing eventmetadata (optional): free-form object for application-specific context (tenantId, contractId, etc.)certificate (optional): { enabled: boolean } — controls whether an audit trail certificate page is appended (default: true)The response returns the signed PDF as base64.
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>"
}
}Documentation Index
Fetch the complete documentation index at: https://superdoc-caio-sd-2929-configurable-toolbar.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
API key authentication. Keys start with sd_
PDF or DOCX input. Provide exactly one of base64 or url.
Show child attributes
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.
Show child attributes
Complete event trail of user interactions. Must include at least one submit event for e-signature compliance.
1Show child attributes
Unique identifier for this signing event
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).
Configuration for the audit trail certificate page that is appended to the signed PDF.
Show child attributes
Default Response
Show child attributes
Was this page helpful?