Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, Google+ doesn't have a "wall," it has "Streams." The proper term might help you find better search results. Either way, unless you're a Google partner, the news isn't good:</p> <p><strong>The API is currently limited to read-only access.</strong> From the <a href="https://developers.google.com/+/api/" rel="nofollow noreferrer">API website</a>:</p> <blockquote> <p>Note: The Google+ API currently provides read-only access to public data. All API calls require either an <a href="https://developers.google.com/+/api/oauth.html#about" rel="nofollow noreferrer">OAuth 2.0 token</a> or an <a href="https://developers.google.com/+/api/oauth.html#apikey" rel="nofollow noreferrer">API key</a>.</p> </blockquote> <p>Because it's read-only, you will not be able to update or post any information anywhere through the API -- you can only use it to pull basic information like profile and activity details.</p> <p>Given that access to the API may change over time, I'll try to keep this answer up to date with information about news or changes related to <em>write</em> access.</p> <hr> <h3>News &amp; Updates</h3> <p><strong><code>2015-04-28</code></strong>: <a href="https://developers.google.com/+/domains/" rel="nofollow noreferrer">Google+ Domains API</a> was announced way back in August 2013, but somehow I missed its relevance to Google+. </p> <blockquote> <p>The Google+ Domains API allows Google Apps customers and ISVs to take advantage of enhanced Google+ APIs to build tools and services that can be used in a variety of ways.</p> </blockquote> <p>No, it does <strong>not</strong> provide <em>full</em> write access to a user's Google+ profile, but it does give you minor advantages over the Google+ API v1, at least within a domain. This one's mainly for mobile app developers.</p> <p><strong><code>2015-01-21</code></strong>: I have revisited many of the sources linked in this answer and searched for news regarding API changes, but Google has been quiet.</p> <p><strong><code>2014-03-12</code></strong>: Various discussion threads on Google+ about write access (or lack thereof):</p> <ul> <li><a href="https://plus.google.com/+JeffDwyerakajdwyah/posts/ZyQjd1F9jw3" rel="nofollow noreferrer">Discussion thread</a> by <a href="https://plus.google.com/107363681102841358647" rel="nofollow noreferrer">Jeff Dwyer</a></li> <li><a href="https://plus.google.com/+JulianBond23/posts/4mLaNh31JcW" rel="nofollow noreferrer">In-depth discussion of the topic</a> by <a href="https://plus.google.com/116328570070842584752" rel="nofollow noreferrer">Thor Mitchell</a> (the Google+ team member mentioned in Update 6)</li> </ul> <p><strong><code>2013-12-03</code></strong>: The issue thread from UPDATE 1 has finally been <a href="https://code.google.com/p/google-plus-platform/issues/detail?id=41#c181" rel="nofollow noreferrer">responded to by a Google+ project member</a>. Additional discussion regarding write-access to Streams is taking place intermittently on the <a href="https://plus.google.com/u/0/communities/113527920160449995981" rel="nofollow noreferrer">Developing with Google+</a> community page.</p> <p><strong><code>2013-07-05</code></strong>: A developer named <a href="https://stackoverflow.com/users/1392628/eric-leroy">Eric Leroy</a> has built <a href="https://github.com/yipyo/google-plus-extension-jsapi" rel="nofollow noreferrer">an "unofficial" JavaScript library</a> that provides read/write extension to the Google+ API. </p> <ul> <li>via <a href="http://1off.quora.com/Google%2B-XHR-Hack-w%2B-Add-Post" rel="nofollow noreferrer">Google+ XHR Hack = w+ (Add/Post)</a></li> </ul> <p><strong><code>2013-05-14</code></strong>: A "social media management company" can gain additional API access by attempting to become a Google+ Pages API Partner.</p> <ul> <li><a href="https://developers.google.com/+/api/pages-signup" rel="nofollow noreferrer">Google+ Pages API Partner Application Form</a></li> <li><a href="https://plus.google.com/104946722942277428266/posts/LUi2ZNyRHag" rel="nofollow noreferrer">More third party tools to help manage your Google+ page</a> - An announcement from Eduardo Thuler</li> <li><a href="http://adwords.blogspot.com/2011/11/third-party-tools-to-help-manage-your.html" rel="nofollow noreferrer">Original Google announcement of third party management tools</a></li> </ul> <p>Here's an excerpt from the Partner Application Form:</p> <blockquote> <p>The Google+ pages API allows social media management companies to add Google+ page management features into their tool. Access to this API is available through a whitelist, and access is granted to partners on a company by company basis dependent on fit with this API.</p> </blockquote> <p>Other articles explaining the lack of a write API:</p> <ul> <li><a href="http://mashable.com/2012/08/02/google-to-developers-wont-screw-you/" rel="nofollow noreferrer">http://mashable.com/2012/08/02/google-to-developers-wont-screw-you/</a></li> </ul> <p><strong><code>2013-01-04</code></strong>: Google just announced <a href="https://developers.google.com/+/history/" rel="nofollow noreferrer">Google+ History</a>. You can use it to write "moments" (which are private by default) but can then be made public by sharing them directly to your stream and/or your profile. One of the moment types is <a href="https://developers.google.com/+/history/api/moments#commentactivity" rel="nofollow noreferrer"><code>CommentActivity</code></a>.</p> <p><strong><code>2012-10-08</code></strong>: There's now a <a href="http://code.google.com/p/google-plus-platform/issues/detail?id=110" rel="nofollow noreferrer">duplicate bug post</a> with only a few comments, but you can check there for future updates as well.</p> <p><strong><code>2012-06-25</code></strong>: I came across the <a href="http://code.google.com/p/google-plus-platform/issues/detail?id=41" rel="nofollow noreferrer">issue tracker post</a> for Google+ Write Access. The enhancement request status is "New" and priority is "Medium" as of June 25<sup>th</sup>, 2012. There are some links of interest in the comments.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to post in Google+ wall
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USCᴏʀʏ
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to post in Google+ wall
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi Cory, thanks for the fast response.Is there any alternative way to do this(post in user's Streams)
      singulars
      1. PO
      1. USKarthi Ponnusamy
    2. CO@joe: Not that I know of, at least, not programmatically.
      singulars
      1. PO
      1. USCᴏʀʏ
    3. CO@mihai: I corrected because a "wall" is generally a Facebook term, as are "likes"; Twitter has "tweets"; Google has "Streams" and "plus-ones." Terminology is an important component of software design and development; ambiguity is not a friendly term in our world. As for the difference, well, [there are many](http://webplanetfreaks.weebly.com/1/post/2011/8/facebook-wall-vs-google-plus-stream.html).
      singulars
      1. PO
      1. USCᴏʀʏ
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload