CreateTweet endpoint failed

[allentown521]

when use CreateTweet endpoint , responsed "errors":[{"message":"Authorization: This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now.

[iSarabjitDhiman]

Hi @allentown521

Have u tried other endpoints? If so, and working fine, you need to take another look at your code. I am not sure if incorrect tid triggers any automation traps. It should throw a 404 if the tid is incorrect.

If you want me to test, I can try hitting /CreateTweet on my side.

Let me know.

[allentown521]

Hi @allentown521

Have u tried other endpoints? If so, and working fine, you need to take another look at your code. I am not sure if incorrect tid triggers any automation traps. It should throw a 404 if the tid is incorrect.

If you want me to test, I can try hitting /CreateTweet on my side.

Let me know.

I've been using your library for months, it's been normal, today I found that the createTweet endpoint is 100% unavailable, but other endpoints are available, I believe it was Twitter that strengthened the validation of this endpoint, maybe the tid algorithm for that endpoint has been adjusted, I think you should test it

[runetech0]

when use CreateTweet endpoint , responsed "errors":[{"message":"Authorization: This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now.

This is because Twitter has implemented TLS fingerprinting which is detecing your Tweets. It has nothing to do X-Client-Transaction-I header.

[allentown521]

when use CreateTweet endpoint , responsed "errors":[{"message":"Authorization: This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now.

This is because Twitter has implemented TLS fingerprinting which is detecing your Tweets. It has nothing to do X-Client-Transaction-I header.

I get the same results no matter what content I send, and other users use the deploy services through me have pointed this out also, so it's normal for you to test? What are you referring to tls fingerprinting function?

[jamboochuuu]

"errors":[{"message":"Authorization: This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Im sure

[iSarabjitDhiman]

As @runetech0 mentioned, its not an issue with the X-Client-Transaction-Id, but with the twitter client you are using.
I tried adding this CreateTweet endpoint to TweeterPy and it worked seamlessly.
I have already switched to curl_cffi library which takes care of cloudflare bypass and tls.

XClientTransaction library doesnt make any http requests for header generation, rather uses homepage response to generate a valid id. Therefore there is no way we gonna implement the tls handling here. Accuracy of tid totally depends on the homepage response you are using for tid generation.

Let me know if there is still anything you guys need help with.

Thank you.

[jamboochuuu]

Which browser fingerprint should curl_cffi specify? I have tried many times and still have a probability of automatic detection.

[iSarabjitDhiman]

Which browser fingerprint should curl_cffi specify? I have tried many times and still have a probability of automatic detection.

I used the chrome python impersonate="chrome" it automatically picks up the latest supported version.
It worked for me.

You can try using custom fingerprints by grabbing one from your browser.

[jamboochuuu]

I tried python impersonate="chrome" but still Authorization: This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Please try again later. (226)" LOL

[jamboochuuu]

When all environments are identical (using curl_cffi), I can tweet 100% of the time using a real transaction ID from a captured tweet endpoint. However, once I use our XClientTransaction module to generate an ID, it fails with high probability. Very strange.

[iSarabjitDhiman]

When all environments are identical (using curl_cffi), I can tweet 100% of the time using a real transaction ID from a captured tweet endpoint. However, once I use our XClientTransaction module to generate an ID, it fails with high probability. Very strange.

I will try to take a look today and get back soon.

[jamboochuuu]

I just tried using curl_cffi to call the XClientTransaction module to generate the id and it seems to be starting to work.