Social API Server Specification

The social API server specification is used for containers that wish to provide a developer the means to leverage their social data, but do not wish to host applications themselves.

This implementation means that containers provide a RESTful method for developers to get, update, insert, and delete their social data. This social data may include:

  • OpenSocial Person information (the user profile), including a user’s friendships and relationships

  • Activity information and actions taken by the user

  • Direct messages sent or to be sent by a user

  • Group information associated with the user

  • Albums and media items

This option is best suited for containers that have a social experience built in but have no desire to integrate applications. These containers may include sites that allow geolocation for their users and commenting about status updates—data that developers can then link to programmatically. Even though the container does not host applications itself, this implementation lends itself well to building applications on mobile devices or other sites that leverage the container’s data sources.

Full specification requirements for the social API server implementation are available at http://opensocial-resources.googlecode.com/svn/spec/1.0/Social-API-Server.xml.

Get Programming Social Applications now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.