Peers.me API
Peers.me provides an API for public profiles and published waves which can be used for your website or any other platform.
All API access is over HTTP. Responses are default in XML but JSON is also possible. Just use .json in your call.
Currently, no API key is required, the authentication is performed via HTTP (only "Basic" is supported), and you'll need to transmit your API Username and Password to perform requests. To get an API Username and Password, contact us.
Peers.me API Libraries
There is currently one plugin available for use with the Peers.me API:
Things you need to know
Wave address
Groups and users have an address which is unique for that specific [subdomain].peers.me.
Avatar url
Sometimes you'll receive some avatar_url with a ":style" in the url. You can change the ":style" with something like; mini, small, medium, large or original.
Publications
Publications are published waves with two different outputs for the text; plain-text and html. A publication has an wave_url which points to the original wave. You'll only access the wave if you're (or one of your groups is) a participant on that specific wave.
Query
It's not yet possible to query a API call for sorting.
You can get a multiple [address] output if you'll comma-separate the addresses like /api/addresses/[address_1],[address_2],[address_3].
Need help?
Please check our support forum or start a ticket.
API Calls
GET /api/addresses/
Returns all public addresses, sorted by name.
Works also for:
/api/users/ (for all users)
/api/groups/ (for all groups)
Example XML
<addresses>
<user>
<address>daniel</address>
<label/>
<name>Daniël Steginga</name>
<avatar_url>http://dev.peers.me/avatars/daniel/:style.png?1297965730</avatar_url>
<created_at type="datetime">2010-05-07 09:21:26 +0200</created_at>
</user>
<group>
<address>company</address>
<label>Organization</label>
<name>Company</name>
<avatar_url>http://dev.peers.me/avatars/company/:style.png?1297964457</avatar_url>
<created_at type="datetime">2010-05-12 15:34:31 +0200</created_at>
</group>
<user>
<address>richard</address>
<label/>
<name>Richard Mos</name>
<avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</avatar_url>
<created_at type="datetime">2010-05-06 17:56:28 +0200</created_at>
</user>
</addresses>GET /api/addresses/[address]
Returns the profile of an address. The root node shows the address-type; user or group.
Works also for:
/api/users/[address]
/api/groups/[address]
Example XML (user)
<user>
<address>daniel</address>
<label/>
<name>Daniël Steginga</name>
<avatar_url>http://dev.peers.me/avatars/daniel/:style.png?1297965730</avatar_url>
<company_name>Peers.me</company_name>
<last_name>Steginga</last_name>
<linkedin>http://nl.linkedin.com/in/danielsteginga</linkedin>
<twitter>http://www.twitter.com/danielsteginga</twitter>
<first_name>Daniël</first_name>
<info>My info</info>
<function>Design & Concept</function>
<flickr>[flick-address]</flickr>
<facebook>[facebook-address]</facebook>
<youtube>[youtube-address]</youtube>
<vimeo>[vimeo-address]</vimeo>
<skype>[skype-address]</skype>
<website>[personal-website-address</website>
<created_at type="datetime">2010-05-07 09:21:26 +0200</created_at>
</user>Example XML (group)
<group>
<address>company</address>
<label>Organization</label>
<name>Company</name>
<avatar_url>http://dev.peers.me/avatars/company/:style.png?1297965731</avatar_url>
<info>In 2008 Peers started with bespoke online communities for large Dutch Organizations.</info>
<created_at type="datetime">2010-05-12 15:34:31 +0200</created_at>
</group>GET /api/addresses/[address]/groups
Returns all groups for the [address], sorted by name.
Works also for:
/api/users/[address]/groups
/api/groups/[address]/groups
Example XML
<groups>
<group>
<address>company</address>
<label>Organization</label>
<name>Company</name>
<avatar_url>http://dev.peers.me/avatars/company/:style.png?1297965731</avatar_url>
<created_at type="datetime">2010-05-12 15:34:31 +0200</created_at>
</group>
<group>
<address>peers-college</address>
<label>Support</label>
<name>Peers College</name>
<avatar_url>http://dev.peers.me/avatars/peers-college/:style.png?1297965732</avatar_url>
<created_at type="datetime">2010-07-28 17:18:22 +0200</created_at>
</group>
</groups>GET /api/addresses/[address]/members
Returns all members for the [address], sorted by name.
Works also for:
/api/groups/[address]/members (for all groups)
Example XML
<members>
<user>
<address>daniel</address>
<label/>
<name>Daniël Steginga</name>
<avatar_url>http://dev.peers.me/avatars/daniel/:style.png?1297965730</avatar_url>
<created_at type="datetime">2010-05-07 09:21:26 +0200</created_at>
</user>
<user>
<address>richard</address>
<label/>
<name>Richard Mos</name>
<avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</avatar_url>
<created_at type="datetime">2010-05-06 17:56:28 +0200</created_at>
</user>
</members>GET /api/publications
Returns all publications, sorted by created_at, limited at 20.
There is an offset option which can be used with /api/publications?offset=[offset].
Example XML
<publications>
<publication>
<wave_id>w+VopH0D8PV0Pnp</wave_id>
<publisher>richard</publisher>
<publisher_name>Richard Mos</publisher_name>
<publisher_avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</publisher_avatar_url>
<placement>richard</placement>
<placement_name>Richard Mos</placement_name>
<publisher_avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</publisher_avatar_url>
<title>Vote for new features!</title>
<text>Customer feedback is very important to us, we use this feedback to prioritize, solve problems and identify new features. Until now we have received feedback through various channels like email, Google Wave, our on-line communities, telephone and face-to-face discussions. But did you know we also have a ...</text>
<wave_url>http://peers.me/waves/w+VopH0D8PV0Pnp</wave_url>
<agenda_date/>
<agenda_start_time/>
<agenda_end_time/>
<location/>
<created_at type="datetime">2010-07-29 12:04:00 +0200</created_at>
-<tags>
<tag>blog</tag>
</tags>
</publication>
<publication>
<wave_id>w+62qFJyA9PeCYg</wave_id>
<publisher>daniel</publisher>
<publisher_name>Daniël Steginga</publisher_name>
<publisher_avatar_url>http://dev.peers.me/avatars/daniel/:style.png?1297965730</publisher_avatar_url>
<placement>daniel</placement>
<placement_name>Daniël Steginga</placement_name>
<placement_avatar_url>http://dev.peers.me/avatars/daniel/:style.png?1297965730</placement_avatar_url>
<title>Peers update</title>
<text>*Feedback* In the next weeks we will work on new features. We want you to vote on our features. So the most important features are being developed first. If you have any great ideas, please share them with us and ...</text>
<wave_url>http://peers.me/waves/w+VopH0D8PV0Pnp</wave_url>
<agenda_date/>
<agenda_start_time/>
<agenda_end_time/>
<location/>
<created_at type="datetime">2010-07-19 13:49:44 +0200</created_at>
-<tags>
<tag>blog</tag>
</tags>
</publication>
</publications>GET /api/publications/[wave_id]
Returns the published wave.
Example XML
<publications>
<publication>
<wave_id>w+VopH0D8PV0Pnp</wave_id>
<publisher>richard</publisher>
<publisher_name>Richard Mos</publisher_name>
<publisher_avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</publisher_avatar_url>
<placement>richard</placement>
<placement_name>Richard Mos</placement_name>
<publisher_avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</publisher_avatar_url>
<title>Vote for new features!</title>
<text>Customer feedback is very important to us, we use this feedback to prioritize, solve problems and identify new features. Until now we have received feedback through various channels like email, Google Wave, our on-line communities, telephone and face-to-face discussions. But did you know we also have a ...</text>
<html type="html">Customer feedback is very important to us, we use this feedback to prioritize, solve problems and identify new features. Until now we have received feedback through various channels like email, Google Wave, our on-line communities, telephone and face-to-face discussions. But did you know we also have a ...</html>
<wave_url>http://peers.me/waves/w+VopH0D8PV0Pnp</wave_url>
<agenda_date/>
<agenda_start_time/>
<agenda_end_time/>
<location/>
<created_at type="datetime">2010-07-29 12:04:00 +0200</created_at>
-<attachments>
<attachment>
<url>http://peers.me/address/public/blog/228/attachments/attach+tHu6rirxG.png</url>
<mime_type>image/png</mime_type>
</attachment>
</attachments>
-<tags>
<tag>blog</tag>
</tags>
</publication>
</publications>GET /api/publications/?placements=[address]
Returns all publications for the placement from address [address], sorted by created_at, limited at 20.
Example XML
<publications>
<publication>
<wave_id>w+VopH0D8PV0Pnp</wave_id>
<publisher>richard</publisher>
<publisher_name>Richard Mos</publisher_name>
<publisher_avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</publisher_avatar_url>
<placement>richard</placement>
<placement_name>Richard Mos</placement_name>
<publisher_avatar_url>http://dev.peers.me/avatars/richard/:style.png?1297965732</publisher_avatar_url>
<title>Vote for new features!</title>
<text>Customer feedback is very important to us, we use this feedback to prioritize, solve problems and identify new features. Until now we have received feedback through various channels like email, Google Wave, our on-line communities, telephone and face-to-face discussions. But did you know we also have a ...</text>
<wave_url>http://peers.me/waves/w+VopH0D8PV0Pnp</wave_url>
<agenda_date/>
<agenda_start_time/>
<agenda_end_time/>
<location/>
<created_at type="datetime">2010-07-29 12:04:00 +0200</created_at>
-<tags>
<tag>blog</tag>
</tags>
</publication>
</publications>