Documenso Rate Limits

Documenso Rate Limits

Output

• A rate-aware document/signing integration with bounded concurrency, idempotency, backoff, monitoring, and replay ownership.
• A safe throttle/recovery receipt that avoids duplicate invitations, duplicate signatures, or accidental document changes.

Examples

Exercise a development API with synthetic documents at controlled concurrency, retain stable idempotency keys, and record aggregate 429/latency/completion results. Back off with jitter on throttling; do not retry document creation or signature actions without verifying their current state.

Overview

Documenso uses a fair-use rate limiting model. There are no published per-minute request quotas -- instead, limits are based on your plan's document allowance and general API fair use. The paid plans (Individual and Team) include unlimited signing and API volume. The free plan has a document limit. If you hit a 429, implement exponential backoff and request queuing.

Prerequisites

• Documenso SDK installed
• Understanding of async/await patterns
• Completed documenso-install-auth setup

Documenso Fair Use Model

Documenso explicitly does not price API usage -- they want developers to build on the platform without API cost concerns. The practical limit is abusive traffic patterns (thousands of requests per second).

Instructions

Step 1: Exponential Backoff with Jitter

// src/documenso/retry.ts
interface RetryConfig {