> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praxis-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Validate the caller's stored Google Services token
> Checks whether the caller's stored Google access token is still accepted by Google
by making a probing call to the userinfo endpoint. Resolves which storage location
to read from in the same priority order as the runtime authenticator: institution
token first (when the JWT has an institution), personal token second.
If Google rejects the token (revoked externally, expired refresh chain, etc.),
the handler clears it from the database and returns `valid: false, cleared: true`.
This is a side-effecting probe — calling it can wipe a stale token.
## OpenAPI
````yaml /mdx/api-reference/admin/admin-api.json get /api/auth/google/services/validate
openapi: 3.0.0
info:
title: Pria Admin API
version: 2.0.1
description: >-
Pria API Documentation Praxis's developer platform is a core part of our
mission to empower organizations to grow better. Our APIs are designed to
enable teams of any shape or size to build robust integrations that help
them customize and get the most value out of Pria. All Pria APIs are built
using REST conventions and designed to have a predictable URL structure.
They use many standard HTTP features, including methods (POST,
GET, PUT, DELETE) and error response codes.
All API calls are
made under https://hiimpria.ai/api and all responses return standard JSON.
In these docs, you'll find lists of all available endpoints for a given API,
along with interactive code blocks for building requests. For walkthroughs
of basic usage for these APIs, check out the API guides.
servers:
- url: https://pria.praxislxp.com
description: Pria API Server
security: []
tags:
- name: Authentication
description: User authentication, registration, and password management (/api/auth)
- name: OAuth
description: OAuth authentication providers - Google, GitHub, SSO (/api/auth/oauth)
- name: User
description: User profile management and account operations (/api/user)
- name: User Institutions
description: User institution memberships and switching (/api/user/institution)
- name: User Tools
description: Available tools for authenticated users (/api/user/tools)
- name: Institutions
description: Institution settings and configuration (/api/user/institution)
- name: Conversation
description: AI conversation and Q&A endpoints (/api/ai)
- name: Realtime
description: Real-time voice AI and WebRTC sessions (/api/ai/rt)
- name: Assistant
description: AI assistant configuration and management (/api/user/assistant)
- name: History
description: Conversation history and favorites (/api/user/history)
- name: RAG
description: >-
Document upload, embedding, and retrieval-augmented generation
(/api/user/files, /api/user/rag)
- name: Setting
description: Instance variables and settings management (/api/user/setting)
- name: Branding
description: Digital twin branding and customization (/api/agent/branding)
- name: Agent
description: Agent engagement and session management (/api/agent)
- name: SDK Launch
description: >-
SDK launch token signing and verification for secure iframe embedding
(/api/auth/sdk-sign, /api/auth/sdk-verify)
- name: Testing
description: Health checks, diagnostics, and test endpoints (/api/test)
- name: Admin Accounts
description: Account management for super admins (/api/admin/account)
- name: Admin Institutions
description: Institution management for admins (/api/admin/institution)
- name: Admin Users
description: User management for admins (/api/admin/user)
- name: Admin Entitlements
description: >-
User-institution relationships and permissions
(/api/admin/userInstitution)
- name: Admin Sessions
description: Session management for admins (/api/admin/session)
- name: Admin Histories
description: Conversation history management and analytics (/api/admin/history)
- name: Admin Assistants
description: AI assistant management for admins (/api/admin/assistant)
- name: Admin Questions
description: Institution question and prompt management (/api/admin/question)
- name: Admin Tools
description: Tool configuration management (/api/admin/tool)
- name: Admin AI Models
description: AI model configuration (/api/admin/aimodel)
- name: Admin MCP Servers
description: Model Context Protocol server management (/api/admin/mcpserver)
- name: Admin Feedbacks
description: User feedback management (/api/admin/feedback)
- name: Admin Uploads
description: Upload management (/api/admin/upload)
- name: Admin Charts
description: Analytics and visualization chart management (/api/admin/chart)
- name: Admin Memory
description: Admin inspection and editing of user/instance memory parameters.
- name: Admin Usage Limits
description: Per-user usage-vs-cap reporting and account-wide at-limit counts.
paths:
/api/auth/google/services/validate:
get:
tags:
- OAuth
summary: Validate the caller's stored Google Services token
description: >
Checks whether the caller's stored Google access token is still accepted
by Google
by making a probing call to the userinfo endpoint. Resolves which
storage location
to read from in the same priority order as the runtime authenticator:
institution
token first (when the JWT has an institution), personal token second.
If Google rejects the token (revoked externally, expired refresh chain,
etc.),
the handler clears it from the database and returns `valid: false,
cleared: true`.
This is a side-effecting probe — calling it can wipe a stale token.
responses:
'200':
description: Validation completed. Inspect `valid` for the outcome.
content:
application/json:
schema:
$ref: '#/components/schemas/GoogleOAuthValidateResponse'
'401':
description: Missing or invalid JWT (verifyToken).
'404':
description: The caller's User record could not be loaded.
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
message:
type: string
example: User not found
'500':
description: Unexpected error during validation.
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
message:
type: string
example: Validation request failed
security:
- bearerAuth: []
components:
schemas:
GoogleOAuthValidateResponse:
type: object
properties:
valid:
type: boolean
description: >-
Whether the stored Google access_token is currently accepted by
Google.
example: true
source:
type: string
nullable: true
enum:
- institution
- user
description: >
Which storage location the validated token came from. `institution`
means it
lived on the user's `UserInstitution.googleLoginToken`; `user` means
the
personal token on the User record. Null when no token is configured.
cleared:
type: boolean
description: >-
Set to true when an invalid token was just cleared from the
database.
example: false
message:
type: string
description: Set when no token is configured for the resolved source.
error:
type: string
description: Set on validation failure — passes through Google's error message.
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: JWT token passed in authorization header
````