Doppio Render API

Name: Doppio Render API API
Brand: Doppio Render API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey6 EndpointsREST

For Agents

Render PDFs and screenshots from URLs or raw HTML using Doppio's managed headless Chromium, with synchronous, hosted-URL, or async-webhook delivery modes.

Quickstart

Get started with Doppio Render API 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:
"render a web page to PDF"

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

Capabilities

What an agent can do with Doppio Render API API.

Render a URL or HTML string to a PDF and stream the binary back in one request

Render a synchronous PDF and receive a hosted URL for download instead of raw bytes

Queue an asynchronous PDF render that posts the result to a webhook on completion

Capture a full-page or viewport screenshot of any URL with custom width and viewport settings

GET STARTED

Start building with Doppio Render API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Doppio Render API, keeping it validated and agent-ready. Doppio renders pixel-accurate PDFs and screenshots from a URL or raw HTML using a managed headless Chromium pool. The API exposes three modes — direct (synchronous binary response), sync (returns a hosted URL), and async (webhook-driven) — for both PDF and screenshot output. Authentication is a single Bearer-style API key passed in the Authorization header.

Use Cases

Patterns agents use Doppio Render API API for, with concrete tasks.

★ On-the-fly invoice PDF rendering

Finance and billing systems can render invoice PDFs by posting customer-specific HTML to /render/pdf/direct and streaming the binary response straight to S3 or to the customer email. Direct mode keeps latency under a second for simple HTML and avoids the round trip of polling. The same template HTML works for receipts, statements, and quotes.

POST to /render/pdf/direct with HTML content and viewport options, then stream the binary PDF response into object storage and return the storage key

Marketing screenshot automation

Marketing and SEO teams can capture daily screenshots of competitor or campaign pages by calling /render/screenshot/sync with the target URL, receiving a hosted URL that can be embedded in dashboards or alerts. Sync mode hosts the result on Doppio's CDN so the caller does not have to manage object storage. The waitFor parameter ensures dynamic content has loaded before capture.

POST to /render/screenshot/sync with the target URL, fullPage true, and waitFor a selector, then store the returned hosted URL in a daily snapshot table

Async batch report generation

Reporting platforms that build hundreds of PDF reports per day can queue work via /render/pdf/async and let Doppio call back to a webhook when each render completes. Async mode decouples request lifetime from render time, which is useful for reports built from large data tables. Each job is identified by a request ID returned in the initial response.

POST to /render/pdf/async with the report HTML and a webhook URL, store the returned job ID, and resolve the resulting PDF when the webhook fires

Agent-driven page capture via Jentic

An AI agent can capture a screenshot or PDF of any URL by searching Jentic for the Doppio render operation, loading the input schema, and executing with the URL plus desired output mode. Jentic stores the API key in the vault so the agent can render without ever seeing the raw token. This is useful for agents producing visual proofs, audit trails, or content briefs.

Search Jentic for 'render a web page to PDF', load the Doppio /render/pdf/sync schema, execute with a target URL, and return the hosted PDF link

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for doppio render api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/render/pdf/direct

Render a PDF and stream the binary response

POST

/render/pdf/sync

Render a PDF and return a hosted URL

POST

/render/pdf/async

Queue an async PDF render with webhook callback

POST

/render/screenshot/direct

Capture a screenshot and stream the binary response

POST

/render/screenshot/sync

Capture a screenshot and return a hosted URL

POST

/render/screenshot/async

Queue an async screenshot render with webhook callback

POST

/render/pdf/direct

Render a PDF and stream the binary response

POST

/render/pdf/sync

Render a PDF and return a hosted URL

POST

/render/pdf/async

Queue an async PDF render with webhook callback

POST

/render/screenshot/direct

Capture a screenshot and stream the binary response

POST

/render/screenshot/sync

Capture a screenshot and return a hosted URL

Why though Jentic?

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

Credential isolation

The Doppio API key is stored encrypted in the Jentic vault and attached to the Authorization header at execution time. Agents reference the credential by ID and never see the raw key in prompts or logs.

Intent-based discovery

Agents search Jentic by intent — for example 'render a web page to PDF' — and receive the matching Doppio operation with its URL/HTML and viewport input schema, ready to execute.

Time to first call

Direct Doppio integration: half a day for auth, mode selection, and webhook setup. Through Jentic: under 30 minutes — search the intent, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Browserless

Browserless exposes a fuller headless-Chrome API including scripted automation, while Doppio focuses on PDF and screenshot rendering

Choose Browserless when the workflow needs Puppeteer-style scripting; choose Doppio for simple URL-or-HTML to PDF/screenshot conversions

Alternative

PDF.co

PDF.co covers HTML-to-PDF plus PDF parsing and form-filling; Doppio focuses on rendering URLs and HTML to PDF or screenshot

Choose PDF.co when the workflow also needs PDF parsing, OCR, or form-filling; choose Doppio for pure URL/HTML to PDF or screenshot rendering

Alternative

HTML2PDF

HTML2PDF is another HTML-to-PDF conversion service with simpler options than Doppio's three render modes

Choose HTML2PDF for the simplest possible HTML-to-PDF call; choose Doppio when you need screenshots, viewport control, or async webhook delivery

Complementary

Docupilot API

Docupilot merges JSON into Word/Google Docs templates; Doppio captures arbitrary HTML or URLs as PDF

Use Docupilot for template-driven business documents (contracts, invoices); use Doppio when the source is a live web page or hand-written HTML

FAQs

Specific to using Doppio Render API API through Jentic.

Why is there no official OpenAPI spec for Doppio Render API?

Doppio does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Doppio Render API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Doppio Render API use?

Doppio uses an API key passed in the Authorization header. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected at execution time, so an agent never holds the raw token in its context.

What is the difference between direct, sync, and async render modes?

Direct mode (`/render/pdf/direct`, `/render/screenshot/direct`) streams the binary file back in the same response. Sync mode (`/render/pdf/sync`, `/render/screenshot/sync`) returns a hosted URL pointing to the rendered file. Async mode (`/render/pdf/async`, `/render/screenshot/async`) queues the job and POSTs the result to a webhook on completion — best for large or slow renders.

Can I render a JavaScript-heavy SPA with the Doppio Render API?

Yes. All render endpoints accept a waitFor selector and a timeout so the headless Chromium pool waits for client-side rendering to finish before capturing the page. Pair this with a viewport configuration to match desktop or mobile breakpoints.

What are the rate limits for the Doppio Render API?

The OpenAPI spec does not declare explicit rate limits. Throughput is governed by your Doppio plan's concurrent-render allowance; bursting beyond that returns 429. For batch workloads, prefer the async endpoints to smooth concurrency over time.

How do I render a PDF with the Doppio Render API through Jentic?

Install the SDK with `pip install jentic`, then search Jentic for `render a web page to PDF`. Load the schema for /render/pdf/sync, populate the URL or HTML and any viewport options, and execute. Jentic returns the hosted PDF URL with no need to handle the API key directly.