Skip to content

Ship document flows in an afternoon

One API key gives you the REST API and the MCP server. Send a PDF and values. Get back a filled PDF and a line for every field saying what happened.

  • On the Business plan
  • Same key, REST or MCP
  • Keys hashed, shown once
  • Live

    REST API

    Upload, detect, fill, send for signing, templates and bulk send. 28 routes and an OpenAPI spec.

    POST /api/v1/fillSee the endpoints
  • Live with an API key

    MCP server

    The same work as 20 tools, for Claude Code and any MCP client that sends your key as a header.

    /api/mcpConnect a client
  • Coming soon

    Embed SDK

    Signing and form filling inside your own app, with your brand.

    Join the waitlist

Key to working call in 60 seconds

No setup beyond a key. AppliFlo finds the fields, fits each value and returns the PDF.

  1. 1
    Make a keyIn Settings, under API keys. It is shown once.
  2. 2
    Send a PDF and valuesValues are keyed by the label printed on the form.
  3. 3
    Read the resultsEvery field says filled, formatted, overflowed or skipped.
Quickstart
# 1 · connect any MCP client that sends a header
claude mcp add appliflo --transport http <APP_URL>/api/mcp --header "Authorization: Bearer aflo_live_..."

# 2 · call a tool (values keyed by field_id from detect_fields)
> fill_document({ document_id: "doc_8f2a", values: {
    fld_name: "Alexandra Whitfield-Harrington",
    fld_movein: "2026-08-01" } })
POST /api/v1/fill · application.pdf
  1. filledApplicant full nameAlexandra Whitfield-Harrington8 pt, shrunk to fit
  2. formattedMove-in date08/01/2026from 2026-08-01
  3. filledSocial security no.9 of 9 boxescomb field
  4. overflowedEmployer addressnot stampedtoo long for the box
  5. skippedGuarantor phoneno value sentleft blank

The overflowed row is the point. Your code sees what did not fit and can ask a person, instead of sending a wrong form.

Your agent can do everything you can

Add the MCP server to Claude Code, or any MCP client that sends your key as a header. The agent uploads, reads, fills and sends for signing with the same tools. Sending or voiding needs confirm: true: without it, nothing is sent and the agent gets back what would go and to whom, to check with you.

Sign-in from Claude.ai and ChatGPT is coming soon. AppliFlo in AI apps

  • upload_document
  • detect_fields
  • list_fields
  • correct_field
  • fill_document
  • fill_form_oneshot
  • send_envelope
  • list_envelopes
Example session · Claude Code
claude mcp add appliflo --transport http <APP_URL>/api/mcp --header "Authorization: Bearer aflo_live_..."> fill lease-2026.pdf with tenants.csv row 2 ↳ upload_document → doc_8f2a ↳ detect_fields → 14 fields · 1 flagged ↳ fill_document ✓ 13 filled · 1 formatted (date → MM/DD/YYYY) ⚠ guarantor_phone: needs a human (no value in row 2)> send it to both tenants for signature ↳ send_envelope → not sent yet: 2 signers, needs confirm> yes, send it ↳ send_envelope { confirm: true } → env_8f2 · 2 signers · awaiting

Endpoints

The routes most integrations start with. Where an MCP tool does the same job, its name is on the right.

REST endpoints, and the MCP tool that does the same job
MethodPathMCP tool that does the same job
POST/api/v1/documentsUpload a PDF and create a document.upload_document
POST/api/v1/documents/:id/detectDetect fields: typed, with confidence and flagged status.detect_fields
GET/api/v1/documents/:id/fieldsList a document’s current fields.list_fields
PATCH/api/v1/documents/:id/fields/:fieldIdCorrect a field’s label, type, semantic type, or box.correct_field
POST/api/v1/documents/:id/fillFill a persisted document’s fields with values.fill_document
POST/api/v1/fillOne-shot: PDF + values in, filled PDF out. No document_id needed.fill_form_oneshot
POST/api/v1/documents/:id/sendRoute a filled document for signature. Each signer is emailed a code to enter before signing unless you pass accessCode "none".send_envelope
GET/api/v1/envelopesList envelopes and their status.list_envelopes
GET/api/v1/openapi.jsonThe OpenAPI spec for the v1 API.None

Envelopes, templates and bulk send have routes too: 28 in all. Routing a document for signature is not legal advice. Check your own compliance needs before sending contracts.

Limits, keys and errors

The numbers your integration should plan for.

  • 120 / minPer key

    Requests a minute for each API key.

  • 20 / minShared pool

    Across detect, fill and send, per key.

  • 1×Scoped keys, shown once

    Each key can read, create drafts, or send and void, and can expire. Outside its scopes a call gets 403 insufficient_scope. We store only a SHA-256 hash.

  • 402Business plan

    The API and MCP with a key are on the Business plan. On other plans a call gets 402 plan_feature. Keys made before this rule keep working.

  • ai_pagesAI pages count the same

    Reads through the API count like any other. Past the limit a read still answers, with built-in fillable fields only, and flags ai_pages.exhausted.

  • 422One key, one request

    An Idempotency-Key replays its first response for 24 hours. Reused with a different request, it answers idempotency_key_reused.

Coming soon

Not live yet. Join the waitlist and we will email you when each one opens.

Coming soon

Sign in from Claude and ChatGPT

Add AppliFlo in Claude.ai or ChatGPT and sign in with your AppliFlo account. No key to copy, on every plan.

AppliFlo in AI apps
Coming soon

Webhooks

Your server hears when a document is signed, without polling.

Coming soon

Embed SDK

Signing and form filling inside your own app, with your brand.

Tell me about

One email when each ships. No newsletter.

Your first call, in 60 seconds.

One key for REST and MCP, on the Business plan. Every account starts on Free; upgrade to Business in Settings → Billing.