Skip to main content
When a contact signs a document or contract in the HoopAI platform, you can redirect them to a custom URL — such as a thank-you page, onboarding form, or payment link. This guide explains how to configure redirects, troubleshoot common issues, and pass dynamic data through query parameters.

​
Setting up a redirect URL

1

Open the document or contract template

Go to Payments > Documents & Contracts and open the template you want to configure. You can also set redirects when creating a new template.
2

Navigate to the signing options

Scroll to the Post-Signing Options section at the bottom of the template editor.
3

Enter your redirect URL

In the Redirect URL field, enter the full URL where the signer should be sent after completing the signature. The URL must include the protocol (e.g., https://).
4

Save the template

Click Save to apply the changes. The redirect will take effect for all new documents generated from this template.

​
URL format requirements

Your redirect URL must meet these requirements:
RequirementDetails
ProtocolMust start with https:// (recommended) or http://
DomainMust be a valid, publicly accessible domain
PathCan include any valid URL path (e.g., /thank-you)
Query parametersSupported — use standard URL encoding for special characters
FragmentsHash fragments (e.g., #section) are supported
Maximum length2,048 characters including query parameters
Do not use localhost, internal IP addresses, or private network URLs. The redirect happens in the signer’s browser, so the destination must be publicly reachable.

​
Passing dynamic data with query parameters

You can append dynamic contact and document data to the redirect URL using Hoop merge fields. These are replaced with actual values at the time of signing. Example redirect URL: 
https://yoursite.com/thank-you?contact_id={{contact.id}}&document_id={{document.id}}&email={{contact.email}}
Available merge fields:
  • {{contact.id}} — The contact’s unique ID in Hoop
  • {{contact.email}} — The signer’s email address
  • {{contact.name}} — The signer’s full name
  • {{document.id}} — The signed document’s ID
  • {{document.name}} — The document template name
URL-encode any merge field values that may contain special characters. Hoop automatically encodes most values, but custom fields with spaces or symbols may need manual encoding in your receiving application.

​
Troubleshooting redirect issues

Verify the redirect URL is saved in the template. Open the template editor and check the Post-Signing Options section. If the field is empty, the signer will see the default Hoop confirmation page instead. Also confirm the document was generated from the updated template — documents created before the change will not inherit the new redirect URL.
The destination URL may be down or returning an error. Test the URL directly in a browser to confirm it loads correctly. If you are using query parameters with merge fields, check that the resulting URL is well-formed and does not contain broken syntax.
Ensure the merge fields are spelled correctly, including the double curly braces. If a merge field value is empty (e.g., the contact has no email on file), the parameter will be included with an empty value. Check the contact record to confirm the data exists.
If you recently updated the redirect URL, the change only applies to new documents generated after the update. Previously sent documents retain the original redirect URL. Resend the document if you need the new redirect applied.
Some browsers or browser extensions block redirects to unfamiliar domains. Ask the signer to try in an incognito/private window or a different browser. HTTPS URLs are less likely to be blocked than HTTP.

​
Testing your redirect

1

Create a test document

Generate a document from the template with the redirect URL configured. Send it to your own email address.
2

Sign the document

Open the signing link and complete the signature process.
3

Verify the redirect

After signing, confirm that you are redirected to the correct URL. Check the browser address bar to verify query parameters are populated with the expected values.
If you are integrating the redirect destination with your own application, log the incoming query parameters on your server to confirm they match the expected merge field values from Hoop.
Last modified on March 5, 2026