canonical: https://jentic.com/apis/docufence.com/docufence

# Docufence PDF API

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.

## For AI 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.

## Scope

Does not handle contract templating, approval workflows, or long-term document archival. Use for uploading, managing, and digitally signing PDF documents only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: List the user's recent files and mark one as a favorite

## Key endpoints

| 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 |

## Key resources

- **Files** — Upload files, generate file IDs, and list recent, favorite, and file-info records
- **Signing** — Sign a PDF directly or through the cloud upload-and-sign flow
- **Digital IDs** — Create, list, and delete the digital IDs used to sign documents
- **Account** — Manage the signer's profile, password, and email OTP verification
- **Packages** — Activate and list the account's active packages

## AI readiness

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.

- **Score:** 18 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 52 / 100
  - Developer Experience & Jentic Compatibility: 74 / 100
  - AI-Readiness & Agent Experience: 31 / 100
  - Agent Usability: 86 / 100
  - Security: 60 / 100
  - AI Discoverability: 3 / 100
- **View full report:** https://jentic.com/apis/docufence.com/docufence/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **SignRequest** — SignRequest is an e-signature API, an alternative to the Docufence PDF API's signing operations.
- **BoldSign** — BoldSign offers e-signature and document workflows comparable to the Docufence PDF API.
- **PDF.co** — PDF.co processes and generates PDFs that pair with the Docufence PDF API's signing step.

## FAQ

### 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.