DocuSeal
DOCS & KNOWLEDGE · FILES & DOCS
Signing templates, submissions, and signers in the account they connected.
Connect DocuSeal with Fabriq Developer
Your user pastes their DocuSeal credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting DocuSeal in practice
Authentication is one X-Auth-Token header with no scoping and no published rate limit, and the global and EU clouds are separate hosts (api.docuseal.com and api.docuseal.eu) so an account and its templates exist on exactly one of them. Failed webhooks are retried for 48 hours on a 2^attempt-minute schedule, which turns a bad deploy into two days of replay.
Worth knowing
- Three separate webhook families have to be subscribed to — form (form.viewed, form.started, form.completed, form.declined), submission (submission.created, submission.completed, submission.expired, submission.archived) and template (template.created, template.updated, template.archived) — so listening to submissions alone misses every signer-level event.
- "Failed webhook requests (4xx, 5xx) are automatically retried multiple times within 48 hours (every 2^attempt minutes) for all production accounts", so an endpoint that 500s during a release keeps receiving the same event for two days.
- The base host is per-deployment rather than per-version: api.docuseal.com globally, api.docuseal.eu for the EU, and a custom host when self-hosted, so region is a configuration value rather than a request parameter.
- DocuSeal publishes no rate limit, payload size or concurrency figures, so there is nothing to size a backoff against beyond observed 429s.
Checked against DocuSeal API (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put DocuSeal behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.