Before proceeding with resolving the limit issue, we should dive into the meaning of rate limiting. It is crucial knowledge for those who work with the public API service.
What is rate limiting and why does it exist
Rate limiting is like putting a speed limit on network traffic. It controls how often someone can do the same action in a certain time period, such as logging into an account. Instead of being on the web server, rate limiting happens within the application itself. It keeps track of the IP addresses making requests and the time between each request. The IP address helps the application identify the requester.
The rate limiting solution checks the time between each request from an IP address and how many requests it makes within a specific timeframe. If there are too many requests from one IP address in that timeframe, the rate limiting solution will block further requests from that IP for a while.
Imagine the rate-limited application saying, "Hey, slow down," to users who are making requests too quickly. It's similar to a police officer pulling over a speeding driver.
What are IP addresses
An IP address is a unique numerical identifier given to any device connected to the Internet. It's like a physical address or phone number for devices to send messages back and forth. A typical IP address looks like this: 198.41.129.1
How rate limiting works for APIs
An API, or application programming interface, allows programs to request specific functionalities. Most users don't see APIs, but they are crucial for applications to work properly. For instance, a restaurant's website may use an API from a table reservation service to let customers make online reservations. APIs are also used by eCommerce platforms to integrate shipping company services for accurate shipping costs.
Each time an API responds to a request, the owner of that API has to pay for server resources and compute time. This is why APIs often have limits on the number of calls a user can make per hour or day. It prevents developers from overusing the API without paying for it.
Rate limiting for APIs also protects against malicious bot attacks. Attackers can use bots to flood an API with repeated calls, making the service unavailable to others or even crashing it. Rate limiting helps prevent such attacks.
What are the limits for SimpleSwap public-API and what to do when you’re pushing the limits?
Currently, the rate limits for public-API depend on the tier a partner has. The tier type depends on the partner’s volumes:
- tier 1 (default): 50 requests per 10 seconds;
- tier 2: 200 requests per 10 seconds;
- tier 3: 500 requests per 10 seconds;
- tier 4: 1000 requests per 10 seconds.
If you exceed the number of requests, your IP will be blocked for 1 minute.
What to do? Try not to exceed the allowed number of requests and use caching.
In order to increase the number of requests, you may contact us at partnerships@simpleswap.io.
Share on: