canonical: https://jentic.com/apis/googleapis.com/plus # Google+ API 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. ## For AI agents Read legacy Google+ activities, comments, and people records by ID for archival and migration use cases. ## Scope Does not post, comment, or modify Google+ data - read-only endpoints only, intended for archival and identifier migration on a retired consumer product. ## Capabilities - 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 - List a person's public activities by collection - List a person's followers or people in a named collection ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **activities** — Read public Google+ activities by ID or by person and collection - **comments** — Read comments on a Google+ activity or fetch a single comment by ID - **people** — Search and retrieve public Google+ profile records and follower collections ## Why Jentic - **Setup:** Wiring the Google+ API by hand means configuring OAuth 2.0 for a retired consumer product, minting a scoped access token, and routing the read-only activity and people requests to the plus/v1 paths on www.googleapis.com yourself. Through Jentic you install once, import the Google+ API from the API Directory, store the OAuth credential once, and your agent calls it. - **Permission scoping:** The Google+ API puts the activity, comment, and person in the URL path (/activities/{activityId}, /people/{userId}), so a rule can pin your agent to the reads it needs on those resources. Every endpoint here is read-only, so the allowed set can archive and migrate identifiers without any way to post or modify. - **Credential handling:** 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. - **Discovery method:** 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. ## Related APIs - **Google People API** — Modern replacement for Google+ profile and contact reads - **Google Blogger API** — Read and write Blogger posts and comments alongside legacy Google+ data - **YouTube Data API** — Manage YouTube content for users whose Google+ identifiers are legacy ## FAQ ### 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.