Carbone
Carbone is a document generation engine that uses Word, Excel, PowerPoint and ODF templates with JSON data to produce PDFs or office documents. The Carbone HTTP API offers a template-then-render workflow with both cloud (api.carbone.io) and on-prem deployments. The Carbone JS rendering engine is open-source and embeddable.
Carbone publishes 3 APIs on the APIs.io network: Render API, Status API, and Template API. Tagged areas include Document Generation, PDF, Templates, Open-Source, and Office.
Carbone’s developer surface includes authentication, documentation, pricing, GitHub presence, engineering blog, and 9 more developer resources.
Kin Score
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Carbone Cloud HTTP API
Cloud-hosted Carbone API. Two flows — upload-once via POST /template then render with a template ID; or single-request inline-base64 render. Bearer-token auth (Authorization hea...
Carbone On-Premises
Self-hosted Carbone deployment exposing the same HTTP API. Auth disabled by default; enable via configuration. 30-day free trial of paid features.
Carbone Render Engine (Open Source)
Open-source Node.js library that powers the rendering engine. Embed directly in your application; render templates with JSON data without hitting the cloud API.
Carbone Render API
The Render API from Carbone — 3 operation(s) for render.
Carbone Status API
The Status API from Carbone — 1 operation(s) for status.
Carbone Template API
The Template API from Carbone — 2 operation(s) for template.
Open Collections 5
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCarbone Cloud HTTP Render API
OPEN COLLECTIONCarbone Cloud HTTP Render Status API
OPEN COLLECTIONCarbone Cloud HTTP Render Template API
OPEN COLLECTIONCarbone Cloud HTTP API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Carbone Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Carbone Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API