Skip to content
  1. Blog
  2. API

What Is API Rate Limiting and How Should Your App Handle It?

TL;DR: API rate limiting caps how many requests a client can send in a set time, and answers extra requests with a 429 error. Your app handles it by slowing down, retrying with backoff and calling less often. The BoldSign eSignature API allows 2,000 requests an hour per live account.

Picture a busy coffee shop at 8 a.m. When everyone rushes the counter at once, orders slow down and mistakes pile up. A line with a pace keeps every order moving.

An API faces the same rush from apps, websites and devices. This guide explains what rate limiting is, the common strategies behind it, and what your code should do when it hits a limit.

What is API rate limiting?

API rate limiting is a rule that caps how many requests one client can send in a given time. A request over the cap gets an error instead of an answer.

Think of the barista who takes one order at a time. Customers still get served, just at a pace the kitchen can keep.

Each request uses server time, memory and bandwidth. A cap such as 100 requests a minute per client keeps the service steady for everyone who shares it.

Why does API rate limiting matter?

Rate limiting keeps a shared API fast and fair. One noisy client cannot slow it down for everyone else.

Rate limits help in three ways:

  • Spikes from one client do not drag down response times for others.
  • A buggy loop that fires 1,000 calls a second gets stopped early, before it runs up costs.
  • Floods of requests from one source are cut off before they do harm.

Rate limiting is one layer of defense. A large distributed denial of service (DDoS) attack needs a dedicated protection service as well.

What are common rate limiting strategies?

Most APIs use one of four rate limiting strategies. Each one counts requests in a slightly different way.

  • Fixed window allows a set number of requests per period, such as 100 a minute, then a reset.
  • Sliding window counts requests over the last rolling period, so bursts at a window edge get caught.
  • Token bucket makes each request spend a token, and tokens refill at a steady rate.
  • Leaky bucket lets requests drain out at a fixed pace, so sudden spikes wait in line.

These strategies run on the server. Our guide to server-side rate limiting shows how to set them up in a Microsoft web API. The rest of this post looks at the client side.

How does BoldSign apply API rate limiting?

We limit each account to 2,000 API requests an hour in a live environment and 50 an hour in sandbox mode. API key calls and OAuth calls share the same count.

The limit applies to the whole account, not to each OAuth app or user. Two apps on one account draw from the same 2,000 requests.

Once you reach the limit, the API answers with status 429 “Too Many Requests”. The API response headers show how much of your limit you have used. Our rate limit page in the developer docs has the details.

How should your app handle a 429 Too Many Requests error?

Treat a 429 as a signal to slow down, not as a failure. A simple retry plan keeps your app working through it.

  1. Stop sending new requests to the API for a moment.
  2. Wait before you retry. Use the Retry-After header when a response includes one.
  3. Double the wait after each failed try, and add a small random delay.
  4. Give up after a few tries and log the error for a person to check.

Our guide to the API retry mechanism shows this backoff in Node.js and Python code.

How do you stay under an API rate limit?

The surest way to avoid 429 errors is to make fewer calls. Plan your traffic so it never comes close to the cap.

  • Set up webhooks for events such as “document signed” instead of polling for status.
  • Send bulk jobs through a queue that releases requests at a steady pace.
  • Add your own limiter in the client, set a little below the API’s cap.
  • Cache data that rarely changes, and drop repeat calls for the same record.
  • Check the usage headers and log how close you get to the limit.

Contact our support team when your use case needs more requests than the limit allows. You can also open a support ticket to talk it through. Our post on managing BoldSign API rate limits has more ideas.

Which BoldSign plan do you need to call the API in production?

Live API calls need the Enterprise API plan, from $30 a month with 40 envelopes. Each extra envelope costs $0.75, as listed on the BoldSign pricing page in November 2026.

Prices are in USD.

Webhooks and live API access are part of that plan. The free sandbox lets you build and test first, with its limit of 50 requests an hour.

How do you start building against the BoldSign API?

The sandbox is a safe place to see a 429 for yourself. Its low hourly limit lets you test your backoff code in minutes.

Frequently asked questions

What does API rate limiting mean?

It means an API accepts only a set number of requests from a client in a given time. Requests over that number get an error until the count resets.

What is a 429 Too Many Requests error?

A 429 is the status code an API sends when you have used up your request allowance. Your app should pause and retry later, not resend straight away.

What is the leading software for rate limiting?

No single tool fits every case. Most teams use an API gateway or the rate limiter built into their web framework.

What is the difference between token bucket and leaky bucket?

A token bucket lets short bursts through as long as tokens are left. A leaky bucket sends requests on at a steady pace, so bursts wait in line.

What is exponential backoff?

Exponential backoff means waiting longer after each failed try, for example 1, 2, then 4 seconds. Adding a small random delay stops many clients from retrying at once.

What is the BoldSign API rate limit?

Live accounts can make up to 2,000 requests an hour, and sandbox accounts up to 50 an hour. The limit counts every call from the account, by API key or OAuth.

Does rate limiting stop DDoS attacks?

Rate limiting helps against floods from single clients, but it does not stop a large distributed denial of service (DDoS) attack alone. That takes a dedicated protection service in front of the API.

How do I reduce the number of API calls my app makes?

Replace polling with webhooks, cache data that rarely changes, and drop repeat calls for the same record. Queue bulk jobs so they run at a steady pace.

Evans Omondi Otieno

Evans Omondi Otieno is a customer support representative and writer at BoldSign, specializing in creating clear, insightful content to help users navigate eSignature solutions. As a blog author, Evans writes well-researched articles that simplify technical concepts, helping businesses and professionals understand how to use BoldSign effectively. With expertise in technical support and content creation, he ensures users have a seamless experience and gain valuable knowledge from his articles.

More posts by Evans Omondi Otieno
Get started

Sign up for your free trial today!

Start free trial
  • 30-day free trial
  • No credit card required