Yes, we have a global catch-all rule that all POST operations are write operations.
User/lookup is typically a GET operation anyway ( http://dev.twitter.com/doc/get/users/lookup ) and you can pass the up-to 100 ids as a long query string parameter, provided your HTTP implementation allows for the length you're aiming for. For best results with the lookup API, I recommend keeping the limit a bit below 100 for best operations. Taylor On Tue, Sep 7, 2010 at 10:43 AM, Brian Maso <br...@blumenfeld-maso.com> wrote: > I just started getting this error message within the past hour for my > application. My application is "read-only" in the sense that it never > updates a user profile or posts any tweets or anything. My application > does, however, use the users/lookup.json API, and I use POST because I > am requesting many profiles at once when I use the API. > > Does the "Read-only" indication on my application's profile mean I can > never use POST? Anyone else seeing anything similar? > > Brian Maso > > -- > 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?hl=en > -- 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?hl=en