We are planning to launch support for multiple media entities in tweets via our REST API on May 28th. This will be exposed as a new extended_entities object in the JSON response.
Today the only type exposed in our entities is photo, however with the addition of extended_entities we plan to expand the types of media we expose. Developers should actively use the type attribute from the media exposed to validate you are handling the types properly, and ignore types that are not of type photo.
For details on the changes we’ll be making to support this feature, visit Multiple Media Entities in Statuses. We’ll Tweet from @TwitterAPI when we make the actual changes on the 28th.
Post your questions here or Tweet to @TwitterDev.



Replies
Accessing to the Web page "Multiple Media Entities in Statuses" is denied when I signed into this site. I can read the page if I sign out.
hmm, that's odd - I checked the permissions and it should allow you to access the page when logged in. Will check whether there's a caching issue.
This will actually be released tomorrow, May 29th, during business hours (PDT).
We will slowly ramp up availability throughout the day.
so it's normal i can't get mulitple photos in a tweet right now?
Yes. I will update this thread when we start to ramp this up, we will roll it out gradually during the day.
The roll out will be completed by the end of the day tomorrow (Friday May 30th, before 5pm PDT).
You should start to see the extended_entities this morning, we are ramping this first. This afternoon we will enable POSTing.
Posting multiple photos still doesn't work:
And now https://dev.twitter.com/docs/api/multiple-media-extended-entities returns "Access denied".
Is something going wrong?
How does it look with the rollout? Unfortunately we are still unable to see extended_entities for tweets in the API. Should we wait or fill in a bug report?
Example request: https://apigee.com//snapshot/twitter?snapId=apigee-console-snapshots-1401598800000_862685cf-519f-488c-9344-72fe4d44acf8.
Thanks.
Not sure if this is an issue with the apigee console, just tested it using twurl with the sample tweet in the docs (https://api.twitter.com/1.1/statuses/show.json?id=449660889793581056) and it worked for me.
Hi Sylvain,
thanks for you reply. Well, after more testing we found out that it actually depends (or it seems to be the reason at least) on used oauth access tokens. With some of them extended_entities are present in the response and with some of them not. Is anybody else seeing the same behavior?
This should be available to all now, please let us know if you are not seeing extended_entities or are not able to POST.
Docs are at https://dev.twitter.com/docs/api/multiple-media-extended-entities.
I am still not seeing extended_entities on getting statuses and the home_timelines.
Ex. Sorry for including non-English charactors.
openedreading 1521 bytes...->read 1521 bytesConn keep-alive{{[][{[115137]{{}{}{}{}}}][][][]}{{{[]}{[{[022]}]}}}}Updating statuses with media_ids works and I can see the multiple photos on Web page, but the API results have no extended_entities, just only entities.
Thank you.
Are you still not seeing extended entities?
No, I am still not seeing extended_entities, just entities on both my App and your developer console.
Twitter developer console snapshot is https://snap.apigee.com/1o9RtJR
We're looking into this and hope to have an update for you from someone on the team shortly.
can't get multiple photos using api:
https://api.twitter.com/1.1/statuses/home_timeline.json
also tried
https://api.twitter.com/1.1/statuses/show/{id}.json
i have posted 3 pictures in this tweet, but i can only get one in media section, and no extended_media in reposonse
"media": [
{
"id": 473655124855111700,
"id_str": "473655124855111681",
"indices": [
0,
22
],
"media_url": "http://pbs.twimg.com/media/BpLC05cIQAEVGoN.png",
"media_url_https": "https://pbs.twimg.com/media/BpLC05cIQAEVGoN.png",
"url": "http://t.co/IZmkq3vmxG",
"display_url": "pic.twitter.com/IZmkq3vmxG",
"expanded_url": "http://twitter.com/iAutoApps/status/473655129678155777/photo/1",
"type": "photo",
"sizes": {
"medium": {
"w": 18,
"h": 18,
"resize": "fit"
},
"thumb": {
"w": 18,
"h": 18,
"resize": "crop"
},
"large": {
"w": 18,
"h": 18,
"resize": "fit"
},
"small": {
"w": 18,
"h": 18,
"resize": "fit"
}
}
}
]
},
Can I get extended_entities in the search/tweets and streams(I use statuses/sample)?
if not supported, is there any plans to support?
I'm also not able to retrieve extended_entities from my app (I'm using Twitter4j).
Using twurl I can see the new object, but when I perform the same request from my app I get a different JSON response (I'm using the same consumer key & secret, if that can help).
twurl /1.1/statuses/show/470059593737846785.json
(I'm also getting an "Access Denied" error on the documentation page, but only when I'm logged in).
Is this available to everyone or only to specific partners.
When i tried using this API, i got "Internal Service Error" with it.
REQUEST
POST /1.1/statuses/update.json?status=tt1&display_coordinates=false&media_ids=473779467069173760,473779756484542460 HTTP/1.1
X-HostCommonName:
api.twitter.com
Authorization:
OAuth oauth_consumer_key="DC0sePOBbQ8bYdC8r4Smg",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1401792930",oauth_nonce="2761693087",oauth_version="1.0",oauth_token="322472919-rJFyTe8VhpzwgABeJLHEZmF7uWwP7xzgpAHu0o8L",oauth_signature="lIGtzDLvz3PCksbf%2BXkvuPqdmYQ%3D"
Host:
api.twitter.com
Content-Length:
0
X-Target-URI:
https://api.twitter.com
Content-Type:
application/x-www-form-urlencoded; charset=UTF-8
Connection:
Keep-Alive
===========
RESPONSE
HTTP/1.1 500 Internal Server Error
x-frame-options:
SAMEORIGIN
content-type:
application/json; charset=utf-8
last-modified:
Tue, 03 Jun 2014 10:55:30 GMT
status:
500 Internal Server Error
date:
Tue, 03 Jun 2014 10:55:30 GMT
x-transaction:
123c19cd017d1f8e
pragma:
no-cache
cache-control:
no-cache, no-store, must-revalidate, pre-check=0, post-check=0
x-xss-protection:
1; mode=block
x-content-type-options:
nosniff
expires:
Tue, 31 Mar 1981 05:00:00 GMT
set-cookie:
lang=en
set-cookie:
guest_id=v1%3A140179293064373993; Domain=.twitter.com; Path=/; Expires=Thu, 02-Jun-2016 10:55:30 UTC
content-length:
52
server:
tfe
strict-transport-security:
max-age=631138519
x-access-level:
read-write-directmessages
{
"errors": [
{
"message": "Internal error",
"code": 131
}
]
}
The domain for uploading is upload.twitter.com, instead of api.twitter.com. Give that one a shot as everyone with valid credentials and write access should have permission to use this.
Suggest looking at RiteTag API - http://ritetag.com/rest-api for hashtag-grading and associated hashtags.
I'm not seeing extended_entities coming back in many cases too, showing fine on Web but not when querying the API directly
Is the maximum number of images that I can attach to a single tweet defined? I figured out that no more than 5 images can be attatched to one tweet, but still it's not defined in
help/configuration. For the sake of completeness I'd like to see the number defined in the configuration.i can't see extended_entities on statuses/show or timeline.
i can't see extended_entities on statuses
does this thread have anything to do with posting tweets from websites via the safari widget in IOS for iphone 5s? Im looking for some info regarding the error message "The tweet (http://followtheoutbreak.worldpress.com/) cannot be sent because the connection to twitter has failed"
If anyone can help me out id greatly appreciate it.