SigFetch
Send documents for signature through your own SigFetch account, so the envelopes belong to you.
SigFetch is the e-signature service behind HootQuill’s signing — envelopes, the page your client signs on, and the certificate of completion that proves they did. Connecting your own account moves that work onto it.
What it does in HootQuill
With a key connected, an uploaded document you send for signature goes out as a SigFetch envelope instead of through HootQuill’s own signing page. Concretely, that changes four things:
- SigFetch emails your client and hosts the page they sign on — so the branding, the domain and the reminders are theirs, not ours.
- The envelope and its certificate live in your SigFetch account, searchable and exportable there, and they stay yours if you ever stop using HootQuill.
- HootQuill still writes the contract, files the signed copy back here, archives it, and keeps its own audit trail. Nothing on this side is given up.
- Uploaded documents only. An agreement HootQuill generated has its signature block built into its own layout, so those keep signing here whether or not SigFetch is connected.
That last point is the one worth reading twice: connecting SigFetch does not move all your signing across. It applies to documents you upload — the case where the document was not built here in the first place.
Why you might want your own account
- Ownership of the record. Every envelope and certificate sits in an account you control.
- Your own sending limits, counted against your account rather than shared.
- One signing trail. If you already send NDAs or HR paperwork through SigFetch, this puts your agreements in the same place instead of a second system.
Hooking it up
Step 1. Create an API key in SigFetch
In SigFetch, go to SettingsAPI Keys and create one. No account yet? Start at sigfetch.com.
Step 2. Open the integration in HootQuill
SettingsIntegrations, then the SigFetch tile. The catalogue is searchable — type “signature” or “esign” if you cannot see it.
Owner-only. A key that can send agreements as you is not something an admin should be able to swap quietly.
Step 3. Paste the key and connect
HootQuill checks the key against SigFetch before storing it, so a bad paste is refused now rather than failing on your first real send. It is then encrypted at rest and never shown again — you see only the first and last few characters, enough to tell which key it is.
The tile changes to Connected once the check passes, and the page records when it was last verified.
Step 4. There is no step four
HootQuill registers its own webhook with SigFetch so completed signings come straight back. You do not configure it, and disconnecting removes it — rather than leaving a dead endpoint retrying against us forever.
What comes back
When your client finishes, the executed PDF is downloaded, filed against the document here, and archived like every other signed agreement.
SigFetch appends its own certificate of completion to that PDF, recording the signer’s IP address, browser, consent time and envelope id. HootQuill does not generate a second certificate for these — theirs records things we never observed, and two certificates that disagree are worse than one.
Disconnecting
Removes the key and unregisters the webhook. Envelopes already in your SigFetch account stay there, because they are yours; signed copies already filed here stay here. New uploads go back to signing through HootQuill.