> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hi-doctor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in with Google

> Sign in or sign up with a Google credential.

An account created this way has **no password**: it cannot use `/v1/users/token/`, and it cannot complete MCP connector sign-in, which is password-based. Set a password through the reset flow first.



## OpenAPI

````yaml /api-reference/openapi.json post /v1/users/google-login/
openapi: 3.0.3
info:
  title: Hi-Doctor API
  version: 1.0.0
  description: >-
    Patient-facing REST API for Hi-Doctor.


    Authenticate with email and password to receive a JWT pair, then send the
    access token as `Authorization: Bearer <token>` on every subsequent request.


    Only patient-accessible endpoints are documented here. Clinician and
    back-office endpoints are intentionally omitted.
  contact:
    name: Hi-Doctor
    email: hello@hi-doctor.ai
    url: https://hi-doctor.ai
servers:
  - url: https://api.hi-doctor.ai
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Account
    description: Registration, email verification, sign-in and profile.
  - name: Questionnaires
    description: Complete a consultation questionnaire and submit it for medical review.
  - name: Consultations
    description: Consultations a doctor has reviewed or is reviewing.
  - name: Prescriptions
    description: Prescriptions and reissue requests.
  - name: Billing
    description: Checkout, subscription management and the Stripe billing portal.
  - name: Records
    description: Orders, invoices and side-effect reports.
  - name: Messages
    description: The patient's private thread with their medical team.
  - name: Progress
    description: Weight, injection and note tracking. Requires an active treatment plan.
  - name: Referrals
    description: Referral summary and transactions.
paths:
  /v1/users/google-login/:
    post:
      tags:
        - Account
      summary: Sign in with Google
      description: >-
        Sign in or sign up with a Google credential.


        An account created this way has **no password**: it cannot use
        `/v1/users/token/`, and it cannot complete MCP connector sign-in, which
        is password-based. Set a password through the reset flow first.
      operationId: users_google_login_create
      parameters:
        - in: header
          name: X-Brand-Slug
          required: true
          schema:
            type: string
            enum:
              - hi-doctor
            default: hi-doctor
          description: >-
            Identifies the Hi-Doctor brand. Required; the request is rejected
            without it.
      responses:
        '200':
          description: No response body
        '400':
          description: No Google credential in the body.
          content:
            application/json:
              example:
                error: Google token is required
      security: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Access token from POST /v1/users/token/

````