← All integrations

PDFMonkey

12 operations2 webhooks

PDF generation API for creating documents from HTML templates and dynamic data.

Supported operations

  • Create DocumentWrite

    Create a document and queue it for PDF generation

  • Create Document SyncWrite

    Create a document and wait for generation to complete

  • Delete DocumentDestructive

    Delete a document [DESTRUCTIVE · IRREVERSIBLE]

  • Get DocumentRead-only

    Get a full document including payload and generation logs

  • Get Document CardRead-only

    Get a document card with status and download URL

  • List Document CardsRead-only

    List document cards with pagination and filters

  • Update DocumentWrite

    Update a document's payload, metadata, or template

Supported triggers

  • Generation Failure

    A document failed to generate

  • Generation Success

    A document finished generating successfully

FAQ

Install corsair and @corsair-dev/pdfmonkey, add the PDFMonkey plugin, and connect with an API key. Then call methods like corsair.pdfmonkey.api.documents.createDocument() from your app. Corsair verifies webhooks, and keeps each tenant isolated.

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

Teams use Corsair for pdf generation api for creating documents from html templates and dynamic data. Common builds include sync jobs, admin tooling, and agents that call PDFMonkey APIs from your backend. Webhook handlers react to PDFMonkey events and fan out to Slack, email, or other plugins in the same tenant.

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 PDFMonkey 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/pdfmonkey in the open repo. When PDFMonkey 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 PDFMonkey data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store PDFMonkey data on your behalf.