git clone ''

(ql:quickload :humbler)

About Humbler

Humbler is a Tumblr API interface that attempts to make it as little of a pain to use as possible. oAuth login and signing is handled by South.

How To

Before you can use Tumblr's API you'll need an application. Copy both the consumer key and secret and plug them into South:

 :api-key key
 :api-secret secret)

Humbler should configure South automatically to use the correct oAuth URLs and provides a simple LOGIN function.


This should return an URL if successful. Open this URL in your browser and allow the application access. It should redirect you to a localhost address, which then completes the authentication process automatically. It should also set up your local user object.

(humbler:name humbler:*user*)

Humbler offers an object-oriented interface that tries to take a lot of manual work off your hands and a lower-level API-mapping. Here's an example using both to create a text post:

(humbler:blog/post-text "my-blog" "Hey, testing this Common Lisp library called Humbler..." :title "Whoa nelly!")

(humbler:save (make-instance 'humbler:text-post :body "Nobody reads text posts anyway." :title "Welp."))

While the low-level functions have some limitations and oddities about them (max 20 results on a listing every call, strange inconsistencies, partial objects) due to the way Tumblr's API is made, the high-level functions try to smoothen over these issues so you don't have to worry about them. If for some reason you hate automatisation or how this abstraction works, you are of course free to build your own on top of the bare API calls though.

Humbler's symbols are split into three packages: HUMBLER-API which contains the API mapping functions, HUMBLER-OBJECTS containing the object and generic function interface, and finally HUMBLER-EXTRA with some functions to help deal with Tumblr (only programmatically, not mentally).

Deferred Slots

Tumblr's API doesn't always return complete objects; some calls only return a slice of the fields an object may exhibit. Humbler tries to take this annoying management off your hands by automatically augmenting your object with slot values from a fitting API call if you try to access it and it is not yet bound. If it fails to augment a slot, either because it does not know any API call to use to retrieve it or because something else went wrong, an error is signalled instead.

Multiple Users, Multiple South Applications

If you need to allow multiple users or south-using applications simultaneously, you'll need to handle the login and environment establishment yourself. Have a look at the South documentation for more information on how to go about this. This functionality is not included in Humbler directly as it is too complex to handle in a generic way.

More Examples

Post to all your blogs:

(dolist (blog (my-blogs))
  (repost (make-instance 'text-post :body "Hi!") blog))

Reblog the last 100 photos from a blog:

(mapcar #'reblog (posts "cool-photo-blog" :type :photo :amount 100))

View the most recent text posts from a tag:

(mapcar #'body (remove-if-not #'text-post-p (tag "interesting-tag)))

Delete all your drafts:

(mapcar #'destroy (my-drafts :amount T))

Interactively reply to all your asks:

(dolist (sub (my-submissions :amount T))
  (when (answer-post-p sub)
    (format T "~a: ~a~%" (asking-name sub) (question sub))
    (reply sub (read-line))))

Further Reading