English API Reference¶
This language-local API entry gives the /en/api/ path a stable structure.
Use the object map below to jump directly to focused API pages.
For an end-to-end task view, use Word Document Workflows.
Language¶
How To Read These Pages¶
The API pages are organized around public C++ objects rather than one long README-style page. Each focused page should expose:
Full public signatures from
include/featherdoc.hppwhere the API is a C++ entry point.Typed parameters, default values, units, and zero-based index rules.
Return values with success/failure semantics.
Short examples that show the intended call shape.
Public Include Entry Points¶
New C++ code should include the smallest public domain header that covers the
types it uses. <featherdoc.hpp> remains the compatibility aggregate when a
caller wants the full public API surface in one include.
<featherdoc/document.hpp>exposes theDocumentroot handle.<featherdoc/document_core.hpp>exposes shared document models, errors, inspection summaries, sections, page setup, images, content controls, and semantic diff data.<featherdoc/tables.hpp>exposesTable,TableRow,TableCell, and table inspection summaries.<featherdoc/templates.hpp>exposes template schema, validation, onboarding, and related helper APIs.<featherdoc/template_part.hpp>exposesTemplatePart.<featherdoc/styles_numbering.hpp>exposes style, numbering, and table style quality models.<featherdoc/reviews_fields.hpp>exposes fields, hyperlinks, notes, comments, revisions, and OMML helpers.<featherdoc/text.hpp>exposesParagraphandRun.<featherdoc/fwd.hpp>exposes lightweight forward declarations.<featherdoc/core.hpp>remains a compatibility aggregate for existing callers that include the older grouped entry point.
Object Map¶
Object |
What it is for |
Entry point |
|---|---|---|
|
Root handle for opening, saving, inspecting, and mutating |
|
Word document workflows |
Task-oriented path for generating, filling, reviewing, and batch-editing Word documents. |
|
|
Text content and run-level formatting. |
|
|
Table structure, rows, cells, widths, borders, alignment, and merge state. |
|
|
Image metadata, inline and floating insertion, extraction, replacement, and removal. |
|
|
Section structure, page setup, and section-resolved header/footer editing. |
|
Fields, links, notes, comments, and revisions |
Word fields, hyperlinks, footnotes, endnotes, comments, and tracked revisions. |
|
Styles and numbering |
Style inspection, style refactoring, numbering catalogs, and default formatting. |
|
|
Shared operations over body, header, footer, and section-specific parts. |
|
Edit plan operations |
JSON operation names accepted by |
|
PDF workflows |
Experimental |
|
Inspection summaries |
Read-only results and shared enum/option types used by content controls, tables, fields, images, and diffs. |
Core Objects
- Document
- Common Tasks
- Success And Failure Semantics
- Short C++ Example
- Typed Signature Guide
- Lifecycle
- Open Validation And Resource Limits
- Explicit Package Repair
- Handle Invalidation
- Template Part Access
- Sections And Inspection
- Template Filling Shortcuts
- Body, Tables, And Images
- Notes, Revisions, And Links
- Related API Families
- Examples
- Paragraph And Run
- Table, TableRow, And TableCell
- Images
- Sections And Page Setup
- Fields, Links, And Review Notes
- Styles And Numbering
- TemplatePart
- Edit Plan Operations
- PDF Workflows
- Enums And Common Option Types