AdminAndy Piper
(Developer Advocate, Twitter)
My feedback
-
3 votesstarted · 2 comments · Twitter Developer Labs » General features · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment An error occurred while saving the comment Thanks for the suggestion. OAuth 2.0 user authentication for the API is on the roadmap https://t.co/roadmap but we are not there yet and this is a big change so it will take some time. In order to access non-public metrics for Tweets we do require user authentication, so that is why we currently require OAuth 1.0A for this functionality (these are private to the authenticated user). We appreciate your interest in a revised authentication mechanism!
-
3 votesAdminAndy Piper
(Developer Advocate, Twitter)
supported this idea
·
-
10 votes
An error occurred while saving the comment -
3 votes
An error occurred while saving the comment Many of these have been deprecated or null for a long time - see [this announcement from 2019](https://twittercommunity.com/t/upcoming-changes-to-user-object-and-get-users-suggestions-endpoints/124732).
Some of these (like and statuses counts) are available via requesting the public_metrics expansion.
Which specific fields do you require, and what is the reason for using them? This will help to inform our product process.
-
5 votes
An error occurred while saving the comment I have not seen this announced on the dev forums so far, how up-to-date is this with the latest API features?
-
1 vote
An error occurred while saving the comment Hi, did you post about this on the Twitter forums? https://twittercommunity.com/c/libraries-and-sdks/63
-
1 vote
An error occurred while saving the comment Did you consider posting this on the forums? https://twittercommunity.com/c/libraries-and-sdks/63
An error occurred while saving the comment This is a third party library for accessing the Twitter API. Twitter does not provide libraries.
-
3 votesAdminAndy Piper
(Developer Advocate, Twitter)
supported this idea
·
-
3 votes
An error occurred while saving the comment Thanks for this! Just to help me to understand better here, are you talking about the Tweets endpoints from v1.1 (statuses/show and statuses/lookup)? Or do you mean the Users endpoints (users/show and users/lookup)?
Currently in v2, you can query the Tweets endpoint by Tweet ID(s). The Users endpoint can take either a username, or an ID or range of either.
-
77 votes
This is being worked on. There are some dependencies that are higher on the backlog that need to be completed first.
An error occurred while saving the comment This is being worked on - https://trello.com/c/qztXMWCK/76-bookmarks-v2-twitter-api - please let us know what we can do to make this a great experience!
An error occurred while saving the comment Thanks for this idea Anu, we'll focus on the API suggestion as this site is for ideas related to the Developer Platform. I'm going to mark this is a duplicate of another request - feel free to add your comments on what you would use an API for, to that idea. Thanks! https://twitterdevfeedback.uservoice.com/forums/921790-twitter-developer-labs/suggestions/39678766-api-endpoint-for-getting-bookmarks
AdminAndy Piper
(Developer Advocate, Twitter)
supported this idea
·
-
3 votes
An error occurred while saving the comment Do you have any further context to share on how this would map to an API feature?
An error occurred while saving the comment There is no 3 day limit that I am aware of on the Twitter API - are you talking about the Premium API monthly subscription?
-
6 votesstarted · 2 comments · Twitter Developer Labs » Tweet Annotations · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Twitter Developer Labs now features search and streaming filters for context annotations.
-
1 vote
An error occurred while saving the comment Reminder that this site is aggregating *API* platform concepts.
Also that the current Notification Option experiment is an experiment.
Can you please explain how you would see your idea and comment being related to a future Twitter Developer API Platform feature?
-
3 votes
An error occurred while saving the comment Thanks for this suggestion.
In the v1.1 trends API, this is currently available. Use the trends/place endpoint and set the WOEID value to "1" -> https://developer.twitter.com/en/docs/trends/trends-for-location/api-reference/get-trends-place
We would be interested in discussion here about potential future versions of the Trends API, but we're unable to take specific ideas for the Twitter website or mobile apps via this channel.
At the moment the website has dropped the worldwide trends view as we improve the new version of Explore, but feel free to communicate how you would use it on this thread https://twitter.com/twittersupport/status/1245837034255577089
-
1 voteacknowledged · 1 comment · Twitter Developer Labs » General features · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment With Twitter Developer Labs there are currently no changes to the authentication mechanism, so existing documentation and tutorials can be used. There are Ruby and Python examples on the Twitter Developer Relations GitHub organisation - e.g. see https://github.com/twitterdev/twauth-web and https://github.com/twitterdev/sign_in_with_twitter_sample. Happy to look into adding other examples for languages like Javascript as well.
-
9 votesstarted · 7 comments · Twitter Developer Labs » Documentation and resources · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment We did revise the current list https://developer.twitter.com/en/docs/developer-utilities/twitter-libraries.html a few weeks ago, covering the standard APIs (with a few with Ads API and premium API coverage)
We'll be looking to identify additional, up-to-date libraries that cover the new functionality supported by Labs as the endpoints graduate, so do let us know if you are aware of any!
An error occurred while saving the comment Thanks Joe - the interest in .NET Language support is noted. We're fortunate to have a couple of good third-party ones at the moment (as you know!) and as we expand the new API surface I'll see what we can do to support the developers.
An error occurred while saving the comment Absolutely. It might entail a cleanup of the current list (which is outdated), and some form of endorsement and/or closer relationship between Twitter and the library developers. If we were to partner with developers in 4-5 frameworks, which languages do you feel might be most valuable - apart from PHP? ;-)
AdminAndy Piper
(Developer Advocate, Twitter)
supported this idea
·
-
1 voteacknowledged · 1 comment · Twitter Developer Labs » General features · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Thanks, I've moved this over the the Twitter Developer Labs category as it fits better there than under the policy section.
-
1 voteacknowledged · 2 comments · Twitter Developer Labs » Recent search · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Can you comment further on the reason that adding the expansion parameter for the user object is an issue? As things stand, this is how the Tweet and User APIs have been designed, to provide for more flexibility in data formatting and in the requests (and this is common across all of the current Labs endpoints). We can certainly consider adding more data to the Tweet object at "default" format level, but the data is already available with a single additional query parameter, so it's not clear what this would add. Thanks!
-
3 votesacknowledged · 0 comments · Twitter Developer Labs » Recent search · Flag idea as inappropriate… · Admin →AdminAndy Piper
(Developer Advocate, Twitter)
supported this idea
·
-
3 votesacknowledged · 2 comments · Twitter Developer Labs » General features · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment I’m moving this to the general Developer Labs section as it does not relate only to academic research.
There is now an OAuth 2.0 beta available for v2 endpoints.
https://twittercommunity.com/t/announcing-oauth-2-0-beta/159189