Skip to main content

SpotDraft to ERP Integration

This page is a pattern guide, not a guarantee of built-in product behavior. It describes an ERP-style integration model that fits the public contract, metadata, download, and webhook APIs.

Where this pattern fits​

Use this guide when SpotDraft should integrate with procurement, finance, or vendor-management workflows owned by an ERP or adjacent source-to-pay system.

If a standard integration may already fit, check SpotDraft integrations first. The public integrations page includes source-to-pay examples.

Public API capabilities this pattern relies on​

This pattern makes sense because the public API supports:

  • contract creation and status retrieval
  • external_metadata correlation
  • contract downloads and download links
  • webhook-triggered downstream processing
  1. store ERP ids in external_metadata
  2. create contracts from ERP-triggered business events
  3. subscribe to execution or other downstream-relevant webhooks
  4. fetch contract metadata and executed files after the contract reaches the required state
  5. update ERP records with the SpotDraft contract id and final metadata

How the systems typically talk​

ERP or procurement event
  -> SpotDraft create contract API
  -> SpotDraft review / signature / execution workflow
  -> webhook event delivery
  -> ERP status, metadata, or document update

Typical systems and triggers​

Common triggers include:

  • vendor onboarding
  • purchase-request approval
  • procurement workflow milestones
  • finance-driven paper generation or execution checkpoints

Good keys to persist​

  • vendor id
  • purchase order number
  • ERP contract record id
  • business unit or legal entity id

Operating model​

ERP integrations are usually strongest when they combine:

  • synchronous API calls for contract initiation
  • metadata for durable cross-system correlation
  • webhook-driven updates for status and execution milestones
  • downstream document sync for finance or procurement records when needed

API and webhook roles​

ERP integrations typically use:

  • contract creation and retrieval APIs
  • metadata fields for procurement or finance identifiers
  • webhook events for execution or status transitions
  • document retrieval APIs when final files must be archived or attached downstream

Avoid​

  • trying to infer ERP linkage from contract title text
  • running full ERP-to-SpotDraft backfills without pagination and throttling
  • letting file-transfer logic block the initial contract creation path