PDFMonkey API
67
AI ReadinessAI-Aware (B+)67/100
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsTesting Qabearer7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Generate PDF documents from templates with dynamic data, supporting both synchronous and asynchronous generation modes. Manage and retrieve generated documents and document cards.
Use for: I need to generate a PDF document from a template, I want to check the status of an async document generation, Retrieve a completed PDF document by its ID, List all documents generated in my account
Not supported: Does not handle HTML-to-PDF conversion, file format transformation, or template visual design via API - use for programmatic document generation from existing templates only.
Jentic publishes the only available OpenAPI specification for PDFMonkey API, keeping it validated and agent-ready. PDFMonkey API generates PDF documents programmatically from templates populated with dynamic data. The service supports both synchronous and asynchronous document generation, enabling high-volume workflows where documents are processed in the background and retrieved when ready. It also provides document card management for organizing and tracking generated documents.
Install Jentic One Beta
Connect the PDFMonkey API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PDFMonkey 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%2Fpdfmonkey.io%2Fpdfmonkey" | 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%2Fpdfmonkey.io%2Fpdfmonkey" | 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 PDFMonkey API.
Generate PDF documents synchronously for immediate download
Queue asynchronous PDF generation for high-volume batch processing
Retrieve document status and download completed PDFs by ID
Manage document cards for organizing generated document metadata
List all generated documents with filtering options
Track document generation progress for async workflows
Use Cases
Patterns agents use PDFMonkey API for, with concrete tasks.
★ Synchronous Document Generation
Generate a PDF document immediately and receive the file in the API response. PDFMonkey's /documents/sync endpoint accepts template data and returns the completed PDF in a single request-response cycle. This is ideal for interactive workflows where users need their document instantly, such as downloading a receipt after a purchase.
POST to /documents/sync with template ID and dynamic data to generate and immediately retrieve a completed PDF
High-Volume Async Generation
Queue large batches of PDF documents for background generation. POST to /documents to create a generation job, then poll GET /documents/{id} or use webhooks to retrieve the completed PDF when ready. This approach handles thousands of documents without blocking the calling application.
POST to /documents with template ID and data to queue async generation, then GET /documents/{id} to check status and retrieve the PDF when complete
Document Lifecycle Management
Track and manage all generated documents through their lifecycle. List documents to audit generation history, retrieve individual document metadata via document cards, and monitor which documents are pending, completed, or failed. This provides full visibility into document generation operations.
GET /documents to list all generated documents, then GET /document_cards/{id} to retrieve metadata for a specific document generation
AI Agent PDF Workflow via Jentic
AI agents generate PDF documents as part of automated business processes by calling PDFMonkey through Jentic. The agent searches for document generation operations, receives the schema for synchronous or async endpoints, and executes without managing bearer tokens or polling logic manually.
Search Jentic for 'generate PDF document', load the /documents/sync operation schema, and execute with template data to produce a PDF immediately
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for pdfmonkey api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/documents
Queue async PDF document generation
POST
/documents/sync
Generate a PDF synchronously and return immediately
GET
/documents/{id}
Retrieve a document by ID with status and download URL
GET
/document_cards/{id}
Retrieve document card metadata
GET
/document_cards
List all document cards
POST
/documents
Queue async PDF document generation
POST
/documents/sync
Generate a PDF synchronously and return immediately
GET
/documents/{id}
Retrieve a document by ID with status and download URL
GET
/document_cards/{id}
Retrieve document card metadata
GET
/document_cards
List all document cards
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
PDFMonkey API
- AI-Aware (B+)67/100
82
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability60
Security75
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
51%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
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).
75
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
75%
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 PDFMonkey API by hand means managing its secret-key bearer auth and choosing between the synchronous and asynchronous document generation paths yourself. Through Jentic you install once, import PDFMonkey from the API Directory, store the API key once, and your agent calls it.
Permission scoping
PDFMonkey carries its template and payload details in the request body and identifies a document by id in the path, so scope the agent by the operations it needs, such as generating a document synchronously or reading a document by id. You choose that set, so any operation you leave out stays unavailable to the agent.
Credential isolation
Your PDFMonkey API key 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 'generate a PDF document', and Jentic returns the matching PDFMonkey operations including /documents and /documents/sync with full schemas so the agent chooses sync or async and calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PDFMonkey API through Jentic.
Why is there no official OpenAPI spec for PDFMonkey API?
PDFMonkey does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PDFMonkey API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the PDFMonkey API use?
PDFMonkey API uses bearer token authentication. You pass your secret API key from your PDFMonkey account dashboard as a Bearer token in the Authorization header. Through Jentic, this key is stored in the credential vault and agents never see the raw token.
What is the difference between sync and async document generation?
POST to /documents/sync generates and returns the PDF in a single response. POST to /documents queues the generation in the background - you poll /documents/{id} or receive a webhook when the PDF is ready. Use sync for immediate needs and async for batch processing.
How do I check the status of an async PDF generation?
GET /documents/{id} returns the current document status including whether generation is pending, processing, completed, or failed. Once complete, the response includes the download URL for the generated PDF.
How do I generate PDFs through Jentic with PDFMonkey?
Install with pip install jentic, search for 'generate PDF document', and Jentic returns the /documents/sync or /documents operation schemas. Execute the call with your template ID and data payload. Jentic handles bearer auth automatically.
What are document cards in PDFMonkey?
Document cards store metadata about generated documents, accessible via GET /document_cards/{id} or listed via GET /document_cards. They provide an organizational layer for tracking generation history and document attributes separate from the PDF files themselves.
Can I limit what my agent is allowed to do with the PDFMonkey API?
Yes. Because you self-host Jentic One, your own rules decide which PDFMonkey operations and credentials the agent may use, so you scope it to only the calls it needs, such as generating a document synchronously through /documents/sync or reading one by id through GET /documents/{id}. If you leave out operations like queuing async jobs on /documents or listing document cards, those stay unavailable to the agent. This lets you grant an agent read-only access to generated documents while withholding the ability to create new ones.
GET STARTED