CloudLayer Document Generation API
Agent-ready OpenAPI document · curated by JenticMediaImage ProcessingapiKey12 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Render PDFs and images from HTML strings, public URLs, or stored templates on CloudLayer using an X-API-Key header.
Use for: Render an HTML invoice to PDF, I want to take a PNG screenshot of a public URL, Generate a PDF from my saved template with customer data, Get the status of CloudLayer job ID xyz
Not supported: Does not OCR existing PDFs, edit existing PDFs, or convert non-HTML source formats - use for HTML-, URL-, and template-based PDF and image rendering only.
Jentic publishes the only available OpenAPI specification for CloudLayer Document Generation API, keeping it validated and agent-ready. CloudLayer turns HTML, URLs, and templates into PDFs and images via a REST API. The v2 surface adds asynchronous job processing and asset storage, so callers can submit a render request, get back a job ID, and pick up the rendered file later - useful when generating long PDFs that exceed a single HTTP timeout. Authentication is an X-API-Key header.
Install Jentic One Beta
Connect the CloudLayer Document Generation API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CloudLayer Document Generation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcloudlayer.io%2Fcloudlayer" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcloudlayer.io%2Fcloudlayer" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with CloudLayer Document Generation API.
Render an HTML string to PDF via /html/pdf
Render a public URL to PDF via /url/pdf with optional page selectors
Generate a PDF from a stored template and JSON data via /template/pdf
Render HTML, URL, or template to PNG or JPG image via the /image endpoints
Manage asynchronous render jobs and retrieve completed assets
Inspect account details and remaining usage at /account
Use Cases
Patterns agents use CloudLayer Document Generation API for, with concrete tasks.
★ Invoice and Receipt PDF Generation
Generate transactional PDFs such as invoices, receipts, and order confirmations from server-rendered HTML. POST /html/pdf with the HTML string and any header/footer markup, and CloudLayer returns the rendered PDF either inline or as a job ID for async pickup. Avoids running headless Chromium in production.
POST /html/pdf with the rendered invoice HTML and pageMargin settings, then download the PDF or poll the job ID.
Web Page Screenshots
Capture screenshots of public web pages for monitoring, social previews, or change-detection alerts. POST /url/image returns PNG or JPG, while POST /url/pdf returns the same page as a multi-page PDF. Useful when an app needs to embed a snapshot of an external page in a report.
POST /url/image with url=https://example.com/dashboard and format=png to capture a screenshot for the daily digest email.
Template-Based Document Generation
Store reusable templates (contracts, certificates, statements) and render them with per-customer data. /template/pdf and /template/image accept a template ID and a JSON data block, applying the data via the template's placeholders. Keeps document layout under design control instead of inline HTML.
POST /template/pdf with templateId=cert-2026 and data={ name, course, date } to render the completion certificate.
AI Agent Document Rendering
Let a Jentic-powered agent render documents on demand. The agent searches Jentic for 'render HTML to PDF', loads the CloudLayer createPdf operation, and executes it with the HTML and options. The X-API-Key stays in your Jentic One instance.
Search Jentic for 'render HTML to PDF', load the CloudLayer htmlToPdf operation, and execute with the agent-generated HTML.
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for cloudlayer document generation api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/html/pdf
Render HTML to PDF
POST
/url/pdf
Render a URL to PDF
POST
/template/pdf
Render a stored template to PDF
POST
/html/image
Render HTML to PNG or JPG
POST
/url/image
Render a URL to PNG or JPG
GET
/jobs/{jobId}
Get the status of a render job
GET
/assets
List stored render assets
GET
/account
Get account information and usage
POST
/html/pdf
Render HTML to PDF
POST
/url/pdf
Render a URL to PDF
POST
/template/pdf
Render a stored template to PDF
POST
/html/image
Render HTML to PNG or JPG
POST
/url/image
Render a URL to PNG or JPG
GET
/jobs/{jobId}
Get the status of a render job
GET
/assets
List stored render assets
GET
/account
Get account information and usage
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the CloudLayer Document Generation API by hand means adding your X-API-Key header on every request and pointing the render calls at api.cloudlayer.io/v2 yourself. Through Jentic you install once, import the CloudLayer Document Generation API from the API Directory, store the key once, and your agent calls it.
Permission scoping
CloudLayer names the render source in the request body rather than pinning one id in the URL path, so scope the agent by the operations it needs, such as rendering HTML to PDF or capturing a URL screenshot. You choose that set, so operations like reading account details or listing assets are only in reach if you include them.
Credential isolation
Your CloudLayer X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'render HTML to PDF' or 'screenshot a URL', and Jentic returns the matching CloudLayer operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CloudLayer Document Generation API through Jentic.
Why is there no official OpenAPI spec for CloudLayer Document Generation API?
CloudLayer does not publish a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CloudLayer Document Generation API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the CloudLayer Document Generation API use?
The API uses an X-API-Key header. Generate the key in the CloudLayer dashboard and pass it on every request. Through Jentic, the key is stored encrypted in the vault and never enters the agent's context.
Can I render long PDFs without hitting an HTTP timeout?
Yes. v2 supports asynchronous processing - POST /html/pdf or /url/pdf returns a job ID, and GET /jobs/{jobId} reports the status. The rendered PDF is then available under /assets, which avoids long-lived synchronous connections for heavy documents.
How do I capture a screenshot of a URL?
POST /url/image with the target URL and format (png or jpg). Optional fields include viewport width and height, full-page capture, and wait selectors so the screenshot fires after a specific element is rendered.
How do I render an HTML invoice through Jentic?
Run jentic search 'render HTML to PDF', load the CloudLayer htmlToPdf operation, and execute with the HTML body and any margin, header, or footer options. Jentic handles the X-API-Key from the stored credential.
Does CloudLayer support PDF templates?
Yes. Store templates in the CloudLayer dashboard, then call POST /template/pdf with the template ID and a JSON data object. The template's placeholders are filled in at render time, keeping layout decisions out of application code.
Can I limit what my agent is allowed to do with the CloudLayer Document Generation API?
Yes. Because Jentic One is self-hosted, you decide which CloudLayer operations and credentials your agent can use. Since CloudLayer names the render source in the request body rather than in the URL path, you scope the agent by the operations it needs, such as rendering HTML to PDF at POST /html/pdf or capturing a URL screenshot at POST /url/image. Read-only operations like inspecting account usage at GET /account or listing stored assets at GET /assets are only in reach if you choose to include them.
GET STARTED