Hello Andrey,
I have reviewed the API code and also tested providing all numbers through the getAllNumbers API request. Below is my input accordingly:
As you know, we already have the following APIs available:
getMillionNumbers
getRepeaterNumbers
getDoubleRepeaterNumbers
getVanityNumbers
getX00-X000
getTollFreeNumbers
getXY0-0000
getX00-Y000
getXYY-YYYY
These APIs allow users to fetch their preferred types of numbers. While we can provide access to all numbers through the getAllNumbers API, doing so would place a heavy load on our server, potentially leading to a server crash. Even if the server successfully handles the request, the response time will be significantly delayed, which could result in a timeout error for the API user.
Considering we have over 90,000 numbers in our database, returning all of them in a single request is neither practical nor advisable. For this reason, I currently limit the getAllNumbers API response to 500 numbers at a time.
Our documentation includes detailed explanations of each API’s request and response structure. However, if an API user requires specific data not covered by the existing APIs, we are open to creating a new, dedicated API for that purpose.
Although we already offer APIs to fetch specific number types like Repeater and Million numbers, I am open to discussing any new ideas or suggestions you may have—especially if they align with customer needs.
