Skip to main content

Overview

Webhooks notify your server when asynchronous operations complete — batch jobs finishing, large renders completing, or async conversions wrapping up. All webhook payloads are signed with HMAC-SHA256 so you can verify they came from PDFBase.

Setup

Configure webhook endpoints in your dashboard or via the API:
Store the secret securely. It’s only returned once at creation time. You’ll need it to verify webhook signatures.

Webhook payload

Verifying signatures

Every webhook request includes a PDFBase-Signature header:
Verify it by computing HMAC-SHA256 of {timestamp}.{raw_body} using your webhook secret:

Event types

Phase 1 (Launch)

Phase 2

Phase 3

Retry behavior

Failed webhook deliveries are retried with exponential backoff: After 5 failed attempts, the event is marked as failed and visible in your dashboard. You can manually retry from there. A delivery is considered failed if your endpoint:
  • Returns a non-2xx status code
  • Doesn’t respond within 15 seconds
  • Has a connection error

Testing webhooks

Use the dashboard’s Send test event button to fire a sample payload to your endpoint. Or use the CLI: