|
Do the display requirements apply to mobile apps and Twitter clients also? |
Yes. Our display requirements cover mobile. See Developer Display Requirements. |
|
Will an application have to request user authorization just to make public API calls? |
When API v1.1 is released, user authorization (and access tokens) are required for all API 1.1 requests. In the weeks following release, some methods will require only application-based authentication for certain "userless" contexts. |
|
Developer Rules of the Road |
Last Update: September 5, 2012.
Rules of the Road
Twitter maintains an open platform that supports the millions of people around the world who are sharing and discovering what's happening now. We want to empower our ecosystem partners to build valuable businesses around the information... |
|
Will an application have to request user authorization just to make public API calls? |
When API v1.1 is released, user authorization (and access tokens) are required for all API 1.1 requests. In the weeks following release, some methods will require only application-based authentication for certain "userless" contexts. |
|
Will the Search API require authentication? |
The Search API is now part of the official REST API in version 1.1. In addition to serving results in a format consistent with other Tweet resources, usage will also require authentication. |
|
When will API 1.0 be retired? |
API 1.0 will cease accepting requests six months from when API v1.1 is released. We will officially turn off the endpoints for API v1.0 on March 5th, 2013. |
|
What output formats will API v1.1 support? |
API v1.1 will support JSON only. We’ve been hinting at this for some time now, first dropping XML support on the Streaming API and more recently on the trends API. XML, Atom, and RSS are infrequently used today, and we’ve chosen to throw our support behind the JSON format shared across the... |
|
How should we handle @usernames? |
When cross-posting to Twitter with @usernames, be sure to accurately map to the user the author intended to @mention. If your service binds users' Twitter accounts with its own concept of a user profiles, then you can use these relationships to help cross-post @usernames accurately. In cases where... |
|
Does the 100,000 access token limit apply to all applications? Who does the 100,000 access token limit apply to? |
The 100,000 token limit only applies to traditional Twitter client applications, which represent only a small share of the broader Twitter ecosystem. This token limit does not apply to any other applications. |
|
Is there any token limit for non-client applications? |
If you think you’re going to need more than 1 million tokens, please plan to come and talk with us as you approach that number. |
|
How do I know how many access tokens my application has? |
At this time you'll have to contact the platform team to learn how many access tokens your application definitively has. You are encouraged to track your access token count independently, acknowledging that you will not be aware of every access revocation. |
|
How is the access token count calculated? |
The access token count is calculated against the number of valid tokens that an application can use to make an API request. This is the total number of tokens your application has procured, minus those tokens that have either been revoked by the user, or our trust and safety team. |
|
API Terms of Service: Most recent changes |
Please Note: These terms are NOT current. Please read the current terms.
Last Update: May 17, 2012 September 5, 2012.
Return to the API Terms of Service: Archive.
Rules of the Road
Twitter maintains an open platform that supports the millions of people around the world who are... |
|
What happens to the widgets that are based on the Search API and API version 1.0? |
They will be deprecated when version 1 is closed. We recommend using the new Embedded Timelines instead. |
|
POST lists/members/destroy |
Removes the specified member from the list. The authenticated user must be the list's owner to remove members from the list. |
|
POST lists/subscribers/create |
Subscribes the authenticated user to the specified list. |
|
POST lists/members/create_all |
Adds multiple members to a list, by specifying a comma-separated list of member ids or screen names. The authenticated user must own the list to be able to add members to it. Note that lists can't have more than 500 members, and you are limited to adding up to 100 members to a list at a time with... |
|
POST lists/members/create |
Add a member to a list. The authenticated user must own the list to be able to add members to it. Note that lists can't have more than 500 members. |
|
POST lists/destroy |
Deletes the specified list. The authenticated user must own the list to be able to destroy it. |
|
POST lists/update |
Updates the specified list. The authenticated user must own the list to be able to update it. |