---
title: "Sign in with ID token (Google One Tap, native SDKs)"
method: POST
path: "/api/auth/id-token"
tags: ["Client"]
---

# Sign in with ID token (Google One Tap, native SDKs)

`POST /api/auth/id-token`

Authenticate a user using an ID token obtained from a native SDK (e.g., Google One Tap).
Currently only the `google` provider is supported.

## Query parameters

- `client_type` 'web' | 'mobile' | 'desktop' | 'server'

## Request body

- object
  - `provider` 'google', required — Identity provider that issued the token
  - `token` string, required — Raw ID token from the provider SDK

## Response `200`

Sign-in successful

- object
  - `user` UserResponse
    - `id` string, uuid
    - `email` string, email
    - `profile` object, nullable — User profile data (name, avatar_url, and custom fields)
      - `name` string
      - `avatar_url` string, uri
    - `metadata` object, nullable — System metadata (device ID, login IP, etc.)
    - `emailVerified` boolean
    - `providers` string[]
    - `createdAt` string, date-time
    - `updatedAt` string, date-time
  - `accessToken` string
  - `csrfToken` string, nullable — CSRF token for use with refresh endpoint (web clients only)
  - `refreshToken` string, nullable — Refresh token for mobile/desktop/server clients (null for web clients)

## Other responses

- `400` — Invalid request - unsupported provider or missing token
- `401` — Invalid or expired ID token

---

[API](https://skmtc.net/insforge/apis/insforge-authentication-api.md) · [All operations](https://skmtc.net/insforge/apis/insforge-authentication-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/insforge/insforge-authentication-api/versions/a935bb49f932/schema)