How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Apache POI website screenshot

Apache POI

Apache POI is a Java API for manipulating various file formats based upon the Office Open XML standards (OOXML) and Microsoft's OLE2 Compound Document format (OLE2). It supports reading and writing Excel, Word, PowerPoint, Visio, and Outlook files.

agent aware

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Apache POI the way a machine reads it — 81 machine-readable artifacts across 1 API, 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 POI scores 28.3/100 (thin), with a separate agent-readiness read of 17/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-10 · rubric v0.20.0
Apache POI Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Apache POI's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apache-poi/"
   title="Apache POI on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/apache-poi.svg"
       alt="Apache POI Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Apache POI

Each block below is one kind of artifact we hold for Apache POI. 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 4

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 POI Conversion API

The Conversion API from Apache POI — 1 operation(s) for conversion.

Apache POI Excel API

The Excel API from Apache POI — 4 operation(s) for excel.

Apache POI PowerPoint API

The PowerPoint API from Apache POI — 2 operation(s) for powerpoint.

Apache POI Word API

The Word API from Apache POI — 2 operation(s) for word.

Open Collections 5

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

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 Poi Rate Limits

5 limits

RATE LIMITS

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

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

Excel HSSF/XSSF

Read and write Excel files in legacy XLS (HSSF) and modern XLSX (XSSF) formats

Word HWPF/XWPF

Read and write Word documents in legacy DOC (HWPF) and modern DOCX (XWPF) formats

PowerPoint HSLF/XSLF

Create and manipulate PowerPoint presentations in PPT and PPTX formats

Formula Evaluation

Evaluate Excel formulas and compute cell values programmatically

Streaming API

Low-memory streaming API (SXSSF) for writing large Excel files

Chart Support

Create and modify charts in Excel workbooks and PowerPoint slides

Digital Signatures

Sign Office documents with digital signatures using OOXML standards

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

16 classes · 31 properties

JSON-LD

Spectral 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 POI API Rules

5 rules · 3 warnings

SPECTRAL

Apache POI API Rules

7 rules · 1 errors · 5 warnings

SPECTRAL

JSON Schema 16

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.

CellData

2 properties

JSON SCHEMA

Cell

4 properties

JSON SCHEMA

ConversionRequest

3 properties

JSON SCHEMA

ConversionResult

4 properties

JSON SCHEMA

DocumentRequest

3 properties

JSON SCHEMA

Document

5 properties

JSON SCHEMA

Paragraph

3 properties

JSON SCHEMA

PresentationRequest

3 properties

JSON SCHEMA

Presentation

4 properties

JSON SCHEMA

Shape

4 properties

JSON SCHEMA

SheetList

1 properties

JSON SCHEMA

Sheet

4 properties

JSON SCHEMA

Slide

3 properties

JSON SCHEMA

WorkbookList

2 properties

JSON SCHEMA

WorkbookRequest

3 properties

JSON SCHEMA

Workbook

5 properties

JSON SCHEMA

Scroll within the panel for all 16 ·

JSON Structure 16

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 Poi Cell Data Structure

2 properties

JSON STRUCTURE

Apache Poi Cell Structure

4 properties

JSON STRUCTURE

Apache Poi Conversion Request Structure

3 properties

JSON STRUCTURE

Apache Poi Conversion Result Structure

4 properties

JSON STRUCTURE

Apache Poi Document Request Structure

3 properties

JSON STRUCTURE

Apache Poi Document Structure

5 properties

JSON STRUCTURE

Apache Poi Paragraph Structure

3 properties

JSON STRUCTURE

Apache Poi Presentation Request Structure

3 properties

JSON STRUCTURE

Apache Poi Presentation Structure

4 properties

JSON STRUCTURE

Apache Poi Shape Structure

4 properties

JSON STRUCTURE

Apache Poi Sheet List Structure

1 properties

JSON STRUCTURE

Apache Poi Sheet Structure

4 properties

JSON STRUCTURE

Apache Poi Slide Structure

3 properties

JSON STRUCTURE

Apache Poi Workbook List Structure

2 properties

JSON STRUCTURE

Apache Poi Workbook Request Structure

3 properties

JSON STRUCTURE

Apache Poi Workbook Structure

5 properties

JSON STRUCTURE

Scroll within the panel for all 16 ·

Examples 16

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

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.

Apache Poi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Apache Poi Vulnerability Disclosure

security.txt · contact published

SECURITY

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.

Apache Poi Agentic Access

11 operations · 5 acting

11 operations · 5 acting

AGENTIC

Use Cases 4

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.

Report Generation

Generate Excel and Word reports programmatically from application data

Data Import/Export

Import data from Excel spreadsheets and export results back

Template Processing

Fill Office document templates with dynamic data

Document Conversion

Convert between legacy Office formats and modern OOXML formats

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

POI is used by Tika for Office document text extraction

Spring Framework

Integrate POI with Spring Boot for web-based document generation

Maven Central

Available as org.apache.poi artifacts on Maven Central

Apache Commons

Uses Commons Collections and Commons Math for data structures

Resources

Every other property we hold for Apache POI — 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

← All providers · Data indexed from github.com/api-evangelist/apache-poi · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Apache POI, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.