Hey all, I'm playing around with the Twitter OAuth API, having rolled my own clients in both ruby and Objective-C. I've managed to authorise myself successfully and send status updates, but api methods like direct_messages/new always give me 401 errors.
I know I'm missing something elementary in the way I'm making the calls, so I just want to clarify a couple of things: - From what I understand in the doc, do the parameters for a POST request go in the body? (I saw a reference to adding them as query params in the url string but that seems to have been removed). - Looking at the OAuth spec and the example on the auth page, can I assume POST parameters are ordered alphabetically along with the other params when building the base string? Do they have to be doubly url encoded? Here's a quick excerpt of the ruby client I put together: https://gist.github.com/1033130 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk