Hi TJ, To be able to send POST requests to the API you need to ensure your application is of access type: Read & Write The message you are getting means your application is Read Only. To change this you need to visit http://dev.twitter.com/apps and then edit the details of your application so that the access type is Read & Write.
This will only change access tokens issues from then on so any users who have already authorised your application will need to be sent through the OAuth process again. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Jan 3, 2011 at 7:08 AM, Tom van der Woerdt <[email protected]> wrote: > It means that your application and tokens are read-only... obviously :-) > You can't write anything when you have a read-only app. > > Tom > > > > On 1/3/11 4:01 PM, TJ Luoma wrote: > >> I have authorized twurl successfully but when I try to create a block, >> it tells me that it's read only >> >> >> # twurl -t -d "screen_name=dwikirowi" "/1/blocks/create.xml" >> opening connection to api.twitter.com... >> opened >> <- "POST /1/blocks/create.xml HTTP/1.1\r\nAccept: */*\r\nConnection: >> close\r\nUser-Agent: OAuth gem v0.4.4\r\nContent-Type: >> application/x-www-form-urlencoded\r\nAuthorization: OAuth >> oauth_consumer_key=\"EK9yzQy6K8gqzAg0pCaQug\", >> oauth_nonce=\"TpGOfe8bnzD74N5Ixrpjaip1PfscSkxTYLlYvXqzs14\", >> oauth_signature=\"yX1suHCZxeGf3pyjNCdkOE5F7rw%3D\", >> oauth_signature_method=\"HMAC-SHA1\", oauth_timestamp=\"1294066225\", >> oauth_token=\"7344012-fsOhwagPQXaz627NUEI9jbxUFyF4QBQakZeikJsoIA\", >> oauth_version=\"1.0\"\r\nContent-Length: 21\r\nHost: >> api.twitter.com\r\n\r\n" >> <- "screen_name=dwikirowi" >> -> "HTTP/1.1 401 Unauthorized\r\n" >> -> "Date: Mon, 03 Jan 2011 14:50:25 GMT\r\n" >> -> "Server: hi\r\n" >> -> "Status: 401 Unauthorized\r\n" >> -> "WWW-Authenticate: Basic realm=\"Twitter API\"\r\n" >> -> "Content-Type: application/xml; charset=utf-8\r\n" >> -> "Content-Length: 147\r\n" >> -> "Cache-Control: no-cache, max-age=1800\r\n" >> -> "Set-Cookie: k=99.174.173.56.1294066225492468; path=/; expires=Mon, >> 10-Jan-11 14:50:25 GMT; domain=.twitter.com\r\n" >> -> "Set-Cookie: guest_id=129406622564378748; path=/; expires=Wed, 02 >> Feb 2011 14:50:25 GMT\r\n" >> -> "Set-Cookie: >> >> _twitter_sess=BAh7CDoHaWQiJTc1YmY4YzA2YTZiNmE1MWIzZjI5N2M2NmQ4MjEyODE4Igpm%250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG%250AOgpAdXNlZHsAOg9jcmVhdGVkX2F0bCsI95FbTC0B--0032072eac8637c5b993db5512109cee00605655; >> domain=.twitter.com; path=/\r\n" >> -> "Expires: Mon, 03 Jan 2011 15:20:25 GMT\r\n" >> -> "Vary: Accept-Encoding\r\n" >> -> "Connection: close\r\n" >> -> "\r\n" >> reading 147 bytes... >> -> "" >> -> "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<hash>\n >> <request>/1/blocks/create.xml</request>\n<error>Read-only >> application cannot POST</error>\n</hash>\n" >> read 147 bytes >> Conn close >> <?xml version="1.0" encoding="UTF-8"?> >> <hash> >> <request>/1/blocks/create.xml</request> >> <error>Read-only application cannot POST</error> >> </hash> >> >> > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
