HTML to Image

Install corsair and @corsair-dev/htmltoimage, add the HTML to Image plugin, and connect with an API key. Then call methods like corsair.htmltoimage.api.account.checkUsage() from your app. Corsair syncs data per tenant.

Yes. HTML to Image requires an API key from your HTML to Image 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 HTML to Image, GitHub, Notion, Stripe, and the rest. Trigger HTML to Image from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for screenshot api for converting html, urls, and templates into png or jpeg images. Common builds include sync jobs, admin tooling, and agents that call HTML to Image APIs from your backend. Local DB entities let you query synced HTML to Image 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 HTML to Image 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/htmltoimage in the open repo. When HTML to Image 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 HTML to Image data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store HTML to Image data on your behalf.