Cannot reblog a tumblr post

Hello! I am using your OAuth API to integrate my website with Tumblr. Unfortunately, I cannot reblog any post, I always get a 401/Not Authorized error in the response.

This is the code:


/////////////////////
$oauth = new oauth_client_class();
$oauth->debug = true;
$oauth->server = 'Tumblr';
$oauth->client_id = Configure::read('tumblr_app_id');
$oauth->client_secret = Configure::read('tumblr_app_secret');
$oauth->Initialize();

if($oauth->Process()) {
$post_id = 40683854239;
$post_reblog_key = 'etDEKiko';

$params = array(
'id' => $post_id,
'reblog_key' => $post_reblog_key
);

$success = $oauth->CallAPI(
'http://api.tumblr.com/v2/blog/nicolas-vnstudios.tumblr.com/post/reblog',
'POST',
$params,
array('FailOnAccessError' => false),
$response
);
var_dump($success);
var_dump($response);

///////////////

However, when I use CallAPI to like a post, it works fine:

//////////
$response = array();
$success = $oauth->CallAPI(
'http://api.tumblr.com/v2/user/like',
'POST',
$params,
array('FailOnAccessError' => false),
$response
);
var_dump($success);
var_dump($response);

///////////////////


Do you know why isn't it working? Am I doing something wrong?
Thanks in advance.

I was able to reblog that article successfully with this code.

$success = $client->CallAPI(
'http://api.tumblr.com/v2/blog/mallemos.tumblr.com/post/reblog',
'POST', array('id'=>'40683854239', 'reblog_key' => 'etDEKiko'),
array('FailOnAccessError'=>true), $reblog);

Are you using the latest version of the class?

Hello Manuel! Your library is very usefull and just great! Thank you very much for it!
I also have a similar problem like Nico Zerpa does. All the tumblr's functionality works fine for me (like, follow, info, etc.), but each time when I try to use /post/reblog I have the same 401 error. I think this is not an issue of your lib, but just issue of Tumblr.
I am using the last version of your lib, also I tried to use your example

$success = $client->CallAPI(
'http://api.tumblr.com/v2/blog/mallemos.tumblr.com/post/reblog',
'POST', array('id'=>'40683854239', 'reblog_key' => 'etDEKiko'),
array('FailOnAccessError'=>true), $reblog);
but I have the same 401 error (Not Authorized).
Can you please help me (maybe you have a bigger experience with the Tumblr then I)?
Thank you in advance!

I have tried it over and over again and it works flawlessly.

The only thing I can think is that you are calling the CallAPI function separately and the access_token_secret is not really set to a token secret value previously obtained from the server.

Manuel, thank you for your answer. I have checked the script one more time, the "reblog" functionality works only for my own page, so I can reblog my own posts but I can't make it for other blogs. I think that this is the Tumblr's issue, because in web interface (directly on "any_name_of_blog".tumblr.com I can reblog any post and can't via API).

I am not sure about that. For me it worked with every page I tried, even from other people.

I also tried putting the incorrect reblog key or page id and it gave error 400, not 401.

It gave me error 401 when I intentionally set the access_token_secret variable to an empty string. So I would check if that variable is correctly set when you call the API.

Hello again, Manuel. I have tried to do like you mentioned, but nothing helps me. Can you please send me (if possible) the complete example (all the php code, all php files, include library) as zip-archive or so for me to test it on my side. Thank you in advance!

The example is the same as the one provided with the class. The only difference is that I send an API call to the reblog API URL.

When the user authorizes API access, the class retrieves two values in the access_token and access_token_secret variables. Do not confuse these two values with the client_id and client_secret values.

You need both of these values to send API calls. When the user is not present, you can still send API calls as long as you initialize those variables with the previously obtained values.

Your problem seems that you may be setting the access_token but probably not access_token_secret. That is a common cause for error 401.

Thank you Manueal one more time, I will try.