Messages sent from Twitter web interface not returned by get_conversation() and get_inbox()

[dunfes]

When I send a message using send_message, it appears correctly in both the API response and the Twitter web interface. However, when a message is sent through the Twitter web interface , it is visible on the web but
completely absent from the API response when calling get_conversation() or get_inbox().

This creates a situation where the conversation history returned by the API is incomplete - it only contains messages that were sent via the API itself, missing all messages sent through Twitter's native interfaces.

Testing Done

I tested this with two accounts by sending messages back and forth:

• Messages sent via API: visible in both API and web
• Messages sent via web: visible only on web, missing from API

I tried multiple approaches including get_conversation(), get_inbox() with different page counts, deleting session files and re-authenticating - all produce the same incomplete results.

Possible Cause (not sure)

Twitter recently redesigned their DM interface. This update might have changed how messages are stored or which endpoint returns the conversation history. It's possible that the current endpoint only returns messages from a specific source, or
Twitter has separated API-originated messages from web-originated messages internally.

Question

Is there a different method or endpoint that could retrieve the complete conversation history including messages sent from the web interface? Or is this a known limitation after Twitter's recent changes?

If there's a way to fix this in the this update, that would be really cool I really like this library and would like to use it 🙏

[Jaden024]

I am experiencing the same problem @mahrtayyab

Is it going to be possible to fix this before the next major update?

[mahrtayyab]

I think I will push the update for everything else first then you work on castle token.
I am working on reversing castle_token generation.