Google+ API

Name: Google+ API
Brand: Google+ API
Availability: InStock

✓ Official Vendor SpecSocial MediaSocial Managementoauth29 EndpointsREST

Install Jentic One Beta

Connect the Google+ API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google+ API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Google+ API.

Search public Google+ activities and people by free-text query

Retrieve a single Google+ activity by activityId

List comments on a Google+ activity

List people who plus-oned or reshared a Google+ activity

GET STARTED

Start building with Google+ API

Explore with Jentic

View OpenAPI Document

For Agents

Read legacy Google+ activities, comments, and people records by ID for archival and migration use cases.

Use for: Search Google+ for a person by name, Get a Google+ activity by its ID, List comments on a Google+ post, Retrieve a Google+ user's public activities

Not supported: Does not post, comment, or modify Google+ data - read-only endpoints only, intended for archival and identifier migration on a retired consumer product.

Use Cases

Patterns agents use Google+ API for, with concrete tasks.

★ Archival Backup of Public Posts

A research team backs up a known public Google+ profile's activities and comments before historical references rot further. Listing /people/{userId}/activities/{collection}=public returns the user's public posts page by page, and each activity ID can be expanded with /activities/{activityId} and its comments. The backup persists into a local archive that can outlive the upstream availability of the data.

Loop GET /people/{userId}/activities/public with pageToken until done, then GET /activities/{activityId}/comments for each activity and persist results to local storage.

Identifier Migration Mapping

An identity team migrating off legacy Google+ user IDs needs to confirm which IDs still resolve and capture the displayName and image fields before retiring them. GET /people/{userId} returns the public Person record for any still-resolvable ID, while GET /people?query=... can search by name. The mapping populates an internal lookup so old systems referencing Google+ IDs can be updated.

Read a CSV of legacy Google+ userIds and call GET /people/{userId} for each, recording the displayName, url, and image.url fields into the new identity table.

Social Sentiment Backfill

A historical analytics project backfills sentiment scores on legacy Google+ comments to compare against newer social platforms. GET /activities/{activityId}/comments returns the comment thread, and each comment's plaintext content is fed to a sentiment model. Because Google+ is read-only legacy data, the backfill runs once and is then frozen.

GET /activities/{activityId}/comments with pageSize=20, score each comment's content, and persist {activityId, commentId, sentiment} rows into the analytics warehouse.

AI Agent Legacy Lookup via Jentic

Migration agents that encounter legacy Google+ identifiers in customer datasets can resolve them through Jentic without managing OAuth scopes by hand. Jentic exposes the people.get and activities.get operations as search-load-execute calls so the agent can resolve a stale ID, capture its display fields, and continue the migration in a single step.

Search Jentic for 'get a Google+ person by ID', load the people.get schema, and execute it for each legacy userId in the migration queue.

Key Endpoints

9 endpoints — the google+ api is the legacy read interface to the google+ social platform, exposing public activities, comments, and people resources via 9 get endpoints.

METHOD

PATH

DESCRIPTION

GET

/activities/{activityId}

Get a single Google+ activity

GET

/activities/{activityId}/comments

List comments on an activity

GET

/activities/{activityId}/people/{collection}

List people who plus-oned or reshared an activity

GET

/comments/{commentId}

Get a single comment

GET

/people

Search Google+ people by query

GET

/people/{userId}

Get a single person's public profile

GET

/people/{userId}/activities/{collection}

List a person's public activities

GET

/activities/{activityId}

Get a single Google+ activity

GET

/activities/{activityId}/comments

List comments on an activity

GET

/activities/{activityId}/people/{collection}

List people who plus-oned or reshared an activity

GET

/comments/{commentId}

Get a single comment

GET

/people

Search Google+ people by query

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Google OAuth credential for the Google+ API is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a Google+ activity' or 'read a Google+ person', and Jentic returns the matching read-only operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Google+ API through Jentic.

What authentication does the Google+ API use?

It uses OAuth 2.0 with the plus.login or plus.me scope (legacy). Through Jentic any required OAuth credential is held in your Jentic One instance and a scoped access token is injected at call time so the agent never sees the raw credential.

Can I post to Google+ with this API?

No. All 9 endpoints in the spec are GET-only - activities.list, activities.get, activities.search, comments.list, comments.get, people.search, people.get, people.list, and the activity-people listing. The consumer Google+ product is shut down so write paths are not provided.

What are the rate limits for this API?

The Google+ API followed standard Google Cloud project quotas measured in queries per day and per second. Because the consumer product is retired, sustained high-volume use is unrealistic - design migration jobs to run once and persist results locally rather than re-querying.

How do I look up a legacy Google+ user through Jentic?

Run jentic search 'get a Google+ person by ID', load the schema for GET /people/{userId}, and execute it with the legacy user identifier. Jentic returns the displayName, url, and image fields useful for migration mapping.

Is the Google+ API free?

There is no per-call charge for the Google+ API. Standard Google Cloud project quotas apply, and the API is offered on a best-effort archival basis given the consumer product was retired in 2019.

Can I read comments on a specific Google+ post?

Yes. GET /activities/{activityId}/comments returns the comment thread on an activity, and individual comments can be fetched with GET /comments/{commentId}. Both endpoints are read-only and return the comment's content, author, and timestamps.

Can I limit what my agent is allowed to do with the Google+ API?

Yes. Because you run Jentic One yourself, your own rules decide which Google+ operations and OAuth credential the agent may use. Every endpoint here is read-only, and since the activity, comment, and person identifiers sit in the URL path such as /activities/{activityId} and /people/{userId}, you can pin the agent to just the reads it needs, like fetching an activity or resolving a legacy person record. There is no way to post or modify Google+ data through this API, so the allowed set stays confined to archival and identifier-migration reads.