The Blogger API (XML-RPC)

Nucleus implements the Blogger API. This allows for tools and services that can communicate with Blogger, to be able to also communicate with Nucleus. Because the way Nucleus works, some interpretations of parameters are slightly different, see the notes below for more info. The structure of method calls and responses are, of course, exactly the same as the methods at Blogger.

Here's the list of available methods. Click them to get more information (links go to either the Blogger API or the Blogger API Mailinglist).

Since Nucleus is structured somewhat differently inside, there are some differences in the way parameters are handled. An overview:

  • Appkeys are ignored.
  • Next to the body of a post, a Nucleus-item also has a title and a category. Blogger only has the body (known as 'contents'). To be able to use the extra parts, you can use <title> and <category> in the contents you send to Nucleus. These tags are only added in the getRecentPosts call
  • What is known under Blogger as 'templates', is known under Nucleus as 'skins'. There can be more than one skin on the system, and each skin can be used by different blogs. The blogger.setTemplate and blogger.getTemplate methods will affect the default skin for the chosen blog, as selected in the Nucleus blog settings. The 'main' and 'archiveIndex' template types refer to the nucleus skinparts 'index' and 'archivelist'
  • The publish parameter is used to determine wether a new post is to be added as a draft or not. When using blogger.editPost, the publish parameter is ignored unless it turns a draft into a published item
  • When using the getUserInfo call, the 'lastname' in the result will be empty and 'firstname' will contain the full name. This is because Nucleus does not make a difference between first name and last name
  • The getRecentPostst-method returns authorName and title as extra parameters. Blogger has been returning these also (although undocumented)
XML-RPC Interface