Skip to content

Integrating Oneflow

Auth: OAuth 2.0 · Partner program: not required · Setup time: about 20 minutes · Last verified: 2026-05-21

Swedish contract-automation platform with native e-signature. Useful when operators want the contract drafting + negotiation surface alongside signing — Oneflow renders structured contracts to PDF for signing rather than uploading pre-rendered files.

OAuth 2.0 Authorization Code grant.

  1. Oneflow account at oneflow.com.
  2. Register an OAuth application via developers.oneflow.com.
  3. Add <base-url>/auth/docsign/oneflow/callback to the redirect URIs.

Set the client credentials as the adapter’s config — on the platform’s page in the admin UI (/platforms/docsign/oneflow), or:

Terminal window
curl -X POST "$INTEGRATION_SERVER_URL/admin/platforms/docsign/oneflow/enable" \
-H "X-Admin-Secret: $ADMIN_SECRET" -H "Content-Type: application/json" \
-d '{"config":{"clientId":"...","clientSecret":"...","redirectUri":"<base-url>/auth/docsign/oneflow/callback"}}'

These are adapter settings, not environment variables: nothing reads a ONEFLOW_CLIENT_ID from .env. See OAuth adapter credentials.

Oneflow treats the contract as the envelope. The contract body (clauses, sections, fields) is structured data — but only metadata flows through the canonical schema. The rendered-PDF document is single-per-envelope.

HMAC-SHA256 in X-Oneflow-Signature (hex).

  • Contract body content (the structured clause tree)
  • Rendered PDF bytes
  • Signature images