API2PDF

Install corsair and @corsair-dev/api2pdf, add the API2PDF plugin, and connect with an API key. Then call methods like corsair.api2pdf.api.chrome.addHeaderFooter() from your app. Corsair syncs data per tenant.

Yes. API2PDF requires an API key from your API2PDF account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit API2PDF, GitHub, Notion, Stripe, and the rest. Trigger API2PDF from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for html and url to pdf conversion api for generating documents from web content. Common builds include sync jobs, admin tooling, and agents that call API2PDF APIs from your backend. Local DB entities let you query synced API2PDF records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per API2PDF API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/api2pdf in the open repo. When API2PDF ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your API2PDF data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store API2PDF data on your behalf.