Skip to main content

Choose a Template Contract Flow

Goal​

Choose the right template-contract recipe before you start implementation.

Overview​

This page is a routing guide, not the canonical implementation doc. Use it to decide which detailed recipe matches the operational outcome you want.

Endpoints used​

  • POST /api/v2.1/public/contracts/
  • POST /api/v2.1/public/contracts/{composite_id}/send_to_counterparties

Prerequisites​

  • a valid public API key
  • a template-backed contract flow in SpotDraft
  • a clear choice between create-only and straight-to-signature behavior

When to use this​

Use this when your contract starts from SpotDraft template data rather than from uploaded third-party paper or an already executed file.

Choose the right path​

Use Create a Template Contract and Sync Data Back when:

  • your integration creates the contract from structured source data
  • the contract may still go through review or human steps in SpotDraft
  • you mainly need a reliable create flow plus downstream sync

Use Create a Template Contract and Send It for Signature when:

  • your workflow is straight-through and should advance to signature immediately
  • your system already has the correct signatories and required inputs
  • you do not want an operator to open SpotDraft just to send the contract

Canonical implementation guides​

Common mistakes​

  • starting with contract creation before identifying the right contract type or template workflow
  • assuming the source-system payload already matches the questionnaire fields configured in SpotDraft
  • treating lifecycle sync as polling-first instead of webhook-first

Production notes​

  • Treat this page as the chooser and the linked implementation pages as the operational source of truth.

Common failure points​

  • choosing the signature path before validating signer and template requirements A straight-through signature flow has stricter payload and workflow assumptions than a create-first flow.