curl --location 'https://api.twitterapi.io/twitter/user_login_v2' \
--header 'x-api-key: {your_key}' \
--header 'Content-Type: application/json' \
--data-raw '{
"user_name":"uss",
"email":"11@gmail.com",
"password":"****",
"totp_secret":"65AUK2MK**",
"proxy":"http://qwodeoiq:*****@206.41.1***:**"
}'

curl --location 'https://api.twitterapi.io/twitter/create_tweet_v2' \
--header 'x-api-key: {your_key}' \
--header 'Content-Type: application/json' \
--data-raw '{

"login_cookies":"e****",
"tweet_text":"testxxxxxxx",
"proxy":"http://****:s1**@206.41.***:662"
}
'

The API for logging in and posting tweets with your own account has been updated to version 2, which is more stable and user-friendly. More APIs are currently undergoing large-scale testing.

🚀 API Performance Upgrade Announcement

We’re excited to share that we’ve completed a major upgrade to our API infrastructure, including improvements to servers, network connectivity, and software optimization. As a result, API response times have significantly improved!

📊 Current Performance Metrics (from US-VA region):

Fastest APIs: As low as 260ms

Average Response Time: ~600ms

This upgrade ensures faster, more reliable access for all users. Try it out and let us know your feedback!

The new APIs have been launched: sending private messages, creating communities, and joining/leaving communities.
Please refer to the documentation.
https://docs.twitterapi.io/api-reference/endpoint/send_dm_v2

Hello.
Currently, our API is experiencing some network latency issues. There may be a delay of 2 to 3 seconds, and sometimes it can even reach 5 seconds. Our engineers are working on resolving this problem. We apologize, but it will take a few more hours to fully fix it—this is because we need to configure some physical servers instead of cloud servers. Configuring a cloud server usually only takes a few minutes, around 5 to 10 minutes to complete, but setting up physical servers is more complicated.

In the meantime, you can increase the timeout duration first to avoid impacting your business. We will notify you if there is any progress update.

[Resolved]
Our technical team has resolved the problem. If there are any additional issues, please get in touch with us. We will also keep a continuous eye on the stability of the service.

Black Friday Special 🎉
🔥 2019–2023 registered Twitter accounts – 50% OFF
⚡ Only ~2000 accounts available, while stocks last!

https://twitterapi.io/buy-twitter-accounts

There are some issues with the API, and we are urgently fixing them.

Progress update: Our service has been restored.

Cause of the issue: The server hosting one of our databases restarted abnormally, resulting in data loss after the restart. After several hours of recovery attempts, we are still working with the service provider to retrieve some of the data.

Impact on you: Your registration information on our website has been lost, so you will need to re-register your account. If you have configured webhooks, you will need to reconfigure the rules.

API Key: All previous API keys are no longer valid. Please log in (or register) to obtain and use a new API key.

Credits: For users who have previously recharged and re-register, we will provide a 5 USD credit as a transitional compensation. Once the data is retrieved, we will recharge the original amount to your new account. Please note that the compensation credits are currently being issued manually, so the arrival time is uncertain. To avoid disrupting your usage, we recommend recharging first.

Finally, we sincerely apologize for this major incident and the impact it has had on your services/users. Our original intention in developing this product was to provide the world's most stable and affordable Twitter API, offering basic capabilities to all creative builders. Due to significant costs, we did not initially invest in redundant servers or third-party databases. We will migrate to a third-party database within a week to ensure higher service availability.

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.