Docufence PDF API
18
AI ReadinessNon-Ready (F)18/100
Agent-ready OpenAPI document · curated by JenticStorageDocument Managementbearer93 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Upload and digitally sign PDF documents: create and manage digital signing IDs, sign files directly or through a cloud flow, and track recent and favorite documents.
Use for: Upload a PDF to sign, Sign a PDF file with my digital ID, Create a new digital signing ID, List my digital IDs
Not supported: Does not handle contract templating, approval workflows, or long-term document archival. Use for uploading, managing, and digitally signing PDF documents only.
Jentic publishes the only available OpenAPI specification for the Docufence PDF API, keeping it validated and agent-ready. The Docufence PDF API uploads PDF documents and signs them with digital IDs. It creates and manages digital signing IDs, signs files directly or through a cloud upload-and-sign flow, and keeps a document library of recent and favorite files. It also manages the signer's account, email OTP verification, and active packages.
Install Jentic One Beta
Connect the Docufence PDF API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Docufence PDF API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdocufence.com%2Fdocufence" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdocufence.com%2Fdocufence" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Docufence PDF API.
Upload PDF files and generate file IDs for signing
Sign a PDF with a stored digital ID
Create and manage digital signing IDs
Sign files on the server through the cloud upload flow
List recent files, mark favorites, and read file info
Manage the signer's profile, email OTP verification, and active packages
Use Cases
Patterns agents use Docufence PDF API for, with concrete tasks.
★ Agent-Driven PDF Signing
An AI agent handling document workflows can upload a PDF, create or select a digital ID, and apply a signature through the Docufence PDF API. The signed file is produced server-side so the agent returns a finished document without a desktop signing tool.
Upload a PDF, create a digital ID, and sign the file, then retrieve the signed result
Cloud Upload and Server-Side Signing
High-volume signing pipelines can use the Docufence PDF API's cloud flow to generate upload URLs, finalize the upload, and sign the file on the server. This keeps large files off the client while still returning a signed PDF.
Generate an upload URL, finalize the upload, and sign the file on the server
Signed Document Library
Document-management tools can list a user's recent files, mark favorites, and read file info through the Docufence PDF API. This gives an agent a working view of a signer's document library alongside the signing operations.
List the user's recent files and mark one as a favorite
Key Endpoints
93 endpoints — jentic publishes the only available openapi specification for the docufence pdf api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/api/v1/upload-file
Upload a file
POST
/api/v1/sign-file
Sign a PDF file
POST
/api/v1/create-digital-id
Create a digital ID for signing
GET
/api/v1/get-digital-ids
List digital IDs
GET
/api/v1/generate-file-id
Generate a file ID
POST
/api/v1/cloud/sign-file-on-server
Sign a file on the server
GET
/api/v1/files/recent
List recent files
GET
/api/v1/active-packages
List active packages
POST
/api/v1/upload-file
Upload a file
POST
/api/v1/sign-file
Sign a PDF file
POST
/api/v1/create-digital-id
Create a digital ID for signing
GET
/api/v1/get-digital-ids
List digital IDs
GET
/api/v1/generate-file-id
Generate a file ID
POST
/api/v1/cloud/sign-file-on-server
Sign a file on the server
GET
/api/v1/files/recent
List recent files
GET
/api/v1/active-packages
List active packages
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
pdf_reader
- Non-Ready (F)18/100
52
Foundational Compliance74
Developer Experience & Jentic Compatibility31
AI-Readiness & Agent Experience86
Agent Usability60
Security3
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
52
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C-Signals: 4
93%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
17%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
74
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
72%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
31
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
13%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
74%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
38%
Summary Coverage
Coverage of summaries across operations/tags/info.
86
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
86%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
3
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
3%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Docufence PDF API by hand means managing its bearer token, handling file uploads and the cloud upload-and-sign flow, and tracking digital IDs across many operations. Through Jentic you install once, import the Docufence PDF API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Docufence PDF API covers document signing plus account and billing operations, so a rule should bound which operations your agent may call. Limit it to the file-upload and signing operations it needs, and leave account operations like profile deletion and user deletion out unless you add them.
Credential isolation
Your Docufence bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'sign a PDF file' or 'create a digital ID', and Jentic returns the matching Docufence operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Docufence PDF API through Jentic.
Why is there no official OpenAPI spec for the Docufence PDF API?
Docufence does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Docufence PDF API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What authentication does the Docufence PDF API use?
The Docufence PDF API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. You obtain the token by signing up or logging in, and most operations require it. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
Can I sign a PDF with the Docufence PDF API?
Yes. The Docufence PDF API uploads a file, creates or selects a digital ID, and signs the PDF, either in a single call or through a cloud flow that signs the file on the server. You can then list recent files and read file info to track the signed documents.
What are the rate limits for the Docufence PDF API?
The OpenAPI spec does not specify rate limits for the Docufence PDF API. Check the provider's documentation at https://docufence.com for the current limits that apply to your account.
Can I limit what my agent is allowed to do with the Docufence PDF API?
Yes. The API covers signing plus account and billing operations, so a rule should bound which operations your agent may call. Write a rule that allows only the file-upload and signing operations the agent needs, and leave account operations like profile deletion and user deletion out unless you add them, and every call it makes is logged.
How do I sign a document with the Docufence PDF API through Jentic?
Search Jentic for 'sign a PDF file' and it returns the Docufence signing operation with its input schema. Import the Docufence PDF API from the Jentic API Directory, store your bearer token once, and your agent can upload a file, create a digital ID, and sign it without hand-wiring the token on each request.
Is there a Docufence PDF API MCP server?
You don't need an MCP server to give your agent the Docufence PDF API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the upload, signing, and file operations. Nothing extra loads into the agent's context until an operation is actually used.
GET STARTED