Users/show
(→users/show) |
(→users/show) |
||
第26行: | 第26行: | ||
* screen_name. 指定用户账号,主要是用来区分用户ID跟用户账号一样,产生歧义的时候。 | * screen_name. 指定用户账号,主要是用来区分用户ID跟用户账号一样,产生歧义的时候。 | ||
o Example: http://api.t.sina.com.cn/users/show.xml?screen_name=101010 | o Example: http://api.t.sina.com.cn/users/show.xml?screen_name=101010 | ||
− | + | ||
* id. The ID or screen name of a user. | * id. The ID or screen name of a user. | ||
o Example: http://api.t.sina.com.cn/users/show/12345.json or http://api.t.sina.com.cn/users/show/bob.xml | o Example: http://api.t.sina.com.cn/users/show/12345.json or http://api.t.sina.com.cn/users/show/bob.xml |
2009年11月5日 (四) 11:40的版本
目录 |
users/show
按用户ID或账户返回用户资料,同时也将返回用户的最新发布的微薄。
Returns extended information of a given user, specified by ID or screen name as per the required id parameter. The author's most recent status will be returned inline.
URL:
curl http://api.t.sina.com.cn/users/show.format
Formats:
xml, json
HTTP Method(s):
GET
Requires Authentication (about authentication):
false (see usage notes)
API rate limited (about rate limiting):
1 call per request
Parameters:
- id. 用户ID或用户帐号。
o Example: http://api.t.sina.com.cn/users/show/12345.json or http://api.t.sina.com.cn/users/show/bob.xml
- user_id. 指定用户ID,主要是用来区分用户ID跟用户账号一样,产生歧义的时候,特别是在用户账号为数字导致和用户id发生歧义。
o Example: http://api.t.sina.com.cn/users/show.xml?user_id=1401881
- screen_name. 指定用户账号,主要是用来区分用户ID跟用户账号一样,产生歧义的时候。
o Example: http://api.t.sina.com.cn/users/show.xml?screen_name=101010
- id. The ID or screen name of a user.
o Example: http://api.t.sina.com.cn/users/show/12345.json or http://api.t.sina.com.cn/users/show/bob.xml
- user_id. Specfies the ID of the user to return. Helpful for disambiguating when a valid user ID is also a valid screen name.
o Example: http://api.t.sina.com.cn/users/show.xml?user_id=1401881
- screen_name. Specfies the screen name of the user to return. Helpful for disambiguating when a valid screen name is also a user ID.
o Example: http://api.t.sina.com.cn/users/show.xml?screen_name=101010
Usage Notes:
- Requests for protected users without credentials from 1) the user requested or 2) a user that is following the protected user will omit the nested status element. Only publicly available data will be returned in this case.
- [Deprecation] The notifications and following attributes will be removed in version 2 of the API. Use /friendships/show or /friendships/exists instead.
Response
(about return values): XML example (truncated):
<?xml version="1.0" encoding="UTF-8"?> <user> <id>1401881</id> <name>Doug Williams</name> <screen_name>dougw</screen_name> <location>San Francisco, CA</location> <description>Twitter API Support. Internet, greed, users, dougw and opportunities are my passions.</description> <profile_image_url></profile_image_url> <url>http://www.igudo.com</url> <protected>false</protected> <followers_count>1031</followers_count> <profile_background_color>9ae4e8</profile_background_color> <profile_text_color>000000</profile_text_color> <profile_link_color>0000ff</profile_link_color> <profile_sidebar_fill_color>e0ff92</profile_sidebar_fill_color> <profile_sidebar_border_color>87bc44</profile_sidebar_border_color> <friends_count>293</friends_count> <created_at>Sun Mar 18 06:42:26 +0000 2007</created_at> <favourites_count>0</favourites_count> <utc_offset>-18000</utc_offset> <time_zone>Eastern Time (US & Canada)</time_zone> <profile_background_image_url></profile_background_image_url> <profile_background_tile>false</profile_background_tile> <statuses_count>3390</statuses_count> <notifications>false</notifications> <following>false</following> <verified>true</verified> <status> <created_at>Tue Apr 07 22:52:51 +0000 2009</created_at> <id>1472669360</id> <text>At least I can get your humor through tweets. RT @abdur: I don't mean this in a bad way, but genetically speaking you're a cul-de-sac.</text> <source><a href="http://www.tweetdeck.com/">TweetDeck</a></source> <truncated>false</truncated> <in_reply_to_status_id></in_reply_to_status_id> <in_reply_to_user_id></in_reply_to_user_id> <favorited>false</favorited> <in_reply_to_screen_name></in_reply_to_screen_name> </status> </user>
Usage examples:
cURL (about cURL):
curl http://api.t.sina.com.cn/users/show.xml?screen_name=dougw