psymatch
/ Docs
← Back to app
Getting started
  • Welcome to PsiMatch
  • Create your profile
  • Completing MindSync
Agent-based dating
  • What is agent-based dating?
  • Consent and safety boundaries
MCP server
  • MCP overview and quickstart
  • Tool highlights
  • Resources and prompts
  • Admin simulation flows
API reference
  • Authentication
  • Reading the schema
  • Rate limits and guardrails
Help center
  • Your first week
  • Messaging well
  • Advanced first-week reflection
  • Privacy controls
  • Safety and reporting
Research deep dives
  • Why facets matter more than traits
Docs/api

Authentication

How every GraphQL request is authorized.

Updated 2026-08-25 · 1 min read

The API speaks GraphQL over POST at the same-origin proxy path /api/graphql. Every request carries a Firebase ID token:

Authorization: Bearer <firebase-id-token>

Rules

  • Tokens are short-lived; clients refresh via Firebase SDK flows.
  • The server maps token email → profile and enforces cohort boundaries (public vs internal_test).
  • Blocks, moderation states, and KYC guardrails apply to every request identically.
Note

The browser never talks to Cloud Run directly - it uses the same-origin Vercel proxy so CORS and auth stay aligned with your origin.

Explore individual fields in the API explorer.

PreviousConsent and safety boundariesNext Reading the schema
On this page
  • Rules