Blogger API > XML-RPC >

Alert This documentation is provided for historical interest only. The Blogger 1.0 API is no longer supported and must not be used for new client development. Please use our GData API instead. — phopkins, 4/2007

blogger.editPost via XML-RPC

By Evan Williams, 8/13/01

blogger.editPost changes the contents of a given post. Optionally, will publish the blog the post belongs to after changing the post. On success, it returns a boolean true value. On error, it will return a fault with an error message.

URI

All XML-RPC requests should go to the following URI: http://plant.blogger.com/api/RPC2

Note: This could (and, likely, will) change at some point! (Due warning will be given.)


Parameters

blogger.editPost takes the following parameters. All are required:
  1. appkey (string): Unique identifier/passcode of the application sending the post. (See access info.)
  2. postid (string): Unique identifier of the post to be changed.
  3. username (string): Login for a Blogger user who has permission to edit the given post (either the user who originally created it or an admin of the blog).
  4. password (string): Password for said username.
  5. content (string): New content of the post.
  6. publish (boolean): If true, the blog will be published immediately after the post is made.

    NOTE: Ther FTP username/password must be saved in the Blogger database (entered via Settings in the main interface) for the publish option to work.


Examples

Here is an example of an XML-RPC call to blogger.editPost:
POST /api/RPC2 HTTP/1.0 User-Agent: Java.Net Wa-Wa 2.0 Host: plant.blogger.com Content-Type: text/xml Content-length: 515 <?xml version="1.0"?> <methodCall> <methodName>blogger.editPost</methodName> <params> <param><value><string>C6CE3FFB3174106584CBB250C0B0519BF4E294</string></value></param> <param><value><string>7441452</string></value></param> <param><value><string>ewilliams</string></value></param> <param><value><string>secret</string></value></param> <param><value><string>Today I had a peanut butter and banana sandwich for lunch. Do you like peanut-butter and banana sandwiches? I do. They're yummy. Please comment!</string></value></param> <param><value><boolean>false</boolean></value></param> </params> </methodCall>
Here is an example methodResponse with no errors:
HTTP/1.1 200 OK Connection: close Content-Length: 125 Content-Type: text/xml Date: Mon, 6 Aug 20001 19:55:08 GMT Server: Java.Net Wa-Wa/Linux <?xml version="1.0"?> <methodResponse> <params> <param> <value><boolean>1</boolean></value> </param> </params> </methodResponse>

Errors

Errors are returned as an XML-RPC <methodResponse> with a <fault> item, containing a <struct> with a faultCode and a faultString, as defined by the XML-RPC spec.

Here an example response for an unsuccessful post. This error is due to a bad appkey:

HTTP/1.1 200 OK Connection: close Content-Length: 225 Content-Type: text/xml Date: Mon, 6 Aug 20001 19:55:08 GMT Server: Java.Net Wa-Wa/Linux <?xml version="1.0"?> <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value><int>4</int></value> </member> <member> <name>faultString</name> <value><string>java.lang.Exception: java.lang.Exception: Error: AppKey is invalid or inactive.</string></value> </member> </struct> </value> </fault> </methodResponse>
That error message doesn't make as much sense as it should, but we'll work on that.

Copyright © 2001 Pyra Labs