> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-api/connect/available-resources/synchronous-services/doc-less-sync.md). # Doc Less Sync {% hint style="info" %} **Authentication Requirements:** * Regular endpoints use `OAuth2` authentication with base URL: `https://api.us.prd.caf.io` * For enhanced security, some endpoints may also support `mTLS` authentication with base URL: `https://mtls.us.prd.caf.io` * For information on implementing `mTLS`, access [Using mTLS](/caf-api/connect/authentication/using-mtls.md) {% endhint %} ## Product guide This section provides documentation for the **Doc Less** service. **Doc Less** is a solution designed to **optimize the user onboarding process** by reusing documents already stored in our database. By doing so, it eliminates the need to request the same documents again, making the onboarding process **faster**, **more efficient**, and **increasing conversion rates**. ### Benefits * **Higher conversion rates**: Speeds up onboarding by reusing existing documents. * **Improved operational efficiency**: Eliminates repetitive steps and reduces user effort. * **Client flexibility**: Allows clients to define the level of document validation based on their risk appetite. ### How it works Doc Less queries a centralized database of previously stored documents. During the onboarding process, the service checks whether the user's documents already exist in the database, **avoiding the need for new document capture**. ### Usage options Doc Less is available in two modes: * **Web onboarding**: Integrated into Certta's standard onboarding flow. * **API flow**: Ideal for clients using direct integration through Certta's Document Capture SDK. ### Activation process 1. **Contract validation**: Make sure your contract includes permission to use Doc Less. 2. **Activation by Certta**: Our technical team will enable the functionality for your account. ### Requirements * For the API flow, it is mandatory to provide the user's CPF (Brazilian ID number) along with confirmation of acceptance of the terms of use and privacy policy in order to retrieve the document reference. {% hint style="info" %} **Document reference** The document reference is an **encrypted hash** that serves as a unique identifier for locating the corresponding document in the database. The document will only be made available after a **valid transaction** is created in Certta's system. These mechanisms ensure both efficient data reuse and compliance with current privacy regulations. {% endhint %} ## API flow guide This guide outlines the three main steps to integrate the **Doc Less** service via API. ### 1. Inserting Certta's Terms of Use and Privacy Policy To use Certta's Doc Less product, it is mandatory to include Certta's Terms of Use and Privacy Policy in the user's onboarding flow. The user's acceptance of Certta's Terms and Privacy Policy must be properly recorded, including logs such as IP address, date, time, and the URLs of the documents accepted. These records and evidences must be shared with Certta. This measure ensures legal compliance and regulatory security in the use of the service. {% hint style="info" %} **Recommended example** *"By continuing, you acknowledge and agree that your personal data will be processed by Certta in accordance with the* [*Terms of Use*](https://www.caf.io/pt/termos-e-condicoes-de-uso) *and the* [*Privacy Policy*](https://www.caf.io/pt/politicas-de-privacidade)*."* {% endhint %} ### 2. Getting the document reference Once you have your access token, you can request a **document reference** for reuse. We provide a service that checks whether the user's documents already exist in our centralized database. If a match is found, the response will include the `documentRef` — a hash string that references the stored document. {% openapi src="/files/nHsMWbvODWjbKlG4FaPN" path="/" method="post" %} [doc-less.yaml](https://3218940882-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVxCOSyBojfSIE5fcpfH%2Fuploads%2Fgit-blob-77c6dea5f449b777223273a991783b2fe4c38db8%2Fdoc-less.yaml?alt=media) {% endopenapi %} ### 3. Reusing the document reference If the response from the previous step is successful and the `status` is `"FOUND"`, the `documentRef` property will be returned. With this reference in hand, you can proceed to create a transaction in Certta's processing flow. To reuse the document, pass the `documentRef` in the `files` array when creating a transaction with the type set to `"DOCUMENT_REF"`: ```json { ... "files": [ "data": "", "type": "DOCUMENT_REF" ] } ``` You can find the full documentation on how to create a transaction by [clicking here](/caf-api/connect/available-resources/transaction.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.caf.io/caf-api/connect/available-resources/synchronous-services/doc-less-sync.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.