Connect your organization to Google+ using the Google+ Domains API

Tuesday, August 13, 2013 | 11:28 AM

Google+ make it easy for Google Apps customers to connect and share within their organisation and encourage collaboration between teams. Today we’re launching an update to the Google+ Android app that includes a number of new features for Google Apps customers, and a new developer offering, the Google+ Domains API.

The Google+ Domains API allows Google Apps customers to integrate Google+ into their existing tools and processes, and allows enterprise software vendors to access Google+ from their products. Applications using the Google+ Domains API can act on behalf of Google Apps users to share posts within the same domain, comment on posts shared within the domain, and manage Circles. In addition, the Google+ Domains API enables Google Apps domain administrators to pre-populate the Circles of new employees, or review sharing activity.

For example, Ocado is building a tool that uses the Google+ Domains API to regularly sync team membership stored in Active Directory with the circles of their employees. This will ensure that every employee always has an up to date circle containing the other members of their team. Cloudlock is using the Google+ Domains API to add support for Google+ to its suite of data loss prevention, governance, and compliance applications.


Any developer can begin developing with the Google+ Domains API today. However only members of a Google Apps domain can use Google+ Domains API applications. To get started check out the documentation. If you have any questions, you can consult the google-plus tag on Stack Overflow, or join the “Developing with Google+” Google+ Community.


Posted by Thor Mitchell, Product Manager, Google+ API

Cross posted on the Google+ Developers blog.

1 comments:

Chris said...

The idea of creating pre-populated (and updating) circles is very interesting, but I wonder how it scales. What if I have thousands of employees to sync nightly? Creating and maintaining circles for all of them seems like it could be taxing on the system once the number and size of circles reaches a certain point.

Example:
Employee A has a circle with Employees B and C.
Employee B has a circle with Employees A and C.
Employee C has a circle with Employees A and B.

That's three circles to maintain, each with three members within to also maintain (if Employee A changes teams, I have to update these three employees, plus all of the employees of the new team). That's manageable, but several hundred circles with dozens of members each is going to mean a lot of processing.

Is there a similar API to have employees join a community, or a page? That would be more of a one-to-many relationship rather than many-to-many and could be a lot easier to manage.

Example:
Employee A is a member of Community 1.
Employee B is a member of Community 1.
Employee C is a member of Community 1.

Under this model, if Employee A changes teams, I only need to update one membership.