Overview

Use the Oneflow API to create, send, track, and sign contracts from your business tools and systems.

You can build a workflow for one account or an integration used by several customers. The three types below describe common projects. They use the same integration model.

Start with Integrations - Introduction to learn how Blueprints and Playbooks connect your application's fields to Oneflow contract data.

Standard integration

Build a standard integration for a specific task in one Oneflow account. Your code can supply the required values or collect them from a form.

For example, create a contract when someone submits a web form or completes a signup process.

Follow Quick start: Blueprints and Playbooks to set up and test the workflow.

Application integration

Build an application integration to connect one customer's CRM, ATS, or another system to Oneflow. Users can select a workspace and template, then create a contract using data from that system.

See Core building blocks for the setup components and Key concepts for how data moves between systems.

Partner integration

Build a partner integration when several customers need to connect your application to their own Oneflow accounts. Each customer has their own setup and account-specific IDs.

Read Partner integration for the basics, then follow Building a partner integration.

Updating an existing integration

See Migrating from the legacy integration framework to choose your path. Follow Migration guide for the detailed steps.