Skip to main content
This page records how composerID publishes into PandaDoc: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. PandaDoc is a document-automation and eSignature platform with a clean public REST API. composerID creates documents from templates and stamps the Intent ID into the document’s metadata, which is returned on reads and webhooks.
Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: public developer portal.

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

PandaDoc Developer Docs

Developer Reference

Official API client (GitHub)

​
API posture

​
Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
PandaDoc documents accept arbitrary metadata (key-value) that is returned on reads and webhooks, so the Intent ID rides natively. Templates and roles are configured per workspace; a single-workspace integration can use an API key, while multi-workspace apps use OAuth.

​
Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.