Trusted Signatures Publisher CLI
Quickstart-first CLI guide for sealing PDFs with Adobe-trusted signatures from CI/CD and scripts.
- Cross-platform binaries
- Digest-only network call
- Pipeline-friendly
Implementation proof
Ship faster with predictable trust behavior
Pick API, CLI, Web sealing, workflow automation, or cloud connector path, validate in Acrobat, and use trust documentation for compliance and architecture review.
~15m
CLI first success
Best for CI/CD and operations pipelines that need immediate signing output.
~30m
API first success
Recommended for product teams embedding trusted PDF sealing in services.
0
file uploads required
Only digest material is sent to sign endpoint; documents remain in your environment.
6
primary build paths
API, CLI, Web sealing, Zapier, Cloud Connector, and Power Automate paths fit different implementation teams.
CLI Quickstart
Use the CLI when your team wants the fastest path from PDF generation to Acrobat-verifiable trust.
1. Install
| |
2. Set credentials
| |
3. Seal a PDF
| |
4. Expected outcome
signed.pdfopens in Acrobat/Reader with trusted signature metadata.- Any unauthorized edits are flagged as invalid.
Useful flags
--ltv: embed long-term validation data--tsa: embed trusted timestamp--limit-changes <policy>: enforce post-seal change policy--endpoint: override API endpoint
Security notes
- Only SHA-256 digest is sent to Trusted Signatures API.
- Private document contents and metadata stay local.
- Ensure machine clock is accurate for HMAC auth.
Next steps
- Need API-level control? Use API quickstart.
- Need enterprise rollout planning? Book demo.
Need architectural review?
Book a technical walkthrough
For enterprise rollout, we can review trust model, controls, and integration patterns with your team.