Please log out and then log back in. If the problem persists, please clear your browser cookies.

Your previous APIKEY will no longer be usable. Please log out and then log back in, and you will get a new APIK.

All new keys start with "new1_".
All old keys will become invalid.

Update: We are in the process of restoring all users' data and points.

• If you have not registered a new account during this period, your API key will remain unchanged.

• If you have already registered a new account, your new API key will take precedence.

• If you had points before, we will add those points to your bonus.

Final Update

Your user information,and recharged credits have been restored.

The bonus credits will be restored within two days.

Apology again, we will offer a $10 credits bonus to all paying customers affected by the issue in 3 days. While this amount is negligible compared to the inconvenience caused to you, we will continue to work hard to ensure the stability of our system moving forward.

Murphy's Law : if you don't back up your data, you will sooner or later suffer losses.

https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Hello.
There is an issue with Cloudflare that has affected our API, resulting in occasional 500 errors. It is recovering gradually. The impact scope includes Instagram, ChatGPT, Twitter (X) and other platforms. Full recovery is expected soon, and no further notifications will be sent.

Add profile about api

curl --location 'https://api.twitterapi.io/twitter/user_about?userName=sama' \
--header 'x-api-key: {your_api_key}'

Please note that Twitter's own service has been experiencing issues for the past hour, which may affect the stability of the API.

Elon pressed the destroy Twitter button again.

Twitter is crashed now. It may affect the stability of some of our APIs.

Announcement

Over the past ~72 hours, we have observed intermittent data inconsistencies affecting the Tweet Search endpoint.

After extensive investigation, the issue appears to be related to network instability impacting certain AWS regions globally. We are actively monitoring the situation and working closely on mitigation to restore full stability as soon as possible.

We will continue to provide updates if there are any significant developments.

Thank you for your patience and understanding.

For the last several days, due to the high usage (https://x.com/elonmusk/status/2027981570594775101, https://x.com/nikitabier/status/2028265231944970601), Twitter disabled some advanced search features like since, until and apparently they disabled pagination as well. You can refer to this screen recording https://filebin.net/bjids0gy1gfp2m08 to see the issue and duplicate tweets.

We are very sorry for the inconvenience this created on your end but it is totally out of our control. Our api doesn't have any custom logic or filtering, it returns you whatever it can get from Twitter by paginating.

Currently, the best way is test your queries over Twitter Web UI to make sure they work before running them on the api.

Also, the list function seems completely unusable right now. We will launch a new actor within 24 hours to support fetching data from lists.

Hello Everyone.
We have confirmed that Twitter has not yet resolved their pagination issue, and the problem cannot be reproduced consistently.

We recommend that when using the Advanced Search API, you split the time range into multiple smaller intervals and avoid relying on pagination for now.

In addition, we have introduced a new endpoint for retrieving timelines from a list. Since it is a timeline endpoint, it does not support filtering by time.

https://docs.twitterapi.io/api-reference/endpoint/list_timeline