api-2-pdf

Api2Pdf through One

Api2Pdf is a document generation API that converts HTML, URLs, Office files, and raw content into PDFs, screenshots, and images, allowing developers to automate document rendering, reporting, and file conversion workflows within applications and backend systems.

One exposes Api2Pdf through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform api-2-pdf if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Api2Pdf is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.

Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.

Before a write

Creates, updates, deletes and sends land on a real Api2Pdf account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.

Actions

ChromePdfUrl

Action	Method	Path	Action id
Convert URL to PDF Using Chrome	GET	/chrome/pdf/url	conn_mod_def::GLusyHJNIPM::2FdHL09ARHaK4DK0rRtyOQ
URL to PDF Using Chrome	POST	/chrome/pdf/url	conn_mod_def::GLusyRDk5A4::B-D05Cl6Q4ukw7RGNZfpIA