Support & FAQ

An API (Application Programming Interface) is a way for different software systems to talk to each other. Think of it as a waiter taking your order at a restaurant: you (the client) tell the waiter (the API) what you want, and the kitchen (the server) delivers it.

Requests are the messages you send to an API when you want it to do something — like get data, update info, or delete stuff. Each interaction with the API is a separate request.

A rate limit is the maximum number of requests you're allowed to make to an API within a certain time frame. It's there to prevent abuse and keep the system running smoothly. Think of it as "you can only annoy the waiter so many times per hour."

You can see your remaining request count either:

• in your dashboard

• or in the response headers of each API call

The API response time depends on the user being checked and the current state of Twitter. We cannot influence Twitter's performance—sometimes it runs slowly, and that is beyond our control. As for the user, the more followers they have, the longer the checking process takes.

If the response time is too long, the likely cause is either Twitter's instability at the moment or the account's high popularity, which requires more time for processing.

Using the endpoint consumes 1 request.

In the case of /search-tweets, 1 request covers every 20 tweets. To retrieve the next 20 tweets, you need to spend another request, and so on.

Unfortunately, this endpoint is not available in our current functionality.

However, we are open to implementing it upon individual request, provided that your purchase volume exceeds 1M requests.