Many of you have been dismayed that you could not override the callback url when a user was attempting to authorize their application. Good news: we’ve patched the bug that was causing this particular issue.
Now, you can pass a url with the oauth_callback parameter and we will redirect the user to that endpoint once you’re done.
Let’s go over a quick example.
When the user is presented with the screen to authorize your app, you should be able to override your default callback with the oauth_callback parameter in your url.
http://www.tumblr.com/oauth/authorize?oauth_token=your_token&oauth_callback=http%3A%2F%2Fmysite.com/oauth_callback/testing
The above url will redirect the user to mysite.com/oauth_callback/testing and let you know if the user has approved or denied your app.
Some more minor fixes:
callback parameter is now allowed when making JSONP requests.limit parameter was not being respected in the tagged route./user/queue path now respects limit. You can request up to 50 posts at one time, and the default is set to 20./user/info should be a GET requestPlease check out the latest documentation for any further details. If you have any questions or concerns, ourAsk box is always open.