What happens when you hit an e-signature API rate limit?

When you exceed the rate limit, the API returns a 429 Too Many Requests HTTP status code. The response usually includes a Retry-After header indicating how many seconds to wait before the next request. Your code should catch this status, pause for the specified duration, and retry the request. Without retry logic, the document send will silently fail — meaning a contract, NDA, or offer letter never reaches the recipient.

Which e-signature API has the highest rate limit?

Signbee offers the highest documented rate limit at 1,000 requests per minute on paid plans. DocuSign allows 1,000 per hour (approximately 17 per minute). BoldSign and PandaDoc offer 300 per minute. HelloSign and Signbee's free tier allow 100 per minute. For high-volume batch signing, the effective throughput depends on both the rate limit and the per-request latency — a 2-second response time with 1,000/min limit means practical throughput of about 500 documents per minute.

May 7, 2026 · Developer Guide

E-Signature API Rate Limits: What Every Developer Should Know

Hit a 429 and your contract never arrives. Here's how to build retry logic that never drops a document — with rate limits from 6 providers compared side-by-side.

Michael Beckett

Founder, Signbee

TL;DR

Rate limits vary wildly across e-signature APIs. DocuSign allows 1,000 calls/hour (~17/min). Signbee allows 1,000/min on paid plans. Without proper retry logic, a single 429 means a contract never reaches the signer. We compared 6 providers and built a retry pattern that handles 429s, 500s, and network failures.

Why rate limits matter for e-signatures

Unlike a failed search query or a broken analytics event, a failed e-signature API call means a real document never reaches a real person. An NDA that doesn't arrive delays a deal. An offer letter that silently fails means a candidate hears nothing. A HIPAA consent form that drops means a patient can't be treated.

Rate limits are the most common cause of silent e-signature failures in production. Your code looks fine. Your tests pass. But under load — during a batch send, a quarterly invoice run, or a busy enrollment period — you exceed the limit and documents start dropping.

Rate limits by provider

Provider	Send limit	Status check limit	429 response?
Signbee (free)	100/min	200/min	Yes + Retry-After
Signbee (paid)	1,000/min	5,000/min	Yes + Retry-After
DocuSign	1,000/hour	1,000/hour	Yes
HelloSign	100/min	150/min	Yes
PandaDoc	300/min	600/min	Yes
BoldSign	300/min	500/min	Yes

For a deeper comparison of integration complexity and pricing, see our full comparison of the 6 best e-signature APIs.

The retry pattern that never drops a document

JavaScript — rate-limit-aware fetch wrapper

async function sendWithRetry(url, options, maxRetries = 3) {
  for (let attempt = 0; attempt <= maxRetries; attempt++) {
    const res = await fetch(url, options);

    if (res.ok) return res.json();

    if (res.status === 429) {
      // Rate limited — respect Retry-After header
      const retryAfter = parseInt(
        res.headers.get("Retry-After") || "5", 10
      );
      console.warn(`Rate limited. Waiting ${retryAfter}s...`);
      await new Promise((r) => setTimeout(r, retryAfter * 1000));
      continue;
    }

    if (res.status >= 500 && attempt < maxRetries) {
      // Server error — exponential backoff
      const delay = Math.pow(2, attempt) * 1000;
      console.warn(`Server error ${res.status}. Retry in ${delay}ms`);
      await new Promise((r) => setTimeout(r, delay));
      continue;
    }

    // Client error (4xx) — don't retry
    throw new Error(`${res.status}: ${await res.text()}`);
  }

  throw new Error("Max retries exceeded");
}

// Usage
const result = await sendWithRetry(
  "https://signb.ee/api/v1/send",
  {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "Authorization": "Bearer YOUR_API_KEY",
    },
    body: JSON.stringify({
      markdown: "# NDA\n\nTerms here...",
      recipient_name: "Jane Smith",
      recipient_email: "jane@example.com",
    }),
  }
);

Common rate limit mistakes

Mistake	Consequence	Fix
No retry logic	Documents silently fail	Exponential backoff + dead letter queue
Ignoring Retry-After	Hammering the API → IP ban	Parse and respect the header
Promise.all for batches	One 429 aborts all docs	Use Promise.allSettled
No concurrency limit	500 simultaneous requests	Chunk into groups of 10-20
No monitoring	Don't know docs are failing	Log 429s, alert on failure rate

Monitoring rate limit health

Track three metrics in production:

429 rate (should be)<1%

Retry success rate (should be)>99%

Dead letter queue size (should be)0

Avg response time (Signbee)<2s

Avg response time (DocuSign)3-5s

Frequently Asked Questions

What are e-signature API rate limits?

Rate limits define how many API calls you can make in a given time window. Exceeding them returns a 429 status code. Without retry logic, the document send silently fails.

What happens when you hit a rate limit?

You receive a 429 Too Many Requests response, usually with a Retry-After header. Your code should pause for the specified duration and retry. Without handling, the document never reaches the signer.

Which provider has the highest rate limit?

Signbee offers 1,000/min on paid plans — roughly 60x more throughput than DocuSign's 1,000/hour. See our full provider comparison.

Never drop a document — 5 free docs/month, 100 req/min.

Read the API docs Batch sending guide

Last updated: May 7, 2026 · Michael Beckett is the founder of Signbee and B2bee Ltd.