---
title: "Frequently asked questions"
description: "Short answers about SignatureAPI pricing, test mode, limits, file types, languages, signer experience and the legal validity of electronic signatures."
canonical: "https://signatureapi.com/docs/faq"
source: "https://signatureapi.com/docs/faq.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T13:06:40Z"
---

# Frequently asked questions

Short answers about SignatureAPI pricing, test mode, limits, file types, languages, signer experience and the legal validity of electronic signatures.

_Last verified against API version 1.18.0._

Short answers to the questions we hear most, each with a link to the page that covers it in full.

## Pricing and accounts

### How much does SignatureAPI cost?

SignatureAPI charges per envelope, starting at $0.25 per envelope, with lower prices at higher volumes. See [Pricing](https://signatureapi.com/pricing) for your monthly volume.

### What counts as an envelope for billing?

Only completed envelopes, signed by all recipients, count for billing. You're not charged per document or per recipient: an envelope with two documents sent to three signers counts as one envelope. See [What is an envelope?](https://signatureapi.com/docs/glossary/envelope)

### Can I try SignatureAPI for free?

Yes. Every account gets a free test API key, and test envelopes cost nothing for as long as you use them. They send no emails and carry a watermark that makes them non-binding. See [Test mode](https://signatureapi.com/docs/api/test-mode).

### Is there a long-term contract?

No. There are no minimum terms, and you can cancel your account from the Dashboard settings at any time. For annual payment or envelope credits bought in advance, [contact us](https://signatureapi.com/contact-us).

## Signing

### Do signers need a SignatureAPI account?

No. Recipients sign from the link in their email, or inside your app when you [embed the ceremony](https://signatureapi.com/docs/embedded/introduction). They can sign from any desktop or mobile browser without creating an account.

### Can recipients sign inside my app?

Yes. Your server gets the recipient's ceremony URL from the API, and your app shows it in an iframe or a mobile WebView. See [Embedded signing](https://signatureapi.com/docs/embedded/introduction).

### Which recipient types are there?

Signers sign, approvers approve without signing, preparers fill in fields before the signers, and automatic signers apply a signature you provide without a ceremony. Qualified signers sign with a qualified electronic signature. See [Recipients](https://signatureapi.com/docs/api/resources/recipients/object).

### What do I get when an envelope completes?

A deliverable: one PDF with the signed documents and, by default, an audit log of every step. SignatureAPI seals it so any later change is visible. See [Deliverables](https://signatureapi.com/docs/api/resources/deliverables/object).

## Documents and limits

### Which file types can I send?

PDF and DOCX. A DOCX can also be a template that SignatureAPI fills with your data before signing. See [Documents](https://signatureapi.com/docs/api/resources/documents/object) and [Templates](https://signatureapi.com/docs/api/resources/documents/templates).

### What are the size and page limits?

Each envelope takes 1 to 10 documents and 1 to 10 recipients. Each document can be up to 10 MB and 100 pages, with up to 100 places. See [Document limits](https://signatureapi.com/docs/api/resources/documents/object#limits).

### How many API requests can I send?

By default, 10 requests per second per API key, with bursts of up to 10 requests. See [Rate limiting](https://signatureapi.com/docs/api/rate-limiting) for higher limits and for MCP and CLI limits.

### Which languages are supported?

The signing ceremony, emails and audit log come in English, Spanish, French, German, Italian, Portuguese (Brazil), Chinese (Simplified), Hungarian and Dutch. Set the `language` property on the envelope. See [Language](https://signatureapi.com/docs/api/resources/envelopes/language).

## Legal and security

### Are SignatureAPI electronic signatures legally binding?

Yes. Electronic signatures from SignatureAPI are legally binding under the US ESIGN Act and similar laws, such as UETA in the US and eIDAS in the EU. Some documents need a specific level or form, so check with your legal counsel. See [Are electronic signatures legal?](https://signatureapi.com/docs/legal-validity/overview)

### Does SignatureAPI support qualified electronic signatures (QES)?

Yes, in public beta, with the qualified trust service provider you choose and at no extra charge during the beta. See [What are qualified signatures?](https://signatureapi.com/docs/qualified-signatures)

### Is SignatureAPI SOC 2 compliant?

Yes. SignatureAPI is SOC 2 Type II compliant, with controls independently audited over time. See [SOC 2](https://signatureapi.com/docs/trust/compliance/soc2) and the other [compliance pages](https://signatureapi.com/docs/trust/compliance/gdpr).

## Still have a question?

Check the [glossary](https://signatureapi.com/docs/glossary), the [troubleshooting guides](https://signatureapi.com/docs/troubleshooting/email-delivery), or [contact support](https://signatureapi.com/support).
