Authenticate with the Conga Sign API using API key or OAuth as documented, obtaining a session token
Create a transaction via the transactions POST endpoint, specifying a document file and a signerGroups array that mixes sequential groups (ordered by sequence number) and parallel groups (sharing the same sequence number) to implement a hybrid routing pattern
For each signer in each group, define the required signature fields by position (page, x, y coordinates) or by anchor text string, and set any required fields (date, initials, text fields) alongside the signature placeholder
Submit the transaction to trigger delivery of signing invitations to the first sequential group (or all members of the first parallel group simultaneously)
Subscribe to Conga Sign webhook events or poll the transaction status endpoint to detect completion, then call the document download endpoint to retrieve the signed PDF with embedded audit trail
Known gotchas
Conga Sign's parallel group implementation requires all members of a parallel group to sign before the routing advances to the next sequential group; a single non-responsive signer in a parallel group blocks the entire transaction from advancing
Anchor-text-based field placement in Conga Sign is sensitive to the exact whitespace and character encoding of the anchor string in the PDF; PDFs that were generated from DOCX via conversion may have different internal text encoding than visually identical PDFs produced natively, causing anchors to fail to match
Conga Sign is a distinct product from Conga Composer; the API credentials, base URLs, and authentication flows are separate and cannot be shared between the two products even within the same Conga platform subscription
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp