Sign API · Beta

ToolPDFs API

PDF infrastructure for your product.

Start with mutual document signing. Create a request, email each person a private signing link, receive a webhook after both finish, and retrieve the completed PDF.

ToolPDFs Sign API

One request. Two signatures. One completed PDF.

A focused workflow for collecting mutual signatures without building document signing infrastructure yourself.

POST

Create signature request

Upload the PDF and signer details. ToolPDFs returns private signing URLs and tracks the request through completion.

  1. 01

    Upload PDF

    Send one document

  2. 02

    Create request

    Get two private links

  3. 03

    Collect signatures

    Both people sign

  4. 04

    Receive webhook

    Completion event arrives

  5. 05

    Retrieve PDF

    Download the signed copy

Private files, secure signing links, and a signed completion webhook.

View the request format →

Designed to support GDPR compliant processing with encrypted transport, private storage, secure signing sessions, retention controls, transparent service providers, and applicable safeguards for processing outside the European Economic Area. Security details

Developer dashboard

Sign in to create test keys and review signature request activity.

Sign in to ToolPDFs

API FAQ

Frequently asked questions

What does the Sign API do?

It creates a mutual signing request, gives each person a private link, and provides one completed PDF after both sign.

Are documents stored?

Yes. Signing documents are stored in private Supabase Storage and are never placed in public buckets.

When are documents deleted?

Completed files are deleted thirty days after completion. Incomplete files are deleted thirty days after the request expires.

Do signers need an account?

No. Each signer uses a private link and can finish without creating a ToolPDFs account.