Glossary
Signing Link
TL;DR
The signing link is the bridge between your application and the signer. When your API call creates a document, the e-signature provider sends an email to the recipient containing this link. Clicking it opens the document in a secure signing interface.
**Anatomy of a signing link**
A typical signing link contains: • A base URL (the provider's signing domain) • A unique token identifying the document and recipient • Optional parameters for customisation (return URL, language)
Example: https://sign.signb.ee/s/abc123def456
**Security properties**
• Single-use or limited-use to prevent replay attacks • Expires after a configurable period (default: 7-30 days) • HTTPS only — never transmitted over unencrypted connections • Token is cryptographically random — cannot be guessed or enumerated
**Embedded vs email signing links**
Two delivery models: 1. **Email delivery** — the provider sends the signing link via email to the recipient (default for most APIs) 2. **Embedded signing** — the API returns the signing link URL, and your application embeds it in an iframe or redirects the user. This creates a white-label experience where the signer never leaves your app.
**What happens after signing**
Once the signer completes the signing ceremony via the link, the system generates a signing certificate (with SHA-256 hash), sends a webhook notification, and the link becomes inactive.
Related terms
Further reading
Related resources
Try Signbee — e-signatures via API.