AsyncAPI channel · PandaDoc · PandaDoc Webhook Events

/webhook

The HTTPS endpoint on the subscriber's server that receives webhook notifications from PandaDoc. PandaDoc sends HTTP POST requests with JSON array payloads containing one or more event objects. The receiver must respond with a 2xx HTTP status code to acknowledge delivery. Payloads are signed with the subscription shared key via HMAC-SHA256 delivered in the x-pd-signature request header.

Provider: PandaDoc AsyncAPI: v2.6.0 Spec: PandaDoc Webhook Events Operations: 1 Messages: 13

Channel address

/webhook

Operations

publish
receivePandaDocWebhookEvent
Receive a webhook event notification from PandaDoc

Messages

document_state_changed
Notification sent when a document transitions to a new lifecycle status such as sent, viewed, completed, declined, or voided.
Content-Type: application/json
recipient_completed
Notification sent when an individual recipient completes all required actions on a document such as signing all assigned fields.
Content-Type: application/json
document_updated
Notification sent when a document's content or metadata is modified, such as when fields are updated or tokens are changed while the document is in draft.
Content-Type: application/json
document_deleted
Notification sent when a document is permanently deleted from the PandaDoc workspace.
Content-Type: application/json
document_creation_failed
Notification sent when asynchronous document creation fails, such as when a file upload or template generation encounters an error.
Content-Type: application/json
document_completed_pdf_ready
Notification sent when the signed PDF for a completed document has finished generating and is ready to download.
Content-Type: application/json
document_section_added
Notification sent when a new section is successfully added to a document bundle via asynchronous upload.
Content-Type: application/json
quote_updated
Notification sent when pricing table or quote data within a document is updated.
Content-Type: application/json
template_created
Notification sent when a new template is successfully created in the workspace.
Content-Type: application/json
template_updated
Notification sent when an existing template is modified.
Content-Type: application/json
template_deleted
Notification sent when a template is permanently deleted from the workspace.
Content-Type: application/json
content_library_item_created
Notification sent when a content library item finishes processing and is ready for use in documents.
Content-Type: application/json
content_library_item_creation_failed
Notification sent when a content library item upload fails during processing.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel
curl "https://apis.io/api/v1/channels/webhook"
All event channels
curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.