---
title: "Login Config"
method: GET
path: "/auth/login-config"
tags: ["AUTH"]
---

# Login Config

`GET /auth/login-config`

## Request

- Base URL: `https://api.myaltimate.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.myaltimate.com/auth/login-config`
- Auth: HTTP bearer

Public login-page bootstrap config — deliberately unauthenticated.

The frontend must decide which login experience to mount (SSO route tree
vs email/password form) before any session exists, so this cannot sit
behind has_token like /tenant-info. It exposes a single bit:
``ssoLoginEnabled`` True means this login host uses SSO; False means no
server-side opinion, and the frontend falls back to its baked-in
SSO_ENABLED allowlist (legacy behaviour). The flag is therefore additive —
it can turn SSO on for a host, never off if already in frontend allowList.

## Headers

- `x-tenant` string

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-11** `70e0a3e5cb0d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/myaltimate/apis/myaltimate-api/changes/auth/login-config/get.md)

---

[API](https://skmtc.dev/myaltimate/apis/myaltimate-api.md) - [All operations](https://skmtc.dev/myaltimate/apis/myaltimate-api/llms.txt) - [OpenAPI document](https://skmtc.dev/myaltimate/apis/myaltimate-api/revisions/727657ce54e9?raw)