How to Embed Clixsign into Your Website

This article describes the embedded Clixsign feature within the FORTH system. It is organized into the following sections:

• Overview
• Prerequisites
• How to Access
• How it Works

Overview

The Embedded Signing Experience with Clixsign allows Forth CRM users to integrate the Clixsign document signing process directly into external websites or applications. Instead of redirecting clients to a third-party Clixsign URL via email, you can now host the signing  within an iFrame on your own domain, reducing drop-off rates and creating a faster, more professional experience. Being able to track the signing status in real-time, your team saves time and reduces manual follow-up errors.

Prerequisites

• An active Clixsign subscription within your FORTH account. (Admin > Settings > ClixSign)
• A secure website (your web address must start with https://) to render the signing frame.
• A valid API Key from the Forth Developer Portal

How to Access

1. Generate your standard Clixsign document link. These steps are available in our Help Center article titled 
   [NOTE: Verify navigation path here]
2. Add ?embed=1 to the end of the web link.
3. Add &origin= followed by your exact secure website address (for example, &origin=https://www.your-website.com).
4. Provide this updated link to your web developer to embed on your website.

How it Works

1. Your client opens your website and views the embedded Clixsign document. The document displays a simplified view to keep the client focused on signing.
   [SCREENSHOT: The simplified Clixsign interface showing only the document and signature tools embedded on a custom webpage]
2. The client interacts with the document (for example, opening, signing, or declining).
3. Clixsign automatically sends real-time status updates to your website.
4. Your system records these updates so you know exactly where the client is in the signing process.

Implementation Guide

1. Generating the Embedded URL

To initiate an embedded session, you must first generate the document request via the API. Use the following endpoint:

Endpoint: POST /v1/clixsign/{contact_id}

Key Parameter: Set the delivery_method to embedded (or leave empty if handling the URL manually).

The API response will now include an embedded_url attribute:

{
  "status": "success",
  "response": {
    "document_id": "ABC-123-XYZ",
    "embedded_url": "https://clixsign.com/s/embed/[UNIQUE_TOKEN]",
    "expires_at": "2026-02-07T12:00:00Z"
  }
}

2. Embedding the iFrame

Insert the embedded_url into an iFrame on your client-facing portal.

💡 Tech Tip: We recommend a minimum width of 800px and a height of 1000px to ensure the document controls and signature pads are fully accessible on mobile and desktop.

<iframe 
    src="YOUR_EMBEDDED_URL_HERE" 
    width="100%" 
    height="1000px" 
    frameborder="0" 
    allow="geolocation; microphone; camera">
</iframe>

Post-Signing Workflow

Once the user completes the signature, Clixsign will attempt to redirect the parent window or the iFrame. You can configure a Return URL in your Clixsign Settings.

• Callback Events: Forth will send a webhook notification (if configured) when the document status changes to Signed or Completed.

• Automatic Extraction: If the document is a Power of Attorney (PoA), it will be automatically extracted and filed in the "Power of Attorney" section of the contact record.

IMPORTANT!  Your web address (the "origin") must match exactly, and it must be secure (https://). If it does not match, the system blocks the real-time status updates to protect your client's data.

Your system can track the following document updates automatically:

• Delivered: The system sent the document.
• Opened: The client opened the document.
• Adopted: The client placed at least one signature.
• Completed: All parties signed the document.
• Declined: The client refused to sign.
• Voided: The system canceled the document.
• Expired: The document passed its expiration date.
• In Escrow: The system applied California state rules to the document.

⚠️ Known Constraints

• Session Expiration: Embedded URLs are single-use and expire after 30 minutes if the session is not initiated.

• Browser Cookies: Users must have "Third-party cookies" enabled (or your domain must be whitelisted) if you are using certain advanced tracking features within the signing frame.

• Signer Roles: Currently, only the Primary Signer can initiate an embedded session via the API. Secondary signers will still receive standard email/SMS notifications.

Assistance

For further assistance, please reach out to support@setforth.com.

Article Revision History