POST /v1/certify
Apply a PKCS#7 detached digital signature to a PDF. This cryptographically proves the document has not been tampered with since certification and identifies the certifier.
This page documents the self-hosted server. For the hosted API at
https://api.formepdf.com, see Hosted API — Certify.Request Body
*
certificatePem and privateKeyPem are required on the self-hosted server. It also accepts them as certificate and privateKey.
Using Inline Certificates
Pass the certificate and private key directly in the request body:Using Saved Certificates
On the hosted API, you can save certificates in Credentials and reference them by ID. This avoids sending private keys in every request.Saved certificates are not available on self-hosted instances. Pass
certificatePem and privateKeyPem directly. On the hosted API, inline PEM goes in certificate and privateKey, and the visible-signature fields are not supported. See Hosted API — Certify.Response
200 OK with Content-Type: application/pdf — the certified PDF.
Related
- Digital Certification — certifying at render time, visible signatures, known limitations
- Credentials & Certificates — managing saved certificates on the hosted API