Agentic Fabriq
PandaDoc
DOCS & KNOWLEDGE · FILES & DOCS
Documents, templates, forms, contacts, and signing status in the account they connected.
Connect PandaDoc with Fabriq Developer
Your user consents at PandaDoc. The credential lands in a vault your agent cannot read, and the tool list it gets back is the intersection of that user’s grant and the agent’s own scopes.
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 PandaDoc in practice
PandaDoc rate limits are counted per user across all of that user’s keys on a sliding 60-second window, and they vary tenfold by operation: 2,000 requests a minute to list or check status but only 100 to download a document. A sandbox key is 10 requests a minute on every endpoint, so nothing about sandbox throughput predicts production.
Scopes that draw scrutiny
OAuth 2.0 scope `read+write`The scope PandaDoc’s own authorization example requests. It is the grant that lets an application create documents and send them out for signature on the user’s behalf.Sandbox API keyAvailable on any plan including a trial, and useful precisely because it cannot send real documents — but capped at 10 requests per minute, so it is not a load-test environment.
Rate limits
- Create from Template: 500 requests/minute. Create from PDF: 300/minute. Create Notarization Request: 100/minute.
- Send Document: 400/minute. Document Details: 600/minute. List, status and delete: 2,000/minute.
- Download Document: 100/minute. Download protected document: 300/minute.
- Sandbox API key: 10 requests per minute on any endpoint.
- Limits are per user across that user’s keys, over a sliding window of the last 60 seconds; overage returns 429 Too Many Requests.
- Maximum request body 2 MB. Maximum PDF for document creation 50 MB, above which the API returns 413 Request entity too large.
Who has to approve
PandaDoc is the gate rather than a workspace admin: the API has to be part of the plan, and creating an application — the prerequisite for OAuth — is only available once production API access is enabled on the account. Until then the sandbox key is the only route.
Worth knowing
- The 2 MB request-body cap and the 50 MB PDF cap are different limits, so a base64-inlined document hits the body ceiling long before the file ceiling.
- Because limits are per user, splitting an agent across two keys owned by the same account changes nothing about throughput.
- Download is the tightest common operation at 100 requests a minute, which is the limit an archival or evidence-collection job hits first.
- Access tokens expire and start returning 401; only the refresh token keeps a long-running integration alive, and multiple token pairs can be issued if it needs more than one.
Checked against PandaDoc API limits (2026-09-29), Authentication process (2026-09-29), About the PandaDoc 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 PandaDoc behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.