Version 1.1 of the Context Voice is out. And we have many things to announce:

New calls and parameters

You probably noticed it takes a long time to get a conversation that has many thousand reactions. We did a few things to improve this issue:

1. We know have 2 endpoints: one for reactions (where you just get the comments for an URL) and one for a resource (that you can use to get meta-data about a URL-based conversation). So for things like title, content or generator of a URL you know have a new endpoint called at http://api.contextvoice.com/1.1/resources
2. We introduce paginated responses – if you read the documentation you will see two parameters: page and perpage that will help you achieve this. You no longer have to download megabytes for one response
3. We automatically track top-blogs. And now we update them faster.
4. You can now order the reactions asc/desc using the ‘created_at‘ field

New platforms

We now introduce 4 new platforms where we gather comments/reactions from: StumbleUpon, Delicious, Mixx and NewYorkTimes. What this means is than from now on we also get comments from NewYorkTimes website and for all the links in our index we get comments from StumbleUpon, Delicious, Mixx.

Simple Update Protocol

We now support Simple Update Protocol or simply SUP. SUP is a project developed and maintained by the good folks at FriendFeed. Context Voice SUP is a a simple and compact “ping feed” that alerts your web app when a conversation has been updated. This reduces update latency and improves efficiency by eliminating the need for frequent polling. Not so many calls means less bandwidth and for paying customers money savings.

Context Voice SUP is available at http://api.contextvoice.com/sup.json/?apikey=yourapikey

Non-authenticated calls

You can now make non-authenticated calls to get reactions for a given URL. So if you only need to get comments for a given URL use http://externalapi.contextvoice.com/1.1/reactions/?url=http://www.yoururl.com

You are restricted to 500 anonymous call per day per IP. This way of using Context Voice API is perfect for plugins, widgets or any type of app that’s distributed on users machines rather than running from one server with one IP address.

That’s about it… Let us know what you think. We welcome any feedback.

Anything else? We also have a new page with wrappers: a Ruby one and a PHP one. Many thanks to the wonderful people who developed them.

PS 1: “What about search?” you may ask. We know… we know. It’s coming but we need a little bit more time to polish and document it. Bare with us and you will not be dissapointed.

PS 2: version 1.0 is still supported by the way. You can even use the new platforms with it. But we recommend you switch to the new version asap.

Related articles by Zemanta

• StumbleUpon’s Su.pr URL Shortening Service Is Now In Private Beta (250 Invites) (techcrunch.com)
• Mixx Still Growing (But Not Fast Enough), Relaunches Website (techcrunch.com)
• 5 Essential Steps to Make Your Site Search & Social Media Friendly (mashable.com)