Wouldn't it be great to expose IP.Board data via REST API?

As developers we need REST API methods to send and receive IP.Board data is some format like JSON or XML.
As a matter of fact, at the time I'm writing this, it's hard to find popular web applications that have not yet decided to support these APIs and published their documentation/methods list!

• Twitter REST API: http://apiwiki.twitt...I-Documentation
• Facebook REST-like interface: http://wiki.develope...m/index.php/API and its Open Stream API.
• 37signals Basecamp REST principles: http://developer.37s...s.com/basecamp/
• Zendesk REST API: http://www.zendesk.c...st_introduction
• Mailchimp JSON/XML documentation: http://www.mailchimp.com/api/
• Google AJAX Search RESTful interface and JSON: http://code.google.c.../documentation/
• Flickr REST request/response format: http://www.flickr.co...quest.rest.html - http://www.flickr.co...ponse.rest.html
• Amazon S3 REST API: http://docs.amazonwe...ev/RESTAPI.html
• Et cetera, et cetera, et cetera... :)

Question - When IPS, Inc. intends to publish the REST API documentation and the full list of methods? Then the new opportunities would be wonderful!

Thanks.

We have the XML skin which you could use with REST to retrieve almost any data.
This topic, for example: http://community.invisionpower.com/xml.php?showtopic=308582

We also have an open XML-RPC API which you can use to develop your own APIs for retrieving or submitting data:
http://community.invisionpower.com/resources/official.html?record=246


Is there something specific you're trying to do? I'm sure we could you point you in the right direction :)

We also have an open XML-RPC API which you can use to develop your own APIs

[...]

Is there something specific you're trying to do?

Hi Mark, we would like to extend and integrate IP.Board with other popular web applications and vice versa. In this scenario the client is primarily the browser rather than a desktop application. An advantage of REST over XML-RPC is that each object has its own URL and can easily be cached, copied, and bookmarked. I think REST is the best with browser based clients.
What we would need is a nice list of methods (including GET/POST, etc.) along the lines of Twitter API Documentation. ;)

We have the XML skin which you could use with REST to retrieve almost any data.

This topic, for example: [url="http://community.invisionpower.com/xml.php?showtopic=308582"]http://community.inv...howtopic=308582[/url]

Consuming that would be crashtastic. You don't enclose your "text" element in CDATA blocks, resulting in XML elements being in the middle of the text.

I would also really like to see json response instead of xml response which will allow to integrate IPB to FB and other rich web apps

+1
I also need REST API with support for XML/JSON

+1
Any news (or plan) about that?

Thanks,

Definitely a value add for me development wise if IPB offered REST/JSON support