Embedded signing

Embed the Subnoto signing experience in your own application. The sign flow runs inside an iframe and is unlocked with a one-time token that you create on your backend. An iframe token is required for every integration (React, Vue, Svelte, Angular, Solid, Qwik, or plain iframe); there is no way to embed the signing UI without it.

How it works

1. Create an envelope using the API or SDK: upload a document, add recipients and signature blocks, then send (for example with distributionMethod: "none" if you open the link yourself).
2. Create an iframe token (required). For that envelope and signer, call POST /public/authentication/create-iframe-token with workspaceUuid, envelopeUuid, and signerEmail. This step is mandatory for every integration. See the Iframe token tutorial for the full API, URL format, and security notes.
3. Embed the signing UI in your app by passing the token into your chosen integration (a framework component or a plain iframe).

Start with the iframe token

No matter which framework you use (React, Vue, Svelte, Angular, Solid, Qwik) or plain HTML, you must create an iframe token on your backend first. The Iframe token page explains how to obtain it and use it in the embed URL.

Supported integrations

Iframe token

Generate and use the token that unlocks the embed

React

Use @subnoto/embed-react in a React app

Vue

Use @subnoto/embed-vue in a Vue app

Svelte

Use @subnoto/embed-svelte in a Svelte app

Angular

Use @subnoto/embed-angular in an Angular app

Solid

Use @subnoto/embed-solid in a Solid app

Qwik

Use @subnoto/embed-qwik in a Qwik app

Vanilla / HTML

Embed with a plain iframe and no framework