Lily AI

Lily AI Auth API

The Auth API from Lily AI — 5 operation(s) for auth.

Documentation GitHub OpenAPI

Operations 5

GET /auth/b2c/login #

GET /auth/microsoft/login #

GET /v2/auth/b2c/login #

GET /v2/auth/microsoft/login #

POST /v2/auth/qa-automated/login #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/lily-ai-auth-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: LilyApp API - Nest Based Application Auth API
  description: Lily App Middleware
  version: '1.0'
  contact: {}
servers:
- url: https://lilyapp-api-prd.pub.lilyai.net
  description: Production (LilyApp-Api-Prod-AWS)
- url: https://lilyapp-api-stg.pub.lilyai.net
  description: Staging
tags:
- name: Auth
paths:
  /auth/b2c/login:
    get:
      operationId: AuthController_loginUserExt
      parameters: []
      responses:
        '200':
          description: Login a user using Azure Active Directory with B2C.
          content:
            application/json:
              schema:
                type: string
      tags:
      - Auth
  /auth/microsoft/login:
    get:
      operationId: AuthController_loginUser
      parameters: []
      responses:
        '200':
          description: Login a user using Microsoft Azure.
          content:
            application/json:
              schema:
                type: string
      tags:
      - Auth
  /v2/auth/b2c/login:
    get:
      operationId: AuthV2Controller_loginUserExt
      parameters: []
      responses:
        '200':
          description: Login a user using Azure Active Directory with B2C.
          content:
            application/json:
              schema:
                type: string
      tags:
      - Auth
  /v2/auth/microsoft/login:
    get:
      operationId: AuthV2Controller_loginUser
      parameters: []
      responses:
        '200':
          description: Login a user using Microsoft Azure.
          content:
            application/json:
              schema:
                type: string
      tags:
      - Auth
  /v2/auth/qa-automated/login:
    post:
      operationId: AuthV2Controller_loginQaSupport
      parameters:
      - name: x-qa-auth
        required: true
        in: header
        schema:
          type: string
      - name: origin
        required: true
        in: header
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/QaSupportLoginDto'
      responses:
        '200':
          description: Login for QA Automated with JWT token validation.
          content:
            application/json:
              schema:
                type: string
        '401':
          description: Invalid token or token validation failed.
        '403':
          description: Origin is not authorized to access this feature.
      tags:
      - Auth
components:
  schemas:
    QaSupportLoginDto:
      type: object
      properties:
        username:
          type: string
          example: xyz@abc.com
          description: QA Support username/email
        password:
          type: string
          example: xyz
          description: QA Support password
      required:
      - username
      - password
  securitySchemes:
    JWT:
      scheme: bearer
      bearerFormat: JWT
      type: http
      in: header