Google OAuth2 API

Name: Google OAuth2 API
Brand: Google OAuth2 API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationoauth23 EndpointsREST

Install Jentic One Beta

Connect the Google OAuth2 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google OAuth2 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 OAuth2 API.

Fetch the authenticated user's profile claims via the userinfo endpoint

Introspect a Google access or ID token to verify it is still active

Confirm the audience and scopes attached to a Google-issued token

GET STARTED

Start building with Google OAuth2 API

Explore with Jentic

View OpenAPI Document

For Agents

Fetch authenticated Google user profile data and introspect Google-issued OAuth tokens through the OAuth2 userinfo and tokeninfo endpoints.

Use for: Get the authenticated Google user's profile, Check whether a Google access token is still valid, Retrieve the email address attached to a Google sign-in, Verify the audience claim of a Google ID token

Not supported: Does not mint or refresh tokens, manage Google accounts, or grant scopes — use for reading profile claims and introspecting existing tokens only.

The Google OAuth2 API surfaces the lightweight identity endpoints that complement the broader Google OAuth 2.0 token flow — the userinfo endpoint that returns profile claims for an authenticated user, and the tokeninfo endpoint that introspects a Google-issued access or ID token. Use it after a sign-in flow to retrieve a user's basic profile (email, name, picture, locale) or to validate that a token is still active and was issued for the expected client. The spec exposes 3 endpoints.

Use Cases

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

★ Sign in with Google profile retrieval

After completing the Google OAuth 2.0 authorization code or implicit flow, call the userinfo endpoint with the resulting access token to retrieve the authenticated user's email, name, locale, and profile picture. This is the canonical step for application onboarding flows that bootstrap a user record from Google identity. The endpoint accepts the bearer token and returns a small JSON document with verified profile claims.

After exchanging an authorization code for an access token, call GET /oauth2/v2/userinfo with the bearer token and extract the email, name, and verified_email fields.

Token validation before privileged actions

Before executing a sensitive action on behalf of a user, validate that the cached Google access token is still active and was issued to the expected client by calling tokeninfo. This catches revoked tokens and audience mismatches before they hit a downstream Google API and surface as opaque 401s. Useful for backend services that store long-lived tokens and replay them.

POST to /oauth2/v2/tokeninfo with access_token=ya29.xxx and reject the request if the response audience field does not match the expected client_id.

Locale-aware personalisation

Read the user's locale from the userinfo response and use it to pick the correct localisation bundle, currency format, and date format for the UI. This avoids the common pitfall of hard-coding en-US for users whose Google account is set to another locale. The locale field comes through as a BCP-47 tag.

Call GET /oauth2/v2/userinfo, read the locale field, and load the matching i18n bundle for the user's session.

Agent-driven Google identity checks via Jentic

An AI agent that needs to confirm a user's Google identity before taking action can use Jentic to call userinfo or tokeninfo without holding raw tokens. The Jentic vault stores the user's refresh token and mints a scoped access token only for the call. Useful for assistant agents that need to confirm identity before surfacing sensitive content.

Use Jentic to find the get-user-info operation, load its schema, and execute it for the current session to confirm the user's verified email.

Key Endpoints

3 endpoints — the google oauth2 api surfaces the lightweight identity endpoints that complement the broader google oauth 2.

METHOD

PATH

DESCRIPTION

GET

/oauth2/v2/userinfo

Get the authenticated user's profile

POST

/oauth2/v2/tokeninfo

Introspect a Google access or ID token

GET

/userinfo/v2/me

Alias for the authenticated user's profile

GET

/oauth2/v2/userinfo

Get the authenticated user's profile

POST

/oauth2/v2/tokeninfo

Introspect a Google access or ID token

GET

/userinfo/v2/me

Alias for the authenticated user's profile

Why Jentic?

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

Credential isolation

User access tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived tokens — refresh tokens never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like get google user profile or validate google token and Jentic returns the matching OAuth2 API operation with its scope requirements and input schema.

Time to first call

Direct integration: a few hours to wire OAuth 2.0 token exchange and call the endpoints. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using Google OAuth2 API through Jentic.

What authentication does the Google OAuth2 API use?

The userinfo endpoint requires a Google OAuth 2.0 bearer token with the userinfo.profile and/or userinfo.email scope. tokeninfo accepts a token as a query parameter and does not need its own bearer credential. Through Jentic, tokens are minted from a refresh credential held in the Jentic vault.

Can I get the user's email through this API?

Yes — call GET /oauth2/v2/userinfo with a token that includes the email scope and the response will include the email and verified_email fields.

What are the rate limits for the OAuth2 API?

Google does not publish a hard quota for these endpoints; treat them as cheap but not free, cache userinfo responses for the session, and avoid calling tokeninfo on every request — call it only when you need to revalidate a stored token.

How do I introspect a token through Jentic?

Search Jentic for token introspection google, load the schema for POST /oauth2/v2/tokeninfo, and execute it with the token to introspect. Jentic returns the audience, scopes, and expiry so the agent can decide whether to proceed.

Does this API mint new access tokens?

No — token minting and refresh happen at https://oauth2.googleapis.com/token, which is part of the broader Google OAuth 2.0 flow and not in this spec. This API only reads profile claims and introspects existing tokens.

What's the difference between userinfo and tokeninfo?

userinfo returns claims about the user (email, name, picture) and requires a bearer token in the Authorization header. tokeninfo returns claims about the token itself (audience, scope, expiry) and takes the token as a parameter.