How to connect API2PDF to OpenClaw
Connect API2PDF to OpenClaw with ClawLink: paste your API2PDF key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.


Api2Pdf is a REST API that enables developers to generate PDFs from HTML, URLs, and various document formats using engines like wkhtmltopdf, Headless Chrome, and LibreOffice.. Once connected, OpenClaw can read and act on API2PDF from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to API2PDF access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical API2PDF setup: install one ClawHub skill, connect API2PDF in the browser, and OpenClaw can call real API2PDF actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to API2PDF.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect API2PDF
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with API2PDF?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect API2PDF in the ClawLink dashboard — paste your API2PDF API key once.
Verify the connection by asking OpenClaw:
Use API2PDF to check status and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once API2PDF is connected in the dashboard, that agent calls the same 10 API2PDF tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
API2PDF MCP for OpenClaw
Looking for a API2PDF MCP server for OpenClaw? ClawLink connects API2PDF to OpenClaw and exposes 10 API2PDF tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes API2PDF integration works the same way.
What the OpenClaw API2PDF integration can do
10 API2PDF tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10.
9 of 10 API2PDF tools for OpenClaw
| Tool | What it does |
|---|---|
Check status api2pdf_check_status | Check the health status of the API2PDF service |
Zebra generate barcode api2pdf_zebra_generate_barcode | Generate barcodes or QR codes using Zebra Crossing (ZXING) |
Add header footer api2pdf_add_header_footer | Convert HTML to PDF with customizable headers and footers using Headless Chrome |
Extract pages api2pdf_extract_pages | Extract specific pages from a PDF document |
Libreoffice PDF to HTML api2pdf_libreoffice_pdf_to_html | Convert a PDF document to HTML using LibreOffice |
Libreoffice thumbnail api2pdf_libreoffice_thumbnail | Generate a thumbnail image of a document using LibreOffice |
Merge pdfs api2pdf_merge_pdfs | Merge multiple PDF documents into a single PDF file |
Optimize PDF api2pdf_optimize_pdf | Optimize a PDF document to reduce file size while maintaining quality |
Reorder pages api2pdf_reorder_pages | Reorder pages of a PDF document by specifying a new page sequence |
Try it: find the API2PDF tool you need
Browse the 9 API2PDF tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use API2PDF to check status and walk me through the result in plain English.
Use API2PDF to zebra generate barcode and walk me through the result in plain English.
Use API2PDF to extract pages and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want API2PDF working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the API2PDF API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected API2PDF account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for API2PDF. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right API2PDF actions to the runtime in a format your agent can reliably use. | 10 tools for API2PDF are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes API2PDF to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect API2PDF in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the API2PDF key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the API2PDF skill but can't call the tools
The ClawHub skill teaches OpenClaw about API2PDF, but the calls run through the ClawLink plugin and your connected account. Make sure API2PDF is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect API2PDF from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling API2PDF tools
API2PDF tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every API2PDF call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
API2PDF returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for API2PDF has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw API2PDF integration?
Yes. ClawLink is the fastest way to connect OpenClaw to API2PDF: link your API2PDF account once in the browser and OpenClaw can call the API2PDF API through 10 ready-made tools — no custom code or token handling.
How do I add API2PDF to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink API2PDF skill from ClawHub, then you click Connect in the dashboard to authorize API2PDF. OpenClaw calls the tools from the next message — no config files, and the API2PDF key you paste is stored server-side instead of in your environment.
How long does it take to connect API2PDF to OpenClaw?
About two minutes. Sign in, click Connect next to API2PDF in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring API2PDF up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want API2PDF working from chat.
OpenClaw installed the API2PDF skill but can't call the tools
The ClawHub skill teaches OpenClaw about API2PDF, but the calls run through the ClawLink plugin and your connected account. Make sure API2PDF is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
Connect SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.