#4

Hi 5_daydream,

yes, that’s correct - with v2 it’s actually not possible to upload media.

#5

Hi @jessicagarson ,

thank you for your reply.

First of all - I find the actual construct complete confusing, because it’s not clear when I login, that I have no access to most of the endpoints. It’s not clearly explained, what I can do and what I cannot do. For example when I look at the features of Essential and Elevated, it looks almost the same. When I then create the endpoints and get the errors for essential restrictions, I really don’t know what to do anymore.

Happily I’ve been accepted for the Elevated Access - now I can post tweets with media.

The documentation could have been more descriptive for the media option on POST /2/tweets. Most of the options have examples, but not the media one. That’s very often the case. I think the documentation can here be made better.

Feel free to contact me if you have any questions :wink:

Thanks,
Sascha

1 Like
#6

@5_daydreams Thanks for following up here. Our current implementation is a bit confusing, but you can attach previously uploaded media to a Tweet at this time. First, you would have to use the v1 media endpoint or Twitter Studio to accomplish this task.

If you do have media already uploaded, you can attach the media to a Tweet like this:

{"text": "Tweeting with media!", "media": {"media_ids": ["1455952740635586573"]}}

We are currently working on a v2 media endpoint, and I have passed your feedback onto the team.

#7

Thanks, @cloudworxx, for your feedback. I can understand how it could be confusing right now, and the fact that you can attach media but not upload it is a bit tricky right now.

Currently we have this is the example listed on the API reference page:

{"text": "Tweeting with media!", "media": {"media_ids": ["1455952740635586573"]}}

We’ve considered adding a second integrate page for this endpoint with more context and examples. I’m interested in hearing from you if you think this would be worthwhile.

Best,

Jessica

#8

Hi Jessica,

sorry for the late reply ;-( Have a lot to do the days before christmas :wink:

I’ve checked the documentation and I think your example helps a lot.
A second integrate page for this endpoint would be very helpful in my opinion.

Love to see, that developers are valued at twitter :wink:

Hope you have great holidays.

Best,
Sascha

2 Likes
#9

No worries! Thank you so much for your feedback here! I’m in the same boat.

Best,

Jessica

#10

Hey, I was trying to do the same, but encountered, that it is impossible to upload image with v2 access, right? I mean, if I want user to tweet something with an image, they need to access with old api v1.1 and it’s not possible for user to access with v2.0 and also upload the image right? I’m asking that, because I don’t understand what’s the use of media_ids if you can’t upload anything in v2 (to tweet already uploaded images? idk)

1 Like
#11

Thanks, @lashaandghulad1.

I do appreciate your feedback here. The current implementation is confusing as you can only attach a previously uploaded media file using the v1.1 endpoint. However, you can access v1.1 endpoints with elevated access, which you can apply to within the developer portal. We’re hoping to have a v2 media endpoint shortly, but at this point, I don’t have a timeframe or ETA I can share yet.

#12

Thanks for the quick response. I’m looking forward to it! I was looking at your roadmap, and was wondering, if it’s possible to add some queue or EST to see which features are next to be added or it’s not just like that easy? haha

#13

I’ll pass on that suggestion to our team. Thanks!

1 Like
#15

Hi.
Are there any updates on when the end point will be available for v2?
We applied for elevated access to get access to the v1 upload endpoint but the request was denied.
Is there any other way or workaround?

Appreciate your help. Thanks

#16

We’re still working on this, but I’ll pass on this feedback internally.

#17

I have submit a request of elevated access for other reasons but got rejected. Now I have to upload image and realized I need elevated access but I have already got rejected, can you help me with this? Thank you very much.

#18

Same here. Trying to make a NFT Sales bot, and cant upload the jpg/png without API 1.1. Applied for elevated and got denied. I made a sales bot in December and was approved, another one in January and was approved, so whats changed now?

#19

Hi, this has been hanging for more than a month, just wondering if there is any update on these, as there are a number of developers wish to have this functionality to work

#20

Thanks, @wgg, for following up. I still don’t have much of an update as I haven’t released a v2 media endpoint, but this is still on our roadmap, and we are very much aware of this issue.

#21

I see, since then, is there any current temp solution?
I have applied for “evaluated” for another reason earlier, and got rejected, and now for using v1.1’s media upload, I wish to apply “evaluated” again but it seems I don’t get anymore chance to apply again. is it possible for you to solve this?
thank you very much for your response anyway.

#22

Sadly, there isn’t a workaround or a solution outside of elevated access. As you mentioned, we don’t currently have a way to edit an application or reapply.

This feature is on our roadmap, stay informed for product updates/changes.

#23

No problem, wish it can be delivered soon :slight_smile:

#24

Hi @jessicagarson,

I’m wondering if you could help me. I spent yesterday morning building the OAuth V2 flow into my app, and only just realised I have to use OAuth V1 to upload media.

The question is do I need to rebuild the whole authentication/authorization into V1 just to have the ability to upload media?

I’m really hoping I can leverage my current OAuth V2 Code flow, and just call an endpoint to get a user access token without redirecting/callback again.

In the developer portal, there are settings to enable v1 and v2 simultaneously, So I suspect V2 for auth flow, and V1 to get user access token > upload media?

Any info will be greatly appreciated.