Custom E-Sign (Self-Signing)

API reference

curl -X POST "https://__mock__/doc-service/v1/esign/esign-custom" \  -F pdf_file="string"

{
  "audit_trail_pdf_base64": "string",
  "signed_pdf_base64": "string",
  "credits_consumed": "string"
}

{
  "detail": {},
  "message": "string"
}

{
  "detail": {},
  "message": "string"
}

Overview

Call POST /doc-service/v1/esign/esign-custom from your backend with Authorization: Bearer <token> and multipart/form-data containing pdf_file (binary PDF). On 200 OK, decode signed_pdf_base64 and audit_trail_pdf_base64 on the server and store under your document vault policy.

Key features

• Self-sign path: No hosted redirect; you supply the PDF bytes.
• Audit artifact: audit_trail_pdf_base64 supports compliance evidence packs.

Implementation

Step 1: Call from your backend

Use your HTTP client library to attach the PDF as pdf_file.

POST /doc-service/v1/esign/esign-custom HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>
Content-Type: multipart/form-data; boundary=----boundary

------boundary
Content-Disposition: form-data; name="pdf_file"; filename="document.pdf"
Content-Type: application/pdf

<binary pdf bytes>
------boundary--

Step 2: Store outputs

Persist decoded PDFs in encrypted storage; do not paste base64 into support tickets.

Error handling

Security notes

• Bearer token must never ship to browser clients.

Benefits

• Fits backend-only signing jobs where a redirect flow is not desired.

Next steps

• Custom E-Sign verification
• Send Request
• Verification API index