Mantic Auth API

The auth API from Mantic — 5 operation(s) for auth.

Operations 5

POST /webapp/session Create Session #
POST /webapp/logout Logout #
DELETE /webapp/demo-session Stop Demo Session #
POST /webapp/demo-session/redeem Redeem Demo Session #
GET /webapp/me Get User Profile #

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/mantic:mantic-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.

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

OpenAPI Specification

mantic-auth-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Fast Auth API
  version: 0.1.0
tags:
- name: Auth
paths:
  /webapp/session:
    post:
      tags:
      - Auth
      summary: Create Session
      description: Create a new session cookie from a Firebase ID token.
      operationId: create_session_webapp_session_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Create Session Webapp Session Post
  /webapp/logout:
    post:
      tags:
      - Auth
      summary: Logout
      description: 'Logout the current user.


        A dead session still clears its cookie, with nothing to revoke; an

        authentication-service failure fails the request.'
      operationId: logout_webapp_logout_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Logout Webapp Logout Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
      - OAuth2AuthorizationCodeBearer: []
  /webapp/demo-session:
    delete:
      tags:
      - Auth
      summary: Stop Demo Session
      description: End the authenticated admin's delegated service-account session.
      operationId: stop_demo_session_webapp_demo_session_delete
      responses:
        '204':
          description: Successful Response
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
      - OAuth2AuthorizationCodeBearer: []
  /webapp/demo-session/redeem:
    post:
      tags:
      - Auth
      summary: Redeem Demo Session
      description: Exchange a one-time admin handoff for a public-app demo cookie.
      operationId: redeem_demo_session_webapp_demo_session_redeem_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RedeemServiceAccountDemoSessionRequest'
        required: true
      responses:
        '204':
          description: Successful Response
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
      - OAuth2AuthorizationCodeBearer: []
  /webapp/me:
    get:
      tags:
      - Auth
      summary: Get User Profile
      description: Get the current user's profile.
      operationId: get_user_profile_webapp_me_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
      - OAuth2AuthorizationCodeBearer: []
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    Goal:
      properties:
        label:
          type: string
          maxLength: 200
          minLength: 1
          title: Label
        description:
          anyOf:
          - type: string
            maxLength: 2000
          - type: 'null'
          title: Description
      additionalProperties: false
      type: object
      required:
      - label
      title: Goal
      description: 'Retained-only profile goal — superseded by `interests`.


        No longer settable via the API and read by no feature. Kept solely so

        pre-interests rows (prod users we asked to set goals) still deserialise and

        survive profile edits until the manual goals->interests backfill + the

        follow-up PR that drops it. See `UserPreferences.goals`.'
    UserRole:
      type: string
      enum:
      - user
      - admin
      - enterprise
      title: UserRole
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    UserOrganisationResponse:
      properties:
        id:
          type: integer
          title: Id
        name:
          type: string
          title: Name
        is_metered:
          type: boolean
          title: Is Metered
          default: false
      type: object
      required:
      - id
      - name
      title: UserOrganisationResponse
    RedeemServiceAccountDemoSessionRequest:
      properties:
        handoff_token:
          type: string
          title: Handoff Token
      type: object
      required:
      - handoff_token
      title: RedeemServiceAccountDemoSessionRequest
    UserPreferences:
      properties:
        function:
          anyOf:
          - type: string
            maxLength: 100
          - type: 'null'
          title: Function
        interests:
          anyOf:
          - items:
              $ref: '#/components/schemas/Interest'
            type: array
            maxItems: 50
          - type: 'null'
          title: Interests
        goals:
          anyOf:
          - items:
              $ref: '#/components/schemas/Goal'
            type: array
            maxItems: 20
          - type: 'null'
          title: Goals
      additionalProperties: false
      type: object
      title: UserPreferences
      description: 'Stored/returned user preferences. Interests always carry a category.


        `goals` is retained-only data (see `Goal`): never written from user

        input (replaced by `interests`) and read by no feature. It is carried through

        the profile write path so existing goals survive until the manual

        goals->interests backfill; a follow-up PR drops it once all users migrate.'
    UserResponse:
      properties:
        id:
          type: string
          title: Id
        email:
          type: string
          title: Email
        name:
          anyOf:
          - type: string
          - type: 'null'
          title: Name
        created_at:
          type: string
          format: date-time
          title: Created At
        last_login:
          type: string
          format: date-time
          title: Last Login
        last_active:
          type: string
          format: date-time
          title: Last Active
        role:
          $ref: '#/components/schemas/UserRole'
        has_admin_account:
          type: boolean
          title: Has Admin Account
          default: false
        organisations:
          items:
            $ref: '#/components/schemas/UserOrganisationResponse'
          type: array
          title: Organisations
          default: []
        preferences:
          anyOf:
          - $ref: '#/components/schemas/UserPreferences'
          - type: 'null'
        onboarding_completed_at:
          anyOf:
          - type: string
            format: date-time
          - type: 'null'
          title: Onboarding Completed At
        is_organisation_admin:
          type: boolean
          title: Is Organisation Admin
          default: false
        is_demo_session:
          type: boolean
          title: Is Demo Session
          default: false
        demo_session_expires_at:
          anyOf:
          - type: string
            format: date-time
          - type: 'null'
          title: Demo Session Expires At
      type: object
      required:
      - id
      - email
      - created_at
      - last_login
      - last_active
      - role
      title: UserResponse
    Interest:
      properties:
        label:
          type: string
          maxLength: 200
          minLength: 1
          title: Label
        category:
          type: string
          enum:
          - region
          - topic
          - sector
          - market
          - org
          - person
          - event
          - goal
          - other
          title: Category
      additionalProperties: false
      type: object
      required:
      - label
      - category
      title: Interest
      description: 'A stored/returned user interest. `category` is REQUIRED here.


        `category` is a `Literal` slug, not a strict `StrEnum`: a strict `StrEnum`

        field does not survive the `TypedJSONB` write->read round-trip (the stored

        string is rejected on load), whereas a `Literal` validates from a plain

        string even under `strict=True`. Guarded by a JSONB round-trip test.'
  securitySchemes:
    OAuth2AuthorizationCodeBearer:
      type: oauth2
      flows:
        authorizationCode:
          scopes: {}
          authorizationUrl: https://app.mantic.com/auth/oauth2/authorize
          tokenUrl: https://app.mantic.com/auth/oauth2/token