Redirect Signers to a URL After Completing a Transaction – Proof Help Center
The article explains how to automatically redirect signers to a specified URL after completing a Proof transaction by generating a client-only API key in the Proof account settings, entering the desired redirect URL in the redirectUrl field, toggling forceRedirect to TRUE, saving the settings, and then sharing the associated EasyLink with signers to apply the redirect.
The short answer: You can automatically redirect signers to a URL of your choice — such as your website or a confirmation page — once their Proof transaction is complete. This is configured through your API key settings and shared via an EasyLink.
1. Set Up the Redirect
To configure the redirect URL, follow these steps after logging in to your Proof account:
- 1.Click Settings from the navigation panel on the left. If you don't see the panel, click the caret to expand it.
- 2.Select API Keys from the Settings menu.
- 3.Click Generate client only key at the top of the page. A new key appears in the list below.
- 4.Click the Settings icon next to the newly created API key.
- 5.Configure the key settings as needed (name, payer, min/max signers, etc.).
- 6.In the redirectUrl field, type or paste the URL where you'd like signers to land when their transaction is complete.
- 7.Toggle forceRedirect to TRUE.
- 8.Click Save.
If the redirect doesn't fire after a transaction is completed, confirm that forceRedirect is set to TRUE and that the redirectUrl field contains a valid, fully-qualified URL (e.g.,
https://yoursite.com/thank-you). The EasyLink must also be generated from this API key for the setting to apply.
2. Send the Transaction via EasyLink
Once the API key is configured, share the associated EasyLink with your signers to apply the redirect.
- 1.Click Tools from the menu on the left.
- 2.Select EasyLinks from the Tools menu.
- 3.Find your API-created EasyLink by the name you assigned it.
- 4.Click the three vertical dots on the right side of your EasyLink.
- 5.Select Share EasyLink and use your preferred sharing method.
Summary Checklist
- Generate a client-only API key in Settings → API Keys.
- Enter your destination URL in the redirectUrl field.
- Toggle forceRedirect to TRUE and save.
- Share the associated EasyLink with signers via Tools → EasyLinks.
Still Unsure?
Our support team is happy to help. Submit a support request or chat with us from any page in the app.
Related
API Supplement
The API Supplement, effective December 16, 2024, is incorporated into the Proof General Terms and grants Subscribers a limited, revocable license to use Proof’s APIs solely for integrating their applications with Proof’s Services, requires secure handling and non-sharing of API Keys, restricts API use to approved purposes, and governs access to sensitive personal data such as homeowner and financial information under strict compliance conditions.
Salesforce Installation and Configuration Guide
This Salesforce Installation and Configuration Guide instructs administrators on installing the Notarize with Proof package, setting up a public Salesforce Site for webhook event handling, configuring API credentials, Lightning components, and permission sets, all requiring an active Proof account with API access and recommending initial setup in a sandbox environment before production deployment.
Proof’s Technical Rebrand: What Customers Need to Know
Notarize is rebranding to Proof, with all web applications moving from notarize.com to proof.com starting September 14, maintaining existing login credentials and URL redirects, introducing a new recommended API endpoint at api.proof.com alongside the existing one, updating email domains to @proof.com, preserving Single Sign On configurations with new metadata, and running both domains concurrently during a transition period to ensure a smooth customer and partner experience.
Edit API-Created EasyLink Settings – Proof Help Center
The Proof Help Center guide explains how organizations can edit API-created EasyLink settings—such as name, payer, signer annotation permissions, ID requirements, transaction details, and signer limits—by logging into their account, navigating to Settings > API Keys, and adjusting options like allow_signer_annotations, require_secondary_photo_ID, external_ID, transaction_type, transaction_name, transaction_doc_category, min_signers, and max_signers, with a maximum of ten devices allowed per meeting including at least one notary and one signer.
Cloning a Child Organization in Command Center
The guide explains how Command Center owners and administrators can clone a child organization by copying specific settings like billing and notary instructions from an existing or root organization to create a new child organization, while noting that certain elements such as EasyLinks, API keys, and users do not transfer, and provides step-by-step instructions along with recommendations to review settings post-cloning and contact support if issues arise.
SoftPro integration setup instructions – Proof Help Center
The SoftPro integration setup instructions guide organizations through connecting SoftPro with Proof by generating and inputting API keys (with options for multiple users and child organizations), explain how documents are automatically returned post-transaction, detail assigning transactions to in-house notaries via specific submission options, and provide step-by-step directions to connect SoftPro to Proof and manage document tagging for streamlined home buying processes.