SignSealer docs

Embedded signing

Keep your application as the operational system of record and use SignSealer as the signing and evidence system of record.

Current supported pattern

  1. Your application creates or prepares the document through the API.
  2. SignSealer returns the signer-specific signing flow.
  3. The signer completes on the hardened hosted or white-label signing surface.
  4. Your application receives state changes through signed webhooks.

Why the public signing page is not generally frameable

The hosted signer page uses anti-framing protections. Removing them globally would let arbitrary sites place a signing page inside a deceptive interface.

Do not disable frame protection globally. A future iframe/JavaScript embed should use a short-lived session bound to the expected parent origin, with strict frame-ancestor CSP and origin-checked messaging.

Partner architecture

For SaaS platforms serving many customer businesses, use OAuth/scoped credentials, tenant-aware provisioning and signed webhooks instead of sharing a master API key into customer browsers.

Start with the API quickstart, then use the API reference for exact request shapes.