# Log in to the user account

This endpoint is utilized for user authentication, granting access to secured endpoints that mandate authentication. Following successful authentication, a blaize_session is generated for the user, enabling them to access the secure endpoints.

Endpoint: POST /blaize/login
Version: 2025-07-30
Security: CookieBlaizeSession, JwtQuery, JwtHeaderXBlaizeJwt, JwtHeaderXZephrJwt, JwtBearer, JwtCookie

## Header parameters:

  - `cookie` (string)
    The session cookie is employed to ascertain whether a user is already authenticated or has an active session.
    Example: "blaize_session=... (optional)"

## Request fields (application/json):

  - `identifiers` (object, required)
    Example: {"email_address":"abc@company.com"}

  - `identifiers.email_address` (string)
    Example: "abc@company.com"

  - `validators` (object, required)
    Example: {"password":"securepassword@123"}

  - `validators.password` (string)
    Example: "securepassword@123"

  - `validators.use_sso` (boolean)
    When this is present there should be no identifiers in the body. The user is identified through a blaize_session cookie.

## Response 200 fields (application/json):

  - `cookie` (string)
    The authenticated user session.
    Example: "blaize_session=443ed68f-0b44-4f32-8443-553d584cb0dd; Expires=Fri, 16 Nov 2018 12:35:56 GMT; Path=/;"

  - `message` (string)
    Example: "Login successful"

  - `tracking_id` (string)
    The user tracking ID.
    Example: "4fac49a6-e423-4ac1-b0ad-d678979344422"


## Response 400 fields

## Response 401 fields