[twitter-dev] is there a REST API method for getting follower requests?
For user accounts that are set up as protected, is there a way to get follower requests (outside of standard email)? This request sort of goes hand in hand with http://code.google.com/p/twitter-api/issues/detail?id=521.
[twitter-dev] Re: is there a REST API method for getting follower requests?
Hi Doug, Does this mean that the below 2 requests are on the distant roadmap? - ability to get follower requests using REST API - ability to accept follower requests using REST API I know the second one is on the distant roadmap, I wasn't sure about the first one. Thanks, Lien On May 18, 2:17 pm, Doug Williams d...@twitter.com wrote: There is currently no way to receive this data through the API. As the issue you liked to above states, this is on the distant roadmap. Thanks, Doug -- Doug Williams Twitter Platform Supporthttp://twitter.com/dougw On Mon, May 18, 2009 at 1:57 PM, Lien Tran lientra...@gmail.com wrote: For user accounts that are set up as protected, is there a way to get follower requests (outside of standard email)? This request sort of goes hand in hand with http://code.google.com/p/twitter-api/issues/detail?id=521.
[twitter-dev] rate-limit and whitelisting
Apologies if this question seems like it's obvious or has already been answered but I read through several posts on this topic as well as the API documentation and I'm still confused. The documentation states: The default rate limit for calls to the REST API is 100 requests per hour. The REST API does account- and IP- based rate limiting. Authenticated API calls are charged to the authenticating user's limit while unauthenticated API calls are deducted from the calling IP address' allotment. QUESTION 1: Does this mean that if my user is signed up with multiple Twitter applications, then the total number of requests that those applications can make on behalf of my user is 100? That is, the 100 rate limit is split across all the applications? The documentation also states we offer whitelisting which will raise an accout or IP address' rate limit to 2 requests per hour. QUESTION 2: If I have a application server with several hundred thousand users, and I have my IP address whitelisted, does this mean I can make only 2 requests per hour for all users that are registered with my server? If so, then I'm not sure how whitelisting will help me here. Am I better off with just relying on the account rate limit of 100? Thanks, Lien
[twitter-dev] Re: Maximum length of a direct message?
The website enforces it, but it's not enforced when using the Twitter REST API. Are there any plans to enforce this? If so, what would be the expected error code returned if a message longer than 140 is sent in the request? On Mar 3, 1:30 pm, TjL luo...@gmail.com wrote: On Tue, Mar 3, 2009 at 2:54 PM, Alex Payne a...@twitter.com wrote: Our system may allow for DMs of longer than 140 characters, but I don't know if we'll support that in perpetuity. Hence, what's documented. The website just recently (IIRC) started to enforce the 140 characters rule in the past week or so. Before that it was possible to send longer DMs even though the counter was below 0. TjL
Is there a way to get a user's friends?
The friends method Returns up to 100 of the authenticating user's friends who have most recently updated, each with current status inline. It's also possible to request another user's recent friends list via the id parameter below. but this method does not provide an easy way to get all my friends, regardless of when they last updated their status. Thanks, Lien
Re: Problems with updating profile image
Thanks Alex. I used curl to see what the request should look like and then coded up my request accordingly. It's working for me now. On Dec 6, 11:37 am, Alex Payne [EMAIL PROTECTED] wrote: The test we use for this method is to use curl: curl -F '[EMAIL PROTECTED]/to/test/image.jpg' -u USERNAME:PASSWORDhttp://twitter.com/account/update_profile_image.xml If you use an HTTP proxy, you can see it generating the appropriate request and response. On Sat, Dec 6, 2008 at 00:09, Lien Tran [EMAIL PROTECTED] wrote: Hello, I've been trying to update myprofileimageusing the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying to upload is a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Problems with updating profile image
Hello, I've been trying to update my profile image using the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying to upload is a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks.
Re: New API methods for updating profile design and images
Hi, Does anyone have a sample of what the HTTP Request POST body should look like? Thanks, Lien On Oct 23, 7:54 am, Alex Payne [EMAIL PROTECTED] wrote: Not any time soon, but we'll keep it in mind. On Wed, Oct 22, 2008 at 10:34 PM, Richie [EMAIL PROTECTED] wrote: Cool. Are there any plans on allowing to update images by adding an url- parameter instead of raw multipart images? This would make the API much simpler to use, but I guess there might be security issues. Richie. On Oct 23, 2:07 am, Alex Payne [EMAIL PROTECTED] wrote: We missed that bit, but we'll be adding a parameter to the update_profile_background_image method that lets you set whether or not it tiles. On Wed, Oct 22, 2008 at 2:52 PM, Richie [EMAIL PROTECTED] wrote: Hi Alex, this looks great. I got some ideas for this allready. One question: How to setprofilebackgroundimagetiles? Thanks, Richie On Oct 21, 8:10 pm, Alex Payne [EMAIL PROTECTED] wrote: Hi all! Some new API methods for you to play with: - /account/update_profile_colors updates the colors on a user's profile(also returned via the /users/show API method) - /account/update_profile_image sets a newprofileimagefor a user - /account/update_profile_background_image sets, you guessed it, a new backgroundimagefor a user'sprofile You can find them all documented underhttp://apiwiki.twitter.com/REST%20API%20Documentation#AccountMethods. The clear use for these methods is a third-partyprofiledesign customizer (basically, a Twitter theme site). Geo apps might want to grab a photo of where the user is at and set it as theirprofile backgroundimage. That sort of thing. Enjoy, and let us know if you find any bugs. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Return user information in verify_credentials instead of just string representing authorized?
Thanks, I filed Issue 173: http://code.google.com/p/twitter-api/issues/detail?id=173 On Oct 30, 1:46 pm, Alex Payne [EMAIL PROTECTED] wrote: Sure, that's a thing we could do. Please request it:http://code.google.com/p/twitter-api/issues/entry On Thu, Oct 30, 2008 at 11:56 AM,LienTran [EMAIL PROTECTED] wrote: Return user information in verify_credentials instead of just string representing authorized? Useful if we could get the user id at this time instead of having to make a separate call to get the data. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Return user information in verify_credentials instead of just string representing authorized?
Return user information in verify_credentials instead of just string representing authorized? Useful if we could get the user id at this time instead of having to make a separate call to get the data.
Return user information in verify_credentials instead of just string representing authorized?
Return user information in verify_credentials instead of just string representing authorized? Useful if we could get the user id at this time instead of having to make a separate call to get the data.
