What is Rate Limiting?
A mechanism that controls the number of API requests a client can make within a specified time period to ensure fair usage and system stability.
Rate limiting is a mechanism used by API providers to control the number of requests a client can make within a specified time period. It ensures fair access to shared resources, prevents abuse, protects system stability, and maintains consistent performance for all users. When a client exceeds its allotted rate limit, subsequent requests are typically rejected with an HTTP 429 (Too Many Requests) status code until the rate limit window resets.
Rate limiting operates at multiple levels. Per-second or per-minute limits control burst traffic, preventing sudden spikes from overwhelming the system. Per-hour or per-day limits control sustained usage, ensuring that high-volume users do not monopolize resources at the expense of others. Per-endpoint limits may apply different thresholds to different operations, reflecting the varying computational cost of each operation: a simple record lookup may have a higher limit than a complex multi-jurisdiction search.
The implementation of rate limiting typically involves tracking request counts using mechanisms like token buckets, sliding windows, or fixed windows. When a request arrives, the system checks the client's current count against the applicable limit. If the limit has not been reached, the request is processed and the counter is incremented. If the limit has been reached, the request is rejected and the client receives an error response with information about when the limit will reset.
API providers communicate rate limit status through standard HTTP headers. Common headers include X-RateLimit-Limit (the maximum number of requests allowed), X-RateLimit-Remaining (the number of requests remaining in the current window), and X-RateLimit-Reset (the time when the limit resets). These headers enable clients to implement intelligent request management, throttling their own requests before hitting the limit.
Why It Matters
Rate limiting is essential for maintaining the reliability and performance of any shared API service. Without rate limits, a single client, whether through a bug, a misconfigured script, or intentional abuse, could consume resources to the point where other users experience degraded performance or service outages. Rate limiting protects the quality of service for all users by establishing predictable boundaries on consumption.
For API consumers, understanding rate limits is critical for building reliable integrations. Applications that exceed rate limits experience failed requests, which can cause data gaps, processing errors, and poor user experiences. Well-designed applications respect rate limits proactively, implementing strategies such as request queuing, exponential backoff, and caching to stay within limits while maximizing throughput.
Rate limiting also plays an important role in API business models. Different pricing tiers typically include different rate limits, with higher tiers offering greater throughput for users who need it. This tiered model allows API providers to serve a range of users, from individual developers running occasional queries to enterprise platforms processing thousands of requests per minute, with pricing that reflects actual usage.
In the context of trademark data, rate limiting is particularly important because search operations can be computationally intensive. A multi-jurisdiction trademark search that spans dozens of offices and analyzes phonetic, visual, and conceptual similarity requires significant processing resources. Rate limits ensure that these resources are allocated fairly across all users.
How Signa Helps
Signa applies two limits to each organization, shared by all its API keys: credits, which set how much you can do, and rate limits, which set how fast. Rate limits are requests per minute and depend on the plan: for most endpoints, 60 on Free, 300 on Starter, 1,000 on Growth and 3,000 on Scale, with custom limits on Enterprise. Some endpoint types, such as screening and compare, have their own lower budgets, so heavy searching does not slow down record reads. Some searches are also limited in how many can run at once.
Every response carries RateLimit-Policy and RateLimit headers with the limit, the requests remaining and the seconds until the window resets, plus credit headers such as X-Credits-Charged and X-Credits-Remaining. When a limit is reached, the API returns 429 with a Retry-After header, and the request is not billed. Paid plans can also spend at most 25% of their monthly credits in one UTC day, which stops a runaway script from draining a month of credits.
Customers who need higher limits can contact Signa, and Enterprise plans have custom limits.
Example
A brand protection agency runs nightly searches for its clients' brands. Its first script fires every request at once and quickly receives 429 responses.
The team rebuilds it around a request queue. The queue reads the RateLimit header on each response and slows down as the remaining count falls, and on a 429 it waits for the Retry-After seconds before continuing. It also groups spellings of each brand into a single search by sending them as a list in q, which cuts the number of requests. The nightly run now stays within the plan's limit, and the team watches the credit headers to keep the month's usage on budget.