This changes a few things:

• Allows for numbers and boolean params to be sent to Tumblr's API.
  • Examples: Under /posts, limit is a Number and reblog_info is a Boolean.
• Include default_params consisting of the api_key, like before. If not, /posts requests don't work.
• In the event that the api_key that is sent in the params is wrong/expired, throw an AuthError.
• Allow the user to manipulate urllib3's maxsize via request's pool_maxsize for multi-threaded applications.
• Updated t.get_access_token to t.get_authorized_tokens in the README.

The Tumblr API returns and empty list (and not a dict) in some cases, e. g. if a blog was not found (404). In these case, calling content.get() raises an AttributeError. This commit fixes it.

Example for a 404 response: http://api.tumblr.com/v2/blog/cocofuckedchanel.tumblr.com/posts/

tried to use your python package but got below error...how can i fix this issue?

Traceback (most recent call last): File "test.py", line 4, in auth_props = t.get_authentication_tokens(callback_url='http://www.xyz.com/somecallbackurl/index.php') File "/opt/.softroot/python-tumblpy/tumblpy/api.py", line 61, in get_authentication_tokens raise TumblpyAuthError('Seems something couldn't be verified with your OAuth junk. Error: %s, Message: %s' % (response.status_code, response.content)) tumblpy.exceptions.TumblpyAuthError: Seems something couldn't be verified with your OAuth junk. Error: 401, Message: oauth_timestamp is too far away; we believe it is now 1390665118, you sent 1390643508, 21610 seconds away

Post requests didn't include the type parameter, so they would fail. For instance, the example in the readme for posting an image didn't work.

I'm not sure if this is the best way to solve the problem, but it makes it so I can submit post requests to the api.

Is it possible to use this library to post something to secondary blog?

I authorized the app and I took a look at Tumblr console where I picked up all the keys from. I have noticed that I can successfully post to my primary blog, but not on secondary (getting {TumblpyError} 404 'There was an error making your request.' error all the time).

This is my current code:

from tumblpy import Tumblpy


def post_tumblr(
        url,
        comment='',
        tags='',
        **kwargs
):
    t = Tumblpy(
        APP_KEY, APP_SECRET,
        OAUTH_TOKEN, OAUTH_TOKEN_SECRET
    )

    blog_url = t.post('user/info')
    blog_url = blog_url['user']['blogs'][0]['url']  # POSTING TO PRIMARY BLOG WORKS
    # blog_url = blog_url['user']['blogs'][1]['url']  # CANNOT POST TO SECONDARY BLOG?

    post_url = t.post(
        'post',
        blog_url=blog_url,
        params={
            'type': 'video',
            'embed': url,
            'caption': comment,
            'tags': tags,
        }
    )

    return True

'Error: 401, Message: {"meta":{"status":401,"msg":"Not Authorized"},"response":[]}' while posting an image using "data" parameter. I followed your example and that's the error I got. Is this a bug?

I'm getting the next error everytime I try to post something:

File "C:\Python27\lib\site-packages\tumblpy.py", line 259, in post extra_endpoints=extra_endpoints, params=params) File "C:\Python27\lib\site-packages\tumblpy.py", line 222, in request raise TumblpyAuthError('Error: %s, Message: %s' % (response.status_code, response.content)) tumblpy.TumblpyAuthError: 'Error: 401, Message: {"meta":{"status":401,"msg":"Not Authorized"},"response":[]}'

I don't know if is from my code or if is from the library.

Hello,

Trying to use the post method for a text post.

t = Tumblpy(TUMBLR_CONSUMER_KEY, TUMBLR_CONSUMER_SECRET,
            TUMBLR_ACCESS_KEY, TUMBLR_ACCESS_SECRET)

        blog_url = t.post('user/info')
        blog_url = blog_url['user']['blogs'][0]['url']
        blog_url = blog_url.replace('http://', '')
        blog_url = blog_url.replace('/', '')
        print(blog_url)

        try:
            if image:
                #Create a photo post using a local filepath
                post = t.post('post', blog_url=blog_url, params={'type':'photo', 'caption': text, 'data': image})
            elif url:
                #Create a link post
                post = t.post('post', blog_url=blog_url, params={'type':'link', 'url': url, 'description': text})
            else:
                print('im definitely text')
                #Create a text post
                post = t.post('post', blog_url=blog_url, params={'type':'text', 'body': text})
        except Exception as e:
            import pdb; pdb.set_trace()
            print(e)

        return HttpResponse(status=200)

The text is just a normal string. I'm using Pythin 3.4.

Error is tumblpy.exceptions.TumblpyError: There was an error making your request. and error_code is 404

Any ideas why this isn't working? Thanks!

Everything seems to be working now, though lacking tests, it's hard to know specifically if it's working, but it's working for my follower tracker that I'm working on.

Using the following:

t.post('post/reblog', params={'id':someid,'reblog_key':somereblog_key})

I get:

Invalid ID or reblog_key specified

I have double checked the reblog key on the post and the id, these are correct, however no matter what I do I get that result, I even built my own module to reblog posts in request_oauthlib!

Fix issues with GET requests in get_authentication_tokens and get_authorized_tokens returns value in bytes and needed to be decoded before response data can be worked with.

The response.content would return an dict with the keys and values encoded;

{b'oauth_token': b'Yh...token...EQ', b'oauth_token_secret': b'YH...token...gO', b'oauth_callback_confirmed': b'true'}

It appears that when Tumblr is having issues, error responses can be different than expected.

I got the error: AttributeError: 'str' object has no attribute 'get'

Sentry recorded that content was a str instead of a dict. The status code was 504.

Relevant line: https://github.com/michaelhelmick/python-tumblpy/blob/master/tumblpy/api.py#L165

It seems like the easiest fix would be to check if the response was a str and if it was, use that for the error_message. Also, in looking at that code, it appears error_message gets written over for every error instead of being appended to. This seems like it could be fixed by ', '.join(content['errors']) instead of the loop.

If these seems like reasonable fixes, I'm happy to open a PR for them.