Multiple Media Entities in Tweets for the REST API

jaakkosf · 2014-06-10T14:10:09.000Z

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.

jaakkosf · 2014-06-10T14:13:52.000Z

Are you still not seeing extended entities?

nosuz · 2014-06-10T15:01:52.000Z

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

jaakkosf · 2014-06-11T18:59:09.000Z

We’re looking into this and hope to have an update for you from someone on the team shortly.

Soreebreaker · 2014-06-13T15:03:28.000Z

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.

c0okk · 2014-06-15T02:28:00.000Z

i can’t see extended_entities on statuses/show or timeline.

LavleenSharma1 · 2014-06-23T14:20:00.000Z

i can’t see extended_entities on statuses

DJStacyBass · 2014-06-30T17:36:40.000Z

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.

SAPIBELTVWORLD · 2014-07-17T00:37:19.000Z

What Will be next check it out when it be available on SAPIBELTV world

abiro · 2014-07-18T13:19:00.000Z

It says May 28, but help/configuration still returns this:

array (
‘characters_reserved_per_media’ => 23,
‘max_media_per_upload’ => 1,
…
‘photo_size_limit’ => 3145728,
…
‘short_url_length’ => 22,
‘short_url_length_https’ => 23,
)

So does the example at https://dev.twitter.com/docs/api/1.1/get/help/configuration.

I also wonder whether statuses/update_with_media can fully replace statuses/update. In other words, with no “media[]”, but everything else exactly the same.

When/if you support multiple files, can each image (and video?) be photo_size_limit large, or are we talking aggregate size of all files per update?

A list of what media types can be uploaded (preferably as MIME type), would be a nice-to-have in help/configuration.

Regards,
Anders

abiro · 2014-07-18T14:09:00.000Z

I noticed that a picture link is at least 26 characters long (http(s):// is not shown, so that maybe adds more), while help/configuration returns 23. Is the link actually shorter, but shown in full?

Example (an actual update): “This should be visible at twitter.com/andersborgme twitizer.com/SsIW8 pic.twitter.com/n8FGHIn6Uz”

When multiple files are supported, will each URL take up space in the tweet or will it point to a page with all the media (how I solved it in Twitizer)?

Cheers,
Anders

abiro · 2014-07-21T18:12:27.000Z

I didn’t even try that, as I assumed I could send only one as help/configuration says so :).

Are more than pictures supported now (like videos and audio)? Any way to determine what media formats are supported?

Has also the picture size limit been changed from 3 MB?

Cheers,
Anders

ok4bx · 2014-07-22T16:52:08.000Z

Any support of extended_entities over stream API?

scottconnerly · 2014-08-01T20:08:26.000Z

It does not appear to be there yet.

mvarrieur · 2014-08-20T23:03:26.000Z

Were you able to figure this out? I can’t seem to get it to work either

andypiper · 2014-08-21T11:31:18.000Z

This should be available in the Streaming API after August 25th.

b7372drdrb · 2014-08-21T20:49:18.000Z

I’m trying to send a POST Request with nodejs but my request fails. Does anybody have a hint?
Tried the following:

Content-Type: multipart/form-data; boundary=---------------------------48870936082676053
-----------------------------48870936082676053
Content-Disposition: form-data; name=“media”; filename="image_5.jpg"
Content-Type: application/octet-stream
Content-Transfer-Encoding: base64

base64 encoded image content
-----------------------------48870936082676053–

But the API responds with “Unknown Twitter API Error” (Status Code 400) “not recognized.”

When using media_data parameter as described in the article (cite: “Note that if you’re uploading a base64-encoded, the param name for this endpoint will be media_data rather than media, which is used for raw images.”)

Content-Type: multipart/form-data; boundary=---------------------------5757786715403199
-----------------------------5757786715403199
Content-Disposition: form-data; name=“media_data”; filename="image_5.jpg"
Content-Type: application/octet-stream
Content-Transfer-Encoding: base64

base64 encoded image
-----------------------------5757786715403199–

The API responds with “Unknown Twitter API Error” (Status Code 409) “media param has zero bytes”

abiro · 2014-08-22T16:55:55.000Z

I use “media[]”, not saying that’s the reason for your issues.

You of course need to authenticate with OAuth, but I assume you do that.

b7372drdrb · 2014-08-23T18:41:26.000Z

Thank you @abiro. Yes I’m using OAuth and had a try with “media[]” but that didn’t work either. I suppose I have to look for an error in my code…

By the way do you POST base64 encoded images?

abiro · 2014-08-27T19:55:30.000Z

I use Zend_Oauth_Token_Access and Zend_Http_Client. From what I can see from the latter, it’s in binary as no conversion is made, only the general “MIME magic” is performed.

My code is no doubt working and in a stable way. I filter out too large images (3 MB), so such are not even attempted to send. I also only upload one image, even though supposedly the API supports more. Users have uploaded much larger animated GIFs than 3 MB, but I store all content in my service and link back.