Documentation
Access Dev CenterSuggest a FeatureContact SupportCreate SandboxRequest a Demo
Start typing to search…

Understanding Shared Links vs Embedded Signing Sessions

Key conceptual differences between PandaDoc's two signing approaches and their implications

Understanding Shared Links vs Embedded Signing Sessions

Overview

PandaDoc offers two distinct approaches for document signing: shared links and embedded signing sessions. While both enable recipients to sign documents, they differ fundamentally in architecture, user experience, and technical capabilities. Understanding these differences is crucial for choosing the right approach for your integration.

Context

The distinction between these approaches matters because they serve different use cases and have different technical constraints. Shared links provide a standalone signing experience with built-in features like automatic redirects, while embedded sessions offer seamless integration into your application but require custom JavaScript handling for post-completion actions.

How Each Approach Works

Shared Links

Shared links direct recipients to a dedicated PandaDoc signing page outside your application. When you send a document through PandaDoc's standard workflow:

  1. Recipients receive an email with a secure signing link
  2. The link opens PandaDoc's hosted signing interface
  3. After completion, PandaDoc can automatically redirect users using the redirect parameter
  4. The entire signing experience happens on PandaDoc's domain

This approach leverages PandaDoc's complete signing infrastructure, including automatic email notifications, reminder systems, and built-in redirect functionality.

Embedded Signing Sessions

Embedded signing sessions integrate the signing experience directly into your application using iframes:

  1. You create a signing session via API to generate a session ID
  2. The session ID is embedded in your application using an iframe
  3. Recipients sign without leaving your application
  4. Post-completion actions must be handled through JavaScript events (session_view.document.completed)
  5. The signing interface appears seamlessly within your application's UI

This approach prioritizes user experience continuity but requires custom handling for post-completion workflows.

Key Architectural Differences

Post-Completion Handling

Shared Links: Support automatic redirects through the redirect parameter in the API. PandaDoc handles the redirect automatically after document completion.

Embedded Sessions: Redirect parameters are ignored. Instead, your application must listen for JavaScript events and handle post-completion actions programmatically.

Integration Complexity

Shared Links: Lower integration complexity. Standard API calls with built-in functionality for common workflows.

Embedded Sessions: Higher integration complexity. Requires iframe management, JavaScript event handling, and custom post-completion logic.

Common Scenarios

When Shared Links Excel

  • Email-based workflows: When recipients expect to receive signing links via email
  • Simple redirect needs: When standard post-completion redirects are sufficient
  • Multi-party signing: When documents require multiple signers with different access patterns

When Embedded Sessions Excel

  • Seamless user experience: When users should never leave your application
  • Custom post-completion workflows: When you need complex actions after signing (updating CRM records, triggering workflows, etc.)
  • White-label solutions: When maintaining your brand experience is critical
  • Real-time integrations: When you need immediate notification of completion events

Trade-offs and Considerations

Shared Links Trade-offs

Advantages:

  • Built-in redirect functionality
  • Lower development complexity
  • Comprehensive email notification system
  • Full PandaDoc feature support

Limitations:

  • Recipients leave your application
  • Less control over user experience
  • Standard redirect options only

Embedded Sessions Trade-offs

Advantages:

  • Seamless user experience
  • Complete control over post-completion actions
  • Custom branding and UI integration
  • Real-time event handling

Limitations:

  • No automatic redirect support
  • Requires JavaScript event handling
  • Higher security responsibility
  • More complex error handling

Technical Implications

The architectural difference affects how you handle common integration scenarios:

  • Redirects: Shared links use API parameters; embedded sessions use JavaScript events
  • Error handling: Shared links rely on PandaDoc's error pages; embedded sessions need custom error handling
  • User feedback: Shared links have built-in completion messages; embedded sessions require custom UI
  • Mobile experience: Shared links work universally; embedded sessions may need responsive iframe handling

Related Concepts

Updated 2 days ago