Build PDF workflows with a predictable API.

Overview

DocuForge exposes a REST API for authentication, template management, rendering, assets, billing, and AI-assisted edits. All authenticated endpoints require a JWT in the Authorization header.

Authentication

Production renders use API keys instead: send the key via the X-API-Key header when calling /v1/render.

X-API-Key: docu_live_your_api_key

Quick start

Render a production PDF from a published template ID and JSON data.

curl -X POST "$DOCUFORGE_API_URL/v1/render" \
  -H "X-API-Key: $DOCUFORGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "template_id": "tpl_live_123", "data": { "invoice_id": "1234" } }' \
  --output document.pdf

Rendering

Production rendering endpoints are available under the consumer API surface.

Errors

The API returns JSON errors with a stable shape. Use the error code to map UI states.

Security and Governance

DocuForge ships with practical defaults for authentication, request safety, and webhook integrity.

• TLS transport, authenticated APIs, and hardened defaults help teams clear security reviews without custom hardening projects.
• Password-protected PDF delivery is built in for regulated workflows handling sensitive documents.
• Credential and token handling defaults are designed to reduce leakage risk across render, billing, and webhook paths.
• JWT and API-key auth paths are isolated by endpoint intent.
• Stripe webhook signatures are verified before billing events are processed.
• Outbound webhooks are signed with HMAC SHA-256 and retried with backoff.
• Webhook URL creation enforces HTTPS in production.
• Plan-aware rate limiting protects render, preview, and AI endpoints.
• Validation middleware enforces request schemas with predictable error payloads.
• Auth, billing, usage, and render mutation routes are explicitly non-cacheable.
• MCP server access requires bearer token auth and optional allowed-origin checks.

MCP Integration

Connect DocuForge to MCP-enabled clients to generate PDFs through tool calls and structured workflows.