> ## 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. # Create > Creation of a new integration key requires specifying the domain (URL / Site) that will manage the key. Access is granted only through the specific domain, along with the Label / Name of the key for easy recognition and identification by users. ## OpenAPI ````yaml POST /integrations 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: /integrations: post: tags: - Integrations summary: Create description: >- Creation of a new integration key requires specifying the domain (URL / Site) that will manage the key. Access is granted only through the specific domain, along with the Label / Name of the key for easy recognition and identification by users. operationId: create 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: domain: description: Domain of the partner website type: string example: https://dashboard.legitimuz.com.br label: description: Name of the integration type: string example: Legitimuz App responses: '200': description: Integrations Create Response headers: Connection: schema: type: string example: keep-alive Date: schema: type: string example: Fri, 15 Sep 2023 21:37:44 GMT Keep-Alive: schema: type: string example: timeout=5 access-control-allow-credentials: schema: type: string example: 'true' access-control-allow-origin: schema: type: string example: api.legitimuz.com content-length: schema: type: string example: '303' content: application/json: schema: type: object properties: integration: type: object properties: created_at: type: string example: '2023-09-15T18:37:43.961-03:00' domain: type: string example: dashboard.legitimuz.com.br id: type: number example: 20 id_user: type: number example: 14 label: type: string example: Legitimuz App tenant_id: type: number example: 13 updated_at: type: string example: '2023-09-15T18:37:43.961-03:00' uuid: type: string example: 4cb2dcd2-5317-4fc8-8f2f-623ed54e929c message: type: string example: Successfully Processed! type: type: string example: insert examples: Integrations Create Response: value: integration: created_at: '2023-09-15T18:37:43.961-03:00' domain: dashboard.legitimuz.com.br id: 20 id_user: 14 label: Legitimuz App tenant_id: 13 updated_at: '2023-09-15T18:37:43.961-03:00' uuid: 4cb2dcd2-5317-4fc8-8f2f-623ed54e929c message: Successfully Processed! type: insert ````