Technical evaluation No credit card for test key No document upload

Evaluate sealing in six clear steps

Create an account, generate a free test API key, and run an end-to-end seal in minutes. This path is designed for developer and product teams validating fit before production rollout.

Create Account Book Demo
Simple sealing flow
Great prices
Acrobat-verifiable output
Technical evaluation overviewFlow diagram from account and test API key to CLI or Zapier setup, local document sealing, and Acrobat review with untrusted test certificate.STEP 1Create accountAccess dashboard andkey controls.No credit card for test key.Ready in minutes.STEP 2Create testAPI keyFree sealing with untrusted cert.Use API Key ID + API key secret.STEP 3 + STEP 4Install integrationtoolingChoose CLI for scriptsor Zapier for no-code flows.CLI docs + Zapier docsConfigure API key valuesSTEP 5Seal documentDigest-only call.No source document upload.STEP 6Verify inValidatoror AcrobatSealed in test mode.No blue badge or green checkin test mode.STRENGTHS• No documentupload• Simplesealing• Greatprices

Process guide

Step-by-step technical eval

Follow this exact sequence to validate API access, local sealing behavior, and Acrobat results before moving to trusted production certificates.

See Pricing

Step 1

Create an account

Create your Trusted Signatures account to access API credentials and evaluation tooling.

Open account portal

Step 2

Create a test API key

Generate a free test key. This enables sealing with an untrusted certificate and requires no credit card.

Step 3

Install CLI or Zap

Choose the integration path that matches your workflow: command line for engineering pipelines or Zapier for automation.

Install CLI Open Zap guide

Step 4

Configure with your API key

Follow documentation to set key ID and key secret in your selected toolchain.

CLI docs Zap docs

Step 5

Seal a document

Run a seal operation using your test key and verify your output PDF is generated without uploading source documents.

Step 6

Open in Acrobat

The document will be sealed but not trusted yet. In this test mode you should not expect the blue badge or green check.

How it works

Seal and verify workflow

Use this model during technical evaluation to validate the sealing path and reader verification behavior end-to-end.

Seal PDF

  1. Send a request using CLI/API/Zap to Trusted Signatures (no document upload).
  2. Embed the returned seal into the PDF.
  3. Distribute the sealed PDF.

Verify PDF

  1. Open the PDF in a reader or use Trusted Signatures Validator.
  2. The seal is verified automatically and the sealer name is displayed.
Seal and verify PDF workflowTwo-lane diagram showing A: seal PDF in four steps and B: verify PDF in two steps, using API, CLI, or Zapier without file upload.Seal and Verify WorkflowNo document upload. Digest-only request with automatic verification at open.SEAL PDF1Prepare and digestOn your infrastructure, preparethe PDF and calculate digest.2Send requestUse API, CLI, or Zapierto request a seal.No document upload.3Embed returned sealEmbed returned seal payloadinto PDF signature contents.4Distributesealed PDFSend sealed output torecipients and downstreamsystems.VERIFY PDF1Open PDF in validator or AcrobatOpen in Trusted Signatures Validator or Acrobat/Reader.2Verification is automaticSeal verifies automatically and the sealer name is displayed.

Need production-ready trust?

Book a demo for trusted certificate rollout

We can help your team move from test-key evaluation to trusted signing with rollout guidance, controls alignment, and pricing clarity.

Book Demo Review Pricing