Twitter Developer Labs
-
Difference between the result of Twitter search screen and the return value of API
In some cases, the result of a search set to include a specific word in the advanced search of twitter is slightly larger than the return value of the API. However, some tweets only appear in the return value of the API.
Why is this? Why aren't they unified?This is the advanced search screen I am talking about.
https://twitter.com/search-advanced?f=liveWe want the same result as searching for AAA in the advanced search screen, so the API rules are:
"(AAA OR bio_name: AAA) -is: retweet"
Please let me know if anything is wrong.Thank you
3 votes -
Accept or deny follower requests (when tweets are protected)
It will be really useful to be able to accept/deny follower requests with Twitter API when tweets are protected.
This feature exists but currently this is not public.When I try to call this endpoint :
POST https://api.twitter.com/1.1/friendships/accept.json?user_id=<follower id>
I've received : {"errors":[{"code":37,"message":"Not authorized to use this endpoint."}]} - HTTP Code : 403
16 votesThanks for the feedback. This is most certainly something that we will be considering as we build the next generation of the Twitter API.
-
More locations for Trends API
Some locations are not available in the Trends API, for example Uganda.
It would be great if the current list locations were expanded to include more locations, such as Uganda and cities in Uganda such as Kampala.
1 vote -
Twitter should provide more granular app permissions
Twitter currently offers three levels of app permissions: (1) read only; (2) read and write; (3) read, write and access Direct Messages. These options are not granular enough for some developers, and developers would like more options to choose from.
For example, an app’s “write” permission could be segmented into more granular options: (1) write access to a user’s profile; (2) write access to a user’s network (follow/unfollow, mute, block, list modification); (3) write access to a user’s timeline, including the permission to Tweet, Retweet, or like a post.
Another example includes Sign In With Twitter: there could be an…
39 votes -
Make custom lists more powerful
The current list management is good to keep for example our "best friends" in one place, but the usage behind it is really limited.
Why not allow several filters in the home page (not in another menu) to display only the tweets of a selected list, and give the possibility to exclude retweets of other users ? It will be useful to follow several persons in priority when you follow too many people.1 vote -
Build a conversation updates API
I would like to recommend building a conversations API that enables developers to track updates to full conversation threads. This API would retrieve the entire conversation that a Tweet is in, and return all Tweets and replies within a given thread. This API would enable developers to go from a Tweet of interest to all replies in the thread, without having to recursively search for Tweets with the correct "inreplytostatusid".
43 votes -
Search bar for your individual timeline
Implementing a search bar solely for your timeline will save users from wasting time trying to remember tweets when they refresh the app. Instead of having to scroll down, search for the tweet with words that are constantly used in the atmosphere, and for those that may have forgotten to bookmark it immediately upon sight.
2 votes -
Contact Tab
Being able to place your contact information in a tab within your bio. Great for networking and leaving space for more details in your bio in general.
1 vote -
Filtered Stream
Extra Rules and Tweet allowance for Filtered Stream.
We have an integration with the Filtered Stream API and on-boarding some private beta customers.
I expect we'll exhaust the number of Rules and volume of Tweets with a handful of customers soon.
Idea: - option(s) to opt into extra Rules/volume of Tweets.
PAYG model would work or having a Premium Filtered Stream API offering please.
2 votesThanks for the feedback! The packaging available with Filtered Stream will change to respond to the needs of developers once we graduate out of Labs.
-
Split personal pictures and memes in media
Can be interesting to split in two the type of medias in user profiles.
1/ Personal pictures of the user (where he is tagged)
2/ All the rest (gif, memes, etc.)
Currently it's a little bit messy when you want to check the medias of a user.2 votes -
Poll with images
It's a pity to not be able to create a poll providing images on the same tweet. Why not adding it, like you did for retweet few years ago ?
2 votes -
Control scope of tweets individually
The evolution of this week was really interesting, but I would go further and like Facebook, let the user decides WHO can see a tweet (everybody, only my followers, our only the mentioned users).
2 votes -
Likes Feature
Having the ability to hide certain likes on your portfolio so they can remain hidden or seen under your control.
1 vote -
Bug: incorrect like_count stats in the sample stream
I got this json data out of https://api.twitter.com/labs/1/tweets/stream/sample?format=detailed
This tweet https://twitter.com/theA1wife/status/1236899957858164736 has ~20K likes right now, though the stats in the json show 0 like_count.
I apologize if this isn't where bugs go, but I didn't find anywhere else to post this.
```
…{
"data": {
"id": "1236899957858164736",
"created_at": "2020-03-09T06:21:45.000Z",
"text": "RT @JLo: Wait for it! @AROD <a rel="nofollow noreferrer" href="https://t.co/MNAxO0z2BA">https://t.co/MNAxO0z2BA</a> <a rel="nofollow noreferrer" href="https://t.co/PZIlDlTvyt"">https://t.co/PZIlDlTvyt"</a>,
"author_id": "960338257190862849",
"referenced_tweets": [
{
"type": "retweeted",
"id": "1236865771692670976"
}
],
"attachments": {
"media_keys": [
"7_1236865730156494848"
]
},
"entities": {
"urls": [
{
"start": 28,
"end": 51,
"url": "<a rel="nofollow noreferrer" href="https://t.co/MNAxO0z2BA"">https://t.co/MNAxO0z2BA"</a>,
"expanded_url": "<a rel="nofollow3 votes -
Bring back "tags" to new search endpoints
Query tags are such a useful and simple feature... These essentially enable developers to inject a tag string into the returned payload... These tag strings can be used to record what query was used to match the data, and are helpful in segregating data into logical groups.
Tags are supported in enterprise and premium search, and I am wondering what the future is with Labs and beyond. Note that tags remain a thing with Labs filtered stream.
I am working on a project where a search endpoint is used to process a long list of queries, and not having tags…
1 vote -
Integration of twitter login flow for mobile apps and websites
A lab for building a simple login flow using the REST API and HTTP headers would do us a world of good. Detailed steps with how to build structured messages (I am aware that this is documented in fair detail but a lab form would additionally help us test our individual solutions as well) along with reference implementation and standard value outputs against which bespoke solutions can be tested. Along with the above a list of reference implementations for various languages such as Javascript, Java, Python would help as well. I am still stuck at Twitter login and am struggling…
1 vote -
Make the endpoint rate limited at user level instead of app level
We have built a social media management app that allows our customers to also view insights for their social accounts and posts.
Every midnight we refresh insights for all posts published via our app in the past 7 days.
For Twitter, we're only recording the number of favorites and retweets (returned by the /tweets endpoint), but we would like to gather more metrics, such as impressions, # of replies and video views.
The current rate limit is 15 requests / 15 minutes and 50 Tweets / request.
This basically means we can gather metrics for only 15 customers at a…
16 votes -
Change the limit on user_timeline for the authenticated user own timeline
The user_timeline endpoint currently has a hard limit of only fetching the most recent 3,200 tweets. I understand this limit if the authenticated user is requesting for timeline tweets from another user. But what if the limit could be changed when the authenticated user is fetching tweets from his own timeline, e.g. the most recent 10,000 tweets or all? Other platforms such as Instagram allow you to fetch all of your media from your profile.
Thanks.
2 votes -
Date of last activity in Get labs/2/users expansions
It's useful to have the date of last activity of a user. Before we could deduce it from the most recent tweet but now it's gone in v2 and it become really tricky to get this information.
4 votes -
Missing entitiy operator is:reply
If I want to filter for original tweets only I can use -is:retweet and -is:quote, but then I still receive tweets which are discussion replies. I can filter them out manually as a work around by checking for inreplytouserid values in the streams data fields, but having a is:reply entitiy operator would be very useful and save traffic and processing power on both sides.
1 vote
- Don't see your idea?