Igor Clark
unread,Jan 20, 2012, 5:21:11 PM1/20/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Tumblr API Discussion
Hi there
My OAuth client is failing at the "request access token" stage,
apparently because I'm not providing an oauth_verifier:
{{"HTTP/1.1",400,"Bad Request"}
[{"connection","close"},
{"date","Fri, 20 Jan 2012 19:44:11 GMT"},
{"server","Apache"},
{"vary","Accept-Encoding"},
{"content-length","34"},
{"content-type","text/html; charset=UTF-8"},
{"p3p","CP=\"ALL ADM DEV PSAi COM OUR OTRo STP IND ONL\""},
{"x-tumblr-usec","D=22003"}]
"Missing or invalid oauth_verifier."}
As I understand it, that's because I'm not following the web-page flow
to get the OAuth verifier token. Is that right?
If so, the thing is, I'm trying to do this all unmanned on the back-
end, so I can't follow that flow.
As an example of how I'd do this elsewhere, Twitter provide access
tokens and access token secrets per-app, directly in their dev site,
so that developers can create valid OAuth signatures without having to
jump through web flow hoops.
Am I missing this somewhere in the Tumblr API site or documentation?
If so, how do I get my access token/secret to use in this way? If not,
is there any plan to support this kind of use? Seems unlikely that I'm
the first person to want to do that :-)
Cheers,
Igor Clark
(PS I only discovered this group after mailing support at tumblr dot
com, sorry about that)