Developers

Build on a data-first signing platform

AppliFlo treats your data as the starting point. Here's how the connector model works — and an honest map of what's shipped versus planned.

The connector model

Data-first by design

AppliFlo starts from your records — connectors feed the auto-fill engine directly.

Connector model

Sources plug in as connectors. CSV and the Globaly platform are live today.

Secure by default

Data is encrypted in transit and at rest, with PAdES signing on every document.

API & connectors: shipped vs roadmap

We won't ship fake SDK badges. This is the real state today.

  • CSV data importShipped
  • Globaly platform connectorShipped
  • Public REST API for documents & envelopesRoadmap
  • API keys & token authRoadmap
  • Webhooks for signing eventsRoadmap
  • Third-party CRM connectors (Salesforce, HubSpot)Roadmap

Quickstart (outline)

Today, the fastest path is the product itself: create a workspace, connect a data source (CSV or Globaly), upload a document, and let field auto-detection and auto-fill do the work before you route it for signature.

A public REST API with token auth and webhooks is on the roadmap. When it ships, this page will carry the real reference and a working quickstart — not before.

Start with what's shipped today

Connect CSV or Globaly and send your first document.

Get started free