So from what I have read (and what would seem obvious to others), Twitter can and does truncate tweets that meet certain conditions - this is completely fine and understandable. What I am having a bit of trouble with is actually retrieving the full tweet itself when it is truncated.
Sound confusing? Here is an example, look up this tweet (id: 782845350918971393). It isn’t a retweet itself and the Web UI displays the full message but when accessing it from the API, I get this back:
A #Gameofthrones fan? Our #earlybird Dublin starter will get you touring the GOT location in 2017 #traveldealls… https://t.co/v8AZKrEokz
The API is saying this tweet is truncated, the text itself is truncated and the URL points back to the web UI. Beyond scraping the tweet from the Web UI, does the API not return the un-truncated version?
I’m specifically wanting to get the real message, I want this from the API (note the different URL in the tweet):
A #Gameofthrones fan? Our #earlybird Dublin starter will get you touring the GOT location in 2017 #traveldealls https://t.co/Jtur98U8zv
I’ve been experimenting with Apigee to see if it was the endpoint I was using has this problem (specifically, I was using the search endpoint) however I have been able to test that it also affects the main tweet retrieval endpoint (/statuses/show)
Everything I have searched about truncation refers to a retweet being truncated but this isn’t a retweet!