Google+ API

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

✓ Official Vendor SpecSocial MediaSocial Managementoauth29 EndpointsREST

For Agents

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

Quickstart

Get started with Google+ API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get a Google+ person by ID"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google+ API 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

Fetch a single Google+ comment by commentId

GET STARTED

Start building with Google+ API API

Explore with Jentic

View OpenAPI Spec

The Google+ API is the legacy read interface to the Google+ social platform, exposing public activities, comments, and people resources via 9 GET endpoints. Callers can list a person's activities by collection, fetch a single activity or comment, list commenters or resharers on an activity, and search people by query. Google+ as a consumer product was shut down in 2019, so this spec is preserved primarily for historical archival reads, migration tooling, and reference where legacy Google+ identifiers still appear in customer datasets.

Use Cases

Patterns agents use Google+ API 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 though Jentic?

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

Credential isolation

OAuth refresh tokens for the legacy Google+ API are stored encrypted in the Jentic vault. Agents receive a scoped access token at call time so the long-lived credential never enters agent context.

Intent-based discovery

Agents search Jentic with intents like 'get a Google+ activity' and receive the matching read-only operation with its full input schema, eliminating manual docs hunts on a retired API.

Time to first call

Direct integration: 1-2 days for OAuth scope provisioning and brittle legacy error handling. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Google People API

Modern replacement for Google+ profile and contact reads

Choose People for any current Google profile or contact lookup; reach for Plus only when working with archived Google+ identifiers.

Complementary

Google Blogger API

Read and write Blogger posts and comments alongside legacy Google+ data

Choose Blogger when migrating Google+ content to a Blogger-hosted archive.

Complementary

YouTube Data API

Manage YouTube content for users whose Google+ identifiers are legacy

Choose YouTube Data when the user-facing surface has migrated from Google+ to YouTube channels.

FAQs

Specific to using Google+ API 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 the Jentic vault 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.