Set up your custom API

Set up your API

Once you have signed up and logged in at, navigate to the docTI tab and press the Create a new API button, as shown below:

First, we need some basic information about your new, custom document processing API. That info will help us highlight your API under the tab My APIs .

The requested properties are the following:

Document type

This field is used to define your API name and endpoint url.

To ensure best performances:

  • use words that describe your document the best, i.e "ID card" if you aim at processing ID cards;
  • avoid using generic names that do not correspond to a document type, i.e. "Test API".


Define the regions: countries or continent from which your documents originate from. By default worldwide.

You can either start typing the country or continent to filter the list, or scroll.


Choose the industry related to your use case. You have the following choices possible:

Legal ServicesDocument parsing or legal firms to extract and analyze legal documents, contracts, and case files.
HealthcareParsing medical records, patient histories, and insurance claims is vital for healthcare providers and insurers.
Finance and BankingParsing financial statements, transaction records, and banking documents helps with auditing, compliance, and customer service.
InsuranceParsing policies, claims, and customer information is essential for insurance companies to process claims and underwrite policies.
Real EstateParsing property documents, leases, and contracts helps in property management and real estate transactions.
Human ResourcesParsing resumes, job applications, and employee records assists in recruitment, onboarding, and talent management.
Government and Public SectorParsing official documents, public records, and forms for administrative purposes and compliance.
Retail and E-commerceParsing invoices, receipts, and product catalogs aids in inventory management, sales analysis, and customer service.
ManufacturingParsing production records, supply chain documents, and quality assurance reports helps in production planning and quality control.
EducationParsing student records, transcripts, and academic documents supports admissions, enrollment, and academic research.
Logistics and TransportationParsing shipping documents, delivery orders, and freight manifests assists in logistics planning and tracking.
Marketing and AdvertisingParsing customer feedback, surveys, and marketing reports helps in market analysis and campaign optimization.
Energy and UtilitiesParsing utility bills, energy consumption reports, and infrastructure documents aids in energy management and billing.
TelecommunicationsParsing customer contracts, service agreements, and billing statements supports customer service and billing operations.
AgricultureParsing agricultural reports, crop yields, and supply chain documents helps in farm management and planning.
Media and EntertainmentParsing content metadata, distribution agreements, and licensing contracts supports content management and distribution.
AutomotiveParsing vehicle registration documents, maintenance records, and warranty information aids in vehicle management and service.
Travel and HospitalityParsing booking confirmations, itineraries, and customer reviews assists in reservation management and customer service.
PharmaceuticalsParsing drug labels, clinical trial data, and regulatory documents supports drug development and compliance.
Technology and SoftwareParsing software licenses, technical documentation, and user feedback helps in software development and customer support.


The Document type, the Region and the Industry are used to pre generate a first data model to set you on the right path to a performant product.

API name

The resource name of your API URL. We automatically generate one for you based on your Document type but you can customize it at your own convenience. Note however that you can’t use special or accented characters. The format of your API URL complies with the following scheme:[username]/[API_name]/v1/predict


An optional, short blurb aimed at conveying the purpose of the API. This description will appear below the image under my APIs tab (and others if you choose to share your API with other users). We suggest you make it as clear and concise as possible to maximize its effectiveness.

Add a typical document of your use case

It is therefore recommended to have at least 1 document nearby. This document will be used to test and validate your data model.

After adding your validation document, Mindee will prepare your product and build an initial data model

Data model definition

When you arrive at this stage, you will be proposed a first data model with the results of the inference already visible.

You will of course have the possibility to Edit or Delete each of those fields to ensure your final data model matches your needs.

By clicking on Add new field you have the possibility to add a new field to the data model and for each to choose the type amongst the following one:

You can add fields by clicking on the corresponding card:

  • String: This field is the most generic one. You can use it to extract a specific text from a document, i.e. a First Name from an Id card.
  • Number: A number field can be any decimal number or integer, such as amounts, percentages, quantities…
  • Date: Date can extract both Date and / or Time. Dates can be written in any format and will be returned in ISO formats yyyy-mm-dd.
  • Phone number: A phone number can be any phone number (any countries).
  • Email address : to extract email addresses.
  • URL: URL can be any kind of URLs, websites, links, …
  • Classification: Define the set of possible classes the documents can belong to. Each class must be exclusive: a document must belong to one class and cannot belong to many classes. If the document belongs to none of the proposed classes, the output will be Null.
  • Object: Define a composite field which includes one or several items of different types. Can be used to extract tables from documents.

Once you select a field type, the following information is required for each field:

  • Field Name: For each field, define a name that will be used to create the corresponding API JSON response key.
    To ensure maximum extraction performances:
    - use descriptive and explicit words, i.e. “First Name”, “Last Name” or “Full Name” instead of “Name”;
    - avoid names that do not correspond with what you are trying to extract, i.e. "Field 1";
    - when applicable, use words that are used in the document for describing the value you want to extract, i.e. “Date Of Birth: 01/01/2000” use the name “Date Of Birth”

  • API response key: is directly defined from the Field Name and cannot be edited.

  • Example: Examples are very important to describe:

    • formatting instructions (respect case);
    • example of data the model should extract.
      To improve performances:
    • use a real world example from a document;
    • respect the case and the format you want for your output;
    • don’t describe the field.
  • The answer can have multiple values: Check the box if you need the model to extract several values in the documents. The values will be outputted as a list.

Whenever you modify the data model, you will have the possibility to retest it: A button will appear on the image Test your data model.

Once you’re done setting up and testing your data model, press the Create API button at the bottom of the screen.

Slack Logo Icon  Join our Slack