> ## Documentation Index
> Fetch the complete documentation index at: https://legitimuz.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Login

> Endpoint responsible for performing API authentication.
Required data: **Username and Password**.
After authentication, a Token (Bearer Token) will be generated, which must be informed in other Endpoints to continue with the Validation Proposal Creation process.



## OpenAPI

````yaml POST /auth/login
openapi: 3.0.3
info:
  title: Legitimuz Parceiros (API Partners)
  description: >-
    The Legitimuz Partners API is developed in the REST style (opens new
    window). To connect to our API, we provide authentication through three main
    parameters: Username and Password. These will be provided via registration,
    which can be done through the SignUp endpoint.

    The API is accessed through standard RESTful HTTP requests. For more
    information, we are available to assist you.
  version: 1.0.0
  contact: {}
servers:
  - url: https://api.legitimuz.com
security: []
tags:
  - name: Auth
    description: >-
      Here we will discuss the authentication and registration of new Users; we
      have 3 main endpoints: Login, SignUp, and Me.


      **In Login,** you can authenticate by providing Username/Password and
      obtain the Bearer Token for authentication.


      **In SignUp,** you can register your account: company data, name, tax
      identification number (CNPJ), and the first user: name, personal
      identification number (CPF), username, date of birth.


      **In "Me",** you will have all the data related to your created account,
      and important IDs to use in subsequent requests.
  - name: Integrations
    description: >-
      Module that manages the API integration keys, where consultation of all
      created and active keys is available.

      **In List**, all queries of active keys are available.

      **In Create**, the creation of new integration keys that will be used in
      the following Endpoints is available.

      **Attention: Manage your API keys carefully, as they provide access to all
      Legitimuz product queries, and should be stored carefully to be used only
      in your product.**
  - name: SMS
    description: >-
      Here we will discuss the authentication and registration of new Users; we
      have 3 main endpoints: Login, SignUp, and Me.
  - name: AML
    description: >-
      Here we will discuss the authentication and registration of new Users; we
      have 3 main endpoints: Login, SignUp, and Me.
  - name: KYC
    description: >-
      In this module, the process of validation and knowledge of your clients
      (KYC, Know Your Client) is carried out.

      There are 4 main endpoints provided for client consultations and
      validations:


      - **OCR Document**
          The validation of the document sent along with the client's CPF (Personal Tax ID in Brazil) is conducted, where various databases and credit bureaus are consulted to verify if the client's provided data actually matches the document. If any inconsistency is found, a "**Manual Review**" alert is returned. If more than one inconsistency is detected, a "_Failed Analysis_" alert is displayed.

      - **Facematch**
          The validation of the client's face or facial features is conducted in comparison with the photo on the submitted document. It is necessary to submit a document with a clear, high-resolution photo so that the comparison can be accurately performed. After the validation, a percentage match between the two images is generated, where only a similarity of 80% or higher between the two faces is considered valid.

      - **CPF Enrichment**
          Endpoint designed for Enrichment / Consultation of client information through the CPF, returning various data such as Full Name, Mother's Name, Address, Phone Number, Email, Age, Date of Birth, etc.

      - **CEP (zip code) Enrichment**
          Returns address data from a call made using the zip code (CEP), returning the Street, State, City, and Neighborhood.
  - name: Receita Federal
paths:
  /auth/login:
    post:
      tags:
        - Receita Federal
      summary: Login
      description: >-
        Endpoint responsible for performing API authentication.

        Required data: **Username and Password**.

        After authentication, a Token (Bearer Token) will be generated, which
        must be informed in other Endpoints to continue with the Validation
        Proposal Creation process.
      operationId: login1
      parameters:
        - name: Origin
          in: header
          schema:
            type: string
            example: api.legitimuz.com
          description: Client's domain (created during the integration key stage)
      requestBody:
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                expiration:
                  description: Token expiration time in hours
                  type: string
                  example: '876600'
                password:
                  description: Legitimuz password.
                  type: string
                  example: ''
                username:
                  description: Legitimuz user, created in the panel / dashboard.
                  type: string
                  example: ''
      responses:
        '200':
          description: ''

````