The best and easiest HTML-to-PDF API
The best and easiest HTML-to-PDF API On Nagent, DocRaptor is exposed as a fully-configurable developer tools integration that any agent can call — 10 actions, and API key authentication. No code is required to wire DocRaptor into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use DocRaptor to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire DocRaptor into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against DocRaptor, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCRAPTOR_CREATE_ASYNC_DOCTool to create documents asynchronously from HTML content. Use when generating PDF, XLS, or XLSX documents and you need to poll for completion status or use a callback URL for notification. Returns a response containing an `id` field — store this value and pass it to DOCRAPTOR_GET_ASYNC_DOC_STATUS to poll for completion, then to DOCRAPTOR_GET_ASYNC_DOC to download the finished document.
Input parameters
Custom metadata for storage and tracking.
Request support assistance with this document.
Identifier for the document.
Enable test mode which adds a watermark to the document.
Validation mode - must be one of: html, none.
Specific DocRaptor Pipeline version to use.
HTTP referrer header value to use when fetching assets.
Enable DocRaptor JavaScript parsing.
POST endpoint URL for completion notification.
URL to fetch HTML content from. Alternative to document_content.
Document format - must be one of: pdf, xls, xlsx.
Advanced rendering configuration options for PrinceXML.
HTML content to transform. Required unless document_url is provided. Mutually exclusive with `document_url` — supplying both causes a validation failure.
ISO 8601 datetime when hosted document expires.
Maximum number of downloads allowed for hosted document.
Continue processing if asset loading fails.
Prevent console.log from interrupting rendering.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_CREATE_DOCTool to create a PDF or Excel document synchronously from HTML content or URL. Use when you need to generate a document file from HTML data. The document is returned immediately as a downloadable file. Either document_content or document_url must be provided, but not both.
Input parameters
A field for storing a small amount of metadata with this document.
Request support help with this request if it succeeds (default: false).
A name for identifying your document.
Enable test mode for this document (adds watermark). Set to false for production documents.
HTML validation mode - none or html.
Specify a specific version of the DocRaptor Pipeline.
Set HTTP referrer when generating this document.
Enable DocRaptor JavaScript parsing (default: false).
POST URL for async completion notifications.
The URL to fetch the HTML data to be transformed. Required if document_content is not provided. Mutually exclusive with document_content.
Output format - pdf for PDF documents, xls for Excel 97-2003, or xlsx for modern Excel.
Advanced rendering configuration options for PrinceXML engine.
The HTML data to be transformed into a document. Required if document_url is not provided. Mutually exclusive with document_url.
ISO 8601 datetime when hosted document becomes unavailable.
Number of times a hosted document can be downloaded.
Failed loading of images/javascripts/stylesheets/etc will not cause rendering to stop (default: true).
Prevent console.log from stopping document rendering (default: false).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_CREATE_DOCUMENT_FROM_REFERRERTool to convert webpages into documents using referrer-based authentication without an API key. Use when you need to generate PDFs or Excel files from registered domains without explicit API credentials.
Input parameters
Document filename to use for the generated file.
Output format for the document. Choose 'pdf' for PDF documents or 'xls' for Excel spreadsheets.
Enable JavaScript processing on the page before conversion. Set to true to execute JavaScript on the page.
CSS media type to use for rendering, such as 'screen' or 'print'. This affects which stylesheets are applied.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_CREATE_HOSTED_ASYNC_DOCTool to create a hosted document asynchronously. Use when you need to generate a PDF, XLS, or XLSX document and track its completion status via callback_url or the status API.
Input parameters
Small metadata storage field.
Requests support assistance; defaults to false.
Identifier for the document.
Enables test mode with watermark; defaults to true.
HTML validation - 'none' or 'html'.
Specifies DocRaptor pipeline version.
Sets HTTP referrer header.
Enables DocRaptor JavaScript parsing; defaults to false.
POST endpoint for async completion notifications.
URL to fetch HTML content. Alternative to document_content.
Type of output document - pdf, xls, or xlsx.
Advanced rendering configuration options for PrinceXML.
HTML data for transformation. Required if document_url is not provided.
ISO 8601 datetime for document expiration.
Maximum download count for hosted docs.
Continues rendering if assets fail; defaults to true.
Prevents console.log interruptions; defaults to false.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_GET_ASYNC_DOCTool to download a completed asynchronous document using the download URL from status response. Use when you have a download_id and need to retrieve the generated document file.
Input parameters
The download_id returned from an async status request or callback. Same id value returned by DOCRAPTOR_CREATE_ASYNC_DOC; use DOCRAPTOR_GET_ASYNC_DOC_STATUS to poll until complete before calling this tool.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_GET_ASYNC_DOC_STATUSTool to check the status of an asynchronously created document. Use when monitoring progress of async documents by polling for completion status.
Input parameters
The status_id returned when creating an asynchronous document. Returned by DOCRAPTOR_CREATE_ASYNC_DOC; store immediately as the same id is also required by DOCRAPTOR_GET_ASYNC_DOC to download the completed document.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_LIST_DOCUMENTS_JSONTool to retrieve a paginated list of previously created documents with metadata in JSON format. Use when you need to see document creation history or query past documents.
Input parameters
Specifies which page of results to return for pagination. Default is 1.
Number of documents per page to return. Default is 100.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_LIST_DOCUMENTS_XMLTool to retrieve a paginated list of previously created documents with metadata in XML format. Use when you need to see document creation history or query past documents in XML format.
Input parameters
Specifies which page of results to return for pagination. Default is 1.
Number of documents per page to return. Default is 100. Maximum is 100.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_LIST_IPS_JSONTool to get list of IP addresses that DocRaptor uses to download assets. Use when you need to know which IPs DocRaptor uses for asset downloading. Note: Using IPs for securing assets is not recommended as they can change without notice.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCRAPTOR_LIST_IPS_TEXTTool to retrieve a list of IP addresses that DocRaptor uses to download assets in plain text format. Use when you need to identify DocRaptor's IP addresses for network configuration or security purposes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 54 agents privately built on Nagent that already use DocRaptor.
Build on Nagent
Connect DocRaptor to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find DocRaptor, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, DocRaptor is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once DocRaptor is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop DocRaptor steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a DocRaptor event fires, the agent kicks off automatically.
Every DocRaptor action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While DocRaptor ships with 10 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching DocRaptor together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build DocRaptor-based workflows tailored to your business.