API Doc

Name: API Doc API
Brand: API Doc
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey2 EndpointsREST

For Agents

Render PDFs from React or HTML templates so an agent can produce branded contracts, receipts, and reports without running headless Chrome.

Quickstart

Get started with API Doc in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"generate a pdf from a react template"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with API Doc API.

Initiate a PDF rendering session via /api/docs/initiate

Generate a final PDF document by calling /api/docs/generate with the prepared payload

Render React components to a styled PDF without managing a headless-browser pipeline

Produce branded receipts and invoices that match the live web UI styling

GET STARTED

Start building with API Doc API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for API Doc, keeping it validated and agent-ready.

The Onedoc API generates PDF documents from React components and HTML, giving developers a programmatic way to render branded contracts, receipts, invoices, and reports. Two endpoints cover the lifecycle: /api/docs/initiate prepares the rendering session and /api/docs/generate returns the rendered PDF. The API is designed for teams that want PDF output that mirrors a React frontend without maintaining a headless-browser pipeline.

Use Cases

Patterns agents use API Doc API for, with concrete tasks.

★ Receipt and Invoice Generation

Render branded receipts and invoices from a React template that already exists in the product UI, removing the need for a separate PDF stylesheet. After /api/docs/initiate prepares the session, /api/docs/generate returns the binary PDF that can be emailed to the customer or stored in the order record. This pattern keeps the visual design in one codebase.

Call POST /api/docs/initiate with the React component payload for the order receipt, then POST /api/docs/generate to retrieve the binary PDF for emailing

Contract Document Rendering

Generate signed-ready contract PDFs from a templated HTML or React document populated with deal-specific values. The two-step initiate-then-generate flow lets the caller validate the payload before paying for the render, which is useful when contract templates change frequently and rendering is the most expensive step.

Initiate a document with the contract template and merged variables, then generate the PDF and post the URL to the e-signature platform

Report and Statement Output

Produce monthly statements, analytic reports, or compliance documents as PDFs from a React component populated with data pulled from the warehouse. The Onedoc API handles pagination and styling, so backend services can focus on data assembly rather than maintaining a separate pdf-rendering stack.

Assemble the report data, send the populated React component payload to /api/docs/initiate, then /api/docs/generate to produce the PDF for storage

Agent-Driven Document Production

Let an AI agent produce PDFs in response to natural-language requests by searching Jentic for 'generate a pdf', loading the Onedoc operation schema, and executing with the template payload. The agent never holds the x-api-key — Jentic injects it at execution time.

Search Jentic for 'generate a pdf from a react template', load the schema for /api/docs/generate, and execute with the user's template payload

Key Endpoints

2 endpoints — the onedoc api generates pdf documents from react components and html, giving developers a programmatic way to render branded contracts, receipts, invoices, and reports.

METHOD

PATH

DESCRIPTION

POST

/api/docs/initiate

Initiate a PDF rendering session

POST

/api/docs/generate

Generate the final PDF document

POST

/api/docs/initiate

Initiate a PDF rendering session

POST

/api/docs/generate

Generate the final PDF document

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The x-api-key for Onedoc is stored encrypted in the Jentic vault (MAXsystem). Agents call /api/docs/initiate and /api/docs/generate through scoped tokens — the raw key never enters agent context.

Intent-based discovery

Agents search by intent (e.g. 'generate a pdf from a react template') and Jentic returns the two-step initiate/generate operations with their schemas, so the agent calls the right sequence without reading Onedoc docs.

Time to first call

Direct Onedoc integration: a few hours for auth and the two-step call sequence. Through Jentic: under 30 minutes — search, load schemas, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PDFMonkey API

PDFMonkey renders PDFs from HTML/Liquid templates managed in their dashboard

Pick PDFMonkey if your team prefers a hosted template editor; pick Onedoc if your design lives in your React codebase

Alternative

PDF Generator API

PDF Generator API offers a drag-and-drop template builder with merge-data rendering

Choose PDF Generator API for non-developer template editing; choose Onedoc when developers own the templates as code

Alternative

CraftMyPDF API

CraftMyPDF provides JSON-to-PDF rendering with a visual template editor

Use CraftMyPDF for JSON-driven templates with no code; use Onedoc when the rendered output must match a React UI exactly

FAQs

Specific to using API Doc API through Jentic.

What authentication does the Onedoc API use?

API key authentication via the x-api-key header. Through Jentic the key is stored encrypted in the vault (MAXsystem) and never enters agent context — agents receive scoped access only.

Can I render React components directly to a PDF?

Yes. The two-step flow uses /api/docs/initiate to prepare the rendering session and /api/docs/generate to return the binary PDF. Onedoc's value proposition is that the React component used in your live UI is the same one rendered to PDF.

What are the rate limits for the Onedoc API?

The OpenAPI spec does not publish explicit rate limits. Limits are governed by your Onedoc subscription tier — check your account dashboard at onedoclabs.com for current quota before bulk rendering.

How do I generate a PDF through Jentic?

Run pip install jentic, then search 'generate a pdf from html'. Jentic returns POST /api/docs/initiate and POST /api/docs/generate with their input schemas — load each schema in turn and execute. The agent never sees the x-api-key.

Is the Onedoc API free to use?

Onedoc operates on a tiered subscription with per-render pricing above the free quota. The OpenAPI spec does not encode pricing — refer to onedoclabs.com for current plans.

Why two endpoints instead of one?

The /api/docs/initiate step lets you validate the payload and lock in template variables before the more expensive /api/docs/generate render call, which is helpful when rendering is metered or when previewing variants before committing.