My favorites | Sign in
Project Logo
       
New issue | Search
for
| Advanced search | Search tips
Issue 550: direct_messages/new: screenname vs id
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  m...@twitter.com
Closed:  Jun 25
Type-Defect
Priority-Low
Component-REST


Sign in to add a comment
 
Reported by su...@sunilgarg.com, May 04, 2009
direct_messages/new does not allow disambiguation between IDs and screen
names that are composed entirely of numbers. 

See http://twitter.com/twitterapi/status/1701325429 for prior conversation.

Thanks.
Comment 1 by m...@twitter.com, Jun 23, 2009
Working on this now. Sorry for the delay but there were some higher priorities ahead of it.
Status: Accepted
Owner: m...@twitter.com
Labels: -Priority-Medium Priority-Low Component-REST
Comment 2 by m...@twitter.com, Jun 25, 2009
Deployed the fix. New parameters are screen_name and user_id (in place of user). Documentation updated as 
well.
Status: Fixed
Sign in to add a comment

Hosted by Google Code