API SuiteDocument Signing
Custom E-Sign Verification
Verify a signed PDF against a public key. Server-side multipart POST with Bearer auth.
API reference
Try itLoading playground…
Loading…
AuthorizationBearer <token>
JWT Bearer token authentication. Obtain a token from the KwikID dashboard.
In: header
signed_pdf_filestring
public_key_filestring
Response Body
curl -X POST "https://__mock__/doc-service/v1/esign/esign-custom-verification" \ -F signed_pdf_file="string" \ -F public_key_file="string"{
"verification_message": "string"
}{
"detail": {},
"message": "string"
}{
"detail": {},
"message": "string"
}Overview
Call POST /doc-service/v1/esign/esign-custom-verification from your backend with Authorization: Bearer <token> and multipart/form-data fields signed_pdf_file and public_key_file (both required). On 200 OK, read verification_message for the outcome text.
Key features
- Cryptographic check: Validates a signed PDF against the supplied public key material.
- Pairs with signing: Use after Custom E-Sign (Self-Signing) or external signers.
Implementation
Step 1: Call from your backend
Attach signed_pdf_file and public_key_file as binary parts per OpenAPI.
Error handling
| HTTP status | When |
|---|---|
| 400 | Missing part or unreadable file. |
| 401 | Invalid token. |
Benefits
- Gives a server-side pass or fail without manual PDF inspection.