ToroDocs for Developers

Legally-binding e-signature, by API.

Add real, ESIGN/UETA-compliant signing to your product in an afternoon. Pay-as-you-go — $1.50 per signature invite, no base fee, no monthly minimum, no wasted allowance. The API is the product.

A payment method is required so usage can bill — you're only charged for invites you actually send.

Developer is API-only — you send programmatically. For manual, click-to-send in the app, see our subscription plans.

$1.50
per signature invite
$0
monthly base
$0
monthly minimum
volume — never capped

Usage aggregates into a single monthly invoice. No per-charge noise, no seat licenses.

Why build on ToroDocs

Pay-as-you-go

No base fee, no monthly minimum, no allowance to waste. Send one invite this month or ten thousand — you pay $1.50 each, and nothing when you're idle.

Full REST API

Templates, field_key merge-field prefill, sequential or parallel routing, webhooks for lifecycle events, and sealed-PDF retrieval. Everything the product does, programmatically.

Same tamper-evident seal

API-sent documents get the identical flatten + digital signature + SHA-256 seal, Certificate of Completion, full audit trail, and public /verify page. No "API-lite" tier.

Built for integrations

Idempotency keys so retries never double-send, per-token rate limits, read/write token scopes, and a JSON envelope with predictable error codes.

Transparent pricing

SignNow's developer rate runs up to $3.50 per invite. ToroDocs is $1.50, flat — the same rate as our overage, no volume games.

Legally binding

ESIGN & UETA compliant: electronic-records consent, attribution, and a court-ready audit trail on every completed document.

How the integration works

  1. 1
    Create a ToroDocs account

    Sign up and subscribe to the Developer plan — a card on file so usage can bill.

  2. 2
    Build a template + name your fields

    Upload your document once, drag on fields, and give each a field_key (e.g. client_name) so you can merge values in later.

  3. 3
    Generate an API token

    Mint a team-scoped bearer token from your account (read/write scopes).

  4. 4
    POST an envelope

    Call POST /api/v1/envelopes with your template id, recipients, and fields: { field_key: value } to prefill. Get back signing links.

  5. 5
    Get the signed, sealed PDF

    A envelope.completed webhook fires when everyone signs — then pull the sealed PDF (with its Certificate of Completion) via the API.