Apache PDFBox
Apache PDFBox is an open-source Java library for working with PDF documents. It allows creation of new PDF documents, manipulation of existing documents, and the ability to extract content from documents with support for digital signatures.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Apache PDFBox the way a machine reads it — 63 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Apache PDFBox scores 49.5/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Apache PDFBox
Each block below is one kind of artifact we hold for Apache PDFBox. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Apache PDFBox Documents API
The Documents API from Apache PDFBox — 3 operation(s) for documents.
Apache PDFBox Forms API
The Forms API from Apache PDFBox — 1 operation(s) for forms.
Apache PDFBox Operations API
The Operations API from Apache PDFBox — 2 operation(s) for operations.
Apache PDFBox Pages API
The Pages API from Apache PDFBox — 1 operation(s) for pages.
Apache PDFBox Signatures API
The Signatures API from Apache PDFBox — 1 operation(s) for signatures.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apache Pdfbox Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Apache Pdfbox Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
PDF Text Extraction
Extract plain text and structured content from PDF documents
PDF Creation
Create new PDF documents programmatically with Java API
PDF Manipulation
Merge, split, rotate, and resize pages in existing PDFs
Digital Signatures
Apply and verify digital signatures for document authenticity
Form Filling
Read and fill interactive PDF forms (AcroForms)
PDF/A Validation
Validate and create PDF/A documents for archiving
Font Handling
Embed and extract fonts, handle Type 1, TrueType, and OpenType
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Apache Pdfbox Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Apache PDFBox API Rules
SPECTRALApache PDFBox API Rules
SPECTRALJSON Schema 11
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CreateDocumentRequest
JSON SCHEMADocumentInfo
JSON SCHEMADocumentMetadata
JSON SCHEMAFormField
JSON SCHEMAFormFields
JSON SCHEMAMergeRequest
JSON SCHEMAPageInfo
JSON SCHEMAPageList
JSON SCHEMASignRequest
JSON SCHEMASplitRequest
JSON SCHEMATextExtractionResult
JSON SCHEMAScroll within the panel for all 11 ·
JSON Structure 11
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apache Pdfbox Create Document Request Structure
JSON STRUCTUREApache Pdfbox Document Info Structure
JSON STRUCTUREApache Pdfbox Document Metadata Structure
JSON STRUCTUREApache Pdfbox Form Field Structure
JSON STRUCTUREApache Pdfbox Form Fields Structure
JSON STRUCTUREApache Pdfbox Merge Request Structure
JSON STRUCTUREApache Pdfbox Page Info Structure
JSON STRUCTUREApache Pdfbox Page List Structure
JSON STRUCTUREApache Pdfbox Sign Request Structure
JSON STRUCTUREApache Pdfbox Split Request Structure
JSON STRUCTUREApache Pdfbox Text Extraction Result Structure
JSON STRUCTUREScroll within the panel for all 11 ·
Examples 11
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 11 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Invoice Processing
Extract data from PDF invoices for automated processing
Document Generation
Generate PDF reports, contracts, and certificates programmatically
Legal Document Management
Digitally sign and verify legal documents
Form Data Collection
Fill PDF forms and extract submitted data
Archive Management
Convert documents to PDF/A for long-term archiving
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Apache Tika
Content detection and text extraction integration
Spring Boot
Spring Boot starter for PDF processing in web applications
Maven Central
Available as org.apache.pdfbox on Maven Central
iText/OpenPDF
Complementary PDF library for advanced PDF generation
Resources
Every other property we hold for Apache PDFBox — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apache-pdfbox · machine-readable index on apis.io