Introduction

The following is a list of features, bug fixes, and improvements that may or may not make it into the next major version of the Twitter API. Where available, items that had an associated issue in the Issues list have been noted. Lastly, this list makes no guarantees or commitments to timelines. This is simply a place to organize the discussion from the community.

 

Would you like to see something added to this list? Tweet an @reply to @twitterapi.

 

Introduction General Design Goals Merging REST and Search APIs Feature Categories Data Direct Messages Following Security Sessions Statuses Support Validation Users Search Common requests

 

General Design Goals

 

Merging REST and Search APIs

• use same date format (epoch time) (206) (306) (731)
• use same User IDs (214)
• include in_reply_to_status_id (273)
• return the same User and Status objects (345)
• use the same screen_name capitalization (626)

 

Feature Categories

  

Data

• Source parameters should be returned as struct, not just a link (75)
• Per-user key/value store to keep of last-read status ID, etc. (171)
• Return numeric error codes, document them (460)
• Disallow page=0 with an error (609)

 

Direct Messages

• POST to destroy (515)
• Retreive direct messages from and to a given user (810)

 

Following

• Batch Following (483)
• Protected users can approve/deny follower requests (8)
• Allow users to cancel follow requests of protected users through the API (699)
• Return following_since/follower_since data in user elements (520)

 

Security

• Deprecate JSON callbacks for methods that return private data (113)

 

Sessions

• Return User object on end_session method (259)

 

Statuses

• Method that returns recently deleted status IDs (addition to Streaming API?) (58)
• Method to find replies to a given status via in_reply_to_status_id (142)

 

Support

• API test console (sandbox) (194)

 

Validation

• Return HTTP status code 405 when POST is used for GET-only method (and vice versa). (475)

 

Users

• Method that returns recently deleted user IDs (addition to Streaming API?) (311)
• People search (return user objects based on fuzzy match on name, screen_name, etc.) (357)
• Combine update_profile_colors and update_profile methods (683)
• Ensure background information includes correct null information. (587, 754)
• Get a list of IDs which have notifications enabled (787)
• Get the full archive of a user's tweets (832)

 

Search

• Search within favorites (859)
• Add more languages to search, including Hebrew (523)

 

Common requests

• Add screen_names to social graph queries (265)
  • Please see the related discussion explaining why this is difficult and not likely to happen.