This snapshot, taken on
27/09/2010
, shows web content acquired for preservation by The National Archives. External links, forms and search may not work in archived websites and contact details are likely to be out of date.
 
 
The UK Government Web Archive does not use cookies but some may be left in your browser from archived websites.

Basic Auth has been deprecated.

Attention! August 31, 2010 Basic Auth has been deprecated. All applications must now use OAuth. Read more »   x

Don't fret! @twitterapi is here to help! Feel free to reach out to us directly, or via our Twitter Development Talk group.

The switch to OAuth is a good thing! You, as the application developer,

  • don't have the burden of keeping potentially damaging credentials for your users (especially considering that a lot of people use the same password for multiple services);
  • don't have to worry about the user changing their password — a user can change his or her password and the OAuth "connection" to your app will still work;
  • don't have to worry about other applications masquerading as your application as only your application can set the byline with your application name;
  • will eventually have access to more trusted APIs from Twitter that will only be available to "trusted" OAuth-enabled applications; and
  • will be contributing to the web of trust between users, service providers, and applications.

Choose your authorization path.

GET statuses/:id/retweeted_by/ids

Show user ids of up to 100 users who retweeted the status.

URL

http://api.twitter.com/version/statuses/:id/retweeted_by/ids.format

Supported formats

xml, json

Supported request methods

GET

Requires Authentication

true About authentication »

Rate Limited

true About rate limiting »

Parameters

Required

  • id The numerical ID of the desired status.
    • http://api.twitter.com/1/statuses/2404341/retweeted_by/ids.xml

Optional

  • count Specifies the number of records to retrieve. Must be less than or equal to 100.
    • http://api.twitter.com/1/statuses/2404341/retweeted_by/ids.xml?count=5
  • page Specifies the page of results to retrieve.
    • http://api.twitter.com/1/statuses/2404341/retweeted_by/ids.xml?page=3
  • trim_user When set to either true, t or 1, each tweet returned in a timeline will include a user object including only the status authors numerical ID. Omit this parameter to receive the complete user object.
    • http://api.twitter.com/1/statuses/2404341/retweeted_by/ids.xml?trim_user=true
  • include_entities When set to either true, t or 1, each tweet will include a node called "entities,". This node offers a variety of metadata about the tweet in a discreet structure, including: user_mentions, urls, and hashtags. While entities are opt-in on timelines at present, they will be made a default component of output in the future. See Tweet Entities for more detail on entities.
    • http://api.twitter.com/1/statuses/2404341/retweeted_by/ids.xml?include_entities=true