For better reliability, optimum performance and to ensure the SBT API platform is available to all of our customers, certain limits have been put in place.
The limits on the total calls and the rate at which the calls can be made helps to protect the system from receiving more data than it can handle, and ensures an equitable distribution of system resources. It ensures that one developer’s actions cannot negatively impact the larger community.
SBT balances load by imposing two types of limits:
* Report API usage limit
* Concurrent (parallel) requests limit
API usage limitations are primarily considered per API Key account.
Report API usage limit
The Report API interface provides the means to programmatically get data such as message sent, message received, keywords and subscribers.
Report API usage has a limit of 1 request per every 15 minutes interval per APIKey account.
It is strongly recommended to use reporting interface during off-peak hours (i.e., 8:00 PM – 8:00 AM CST)
Concurrent (parallel) requests limit
There is a limit on the number of requests that a user can execute concurrently.
Send Message Request Limit:
A user (APIKey account) can send up to 10 parallel requests or use multiple threads at a given time. For sending messages, a limit of 100 messages per request is allowed
Carrier Lookup Limit:
Carrier lookups can be done up to 10 parallel requests with 10 numbers in each request.
1 request per 15 min and no requests between 12:00AM to 2:00AM CST.
We ask that you honor the rate limit. If your application abuses the rate limits we will blacklist it. If you are blacklisted you will be unable to get a response from the SBT API. If your application has been blacklisted and you think there has been an error you can contact our support team.
If send message request attemt is made with invalid Status URL for 200 times, then status call URL is blacklisted in our platform and you will not be able to use it in future. For unblocking the status URL please contact SBT team.