Documentation
Overview
FAQ

FAQ

General

  • Infermedica provides APIs (Application Programming Interface) for preliminary symptom analysis and patient triage that can be implemented in intelligent symptom checkers, medical bots, and adaptive patient intake forms as well as health applications.

    After receiving a patient’s health data (such as: symptoms, risk factors and/or demographics), our inference engine will analyze it and provide you with a list of most probable conditions, triage level, specialist recommendation, and more - all thanks to the sophisticated statistical algorithms we use to perform AI-driven analysis. Currently we have two APIs, Platform API and Engine API.

    If you would like to know more about Infermedica or our products, please contact us.

  • Please take a look at some of our case studies.

    • Get in touch with our team to see what plans are available. After your account is approved, you will get credentials, and be able to use one of Infermedica’s APIs.
    • Make your first request.
      • For Engine API, check the Quickstart section of the documentation to find a short introduction on how to start using an API.
      • For Platform API, see Getting started.

Licensing and pricing

  • Infermedica’s APIs are available on several plans. For detailed pricing, please get in touch with our team. It’s also possible to apply for a trial access account, which includes up to 2,000 API calls.

  • If you exceeded the granted trial API calls and would like to continue making calls, you’ll need to upgrade your plan. To do so, please get in touch with our team.

    Upgraded plans may allow you to use Infermedica’s APIs in their entirety, share them with the wider public, or commercialize them, depending on which plan is chosen.

  • If your account has been blocked/deleted, it’s probably due to a violation of the Terms of Service. The most common violations involve one of the following:

    • Using more than one API account.
    • Providing illegitimate account information (e.g. a temporary/fake email address).
    • “Scraping” the database.

    If your account is blocked or deleted, we will send you an email explaining why.

    ℹ️

    If you believe your account has been blocked/deleted by mistake, please contact us.

Trial access

  • Every account is verified and approved by our team. We want to make sure all the information you provide is real and accurate. This approach allows us:

    • to build an active and engaged community of developers and professionals, who share our passion for creating great healthcare apps
    • to prevent subscriptions from users who have previously violated our Terms of Service
  • Granting you access to the trial depends almost entirely on the information you enter in the contact form. To get through the approval process smoothly, please make sure you provide:

    • full name of the organization you represent
    • your business email
    • real name and surname
    • your role in the organization
    • a brief description of the project in which you would like to use/try Infermedica’s Platform API

    If we have trouble verifying your information, we'll reach out to you.

  • There might be a few different reasons why your account hasn’t been approved:

    • You provided unspecific or too generic information in the request form. For example:
      • Personal email address instead of corporate email address
      • Invalid or spam/temporary email
      • No specific organization (e.g. “Self”, “No”)
      • No name and/or surname
      • No answer or too generic an answer to the question “How do you intend to use Infermedica API” (e.g. “Test”, “self” “I don’t know”)
    • You already have an account linked to you or your organization.
    • You used to have an Infermedica API account which has been blocked or deleted due to a violation of the Infermedica API Terms of Service.
    ℹ️

    You can always resubmit your form with the proper information. Please refer to: What are the requirements to get a trial access?

Medical content

  • We publish an easily-browsable list of symptoms and conditions.

    When using the Engine API, the most reliable way is to obtain them through the API itself (using either the /symptoms or /conditions endpoint), as this will always fetch the current version. For the Platform API, please refer to our Navigating question flows section.

    The API Reference section in our developer portal (after you’ve successfully logged in) and Postman are also useful options when using the Engine API.

  • English is the primary language of our medical database. In custom plans involving our Engine API, however, we support multiple languages, including:

    • Arabic
    • Chinese (Simplified)
    • Chinese Traditional (Hong Kong)
    • Czech*
    • Dutch
    • English, used by default*
    • Estonian
    • French*
    • German*
    • Greek
    • Italian
    • Japanese
    • Latin American Spanish
    • Polish*
    • Portuguese
    • Portuguese (Brazilian)
    • Romanian
    • Russian
    • Slovak
    • Spanish
    • Thai
    • Turkish
    • Ukrainian

    * Languages currently available for our Platform API. For the most up-to-date list of languages available for our Platform API, please contact us.

  • The content development process is divided into stages. These include defining the scope of the desired changes, eliciting expert knowledge based on the literature and other available sources, specifying test criteria, performing manual and automated acceptance tests, and finally deploying the verified model to the API. The process can be efficiently repeated with automated regression tests to guarantee the stability of the system.

    You can read more about the knowledge base in the Medical content section of the API documentation.

    If you would like to learn more, please contact us.

  • The knowledge base is nurtured by our team of doctors, who rely on respected literature, medical textbooks and publications. This process is also supported by the analysis of huge data sets to extract statistical relations and numerical approximations of diseases. You can read about the knowledge base in the Medical concepts section of the API documentation.

    If you would like to learn more, you can contact us directly.

  • The medical content used in Infermedica's APIs accounts for infants, children, adolescents, and adults. This allows parents to run the initial symptom assessment and triage on children that are just a couple of weeks old and up.

Pediatrics content

  • The exact age plays an important role in the symptom assessment of infants and small children. We decided to ask for the exact date of birth to ensure a better user experience.

  • You can start by contacting the Infermedica team to discuss pricing. Pediatrics content is fully compatible with Infermedica's APIs and constructed in a way that enables it to be deployed in existing implementations with ease.

  • The costs of implementing pediatrics content vary depending on a variety of factors including whether it's a new or existing customer.

    If you are already using one of Infermedica’s APIs, you can discuss pricing with our support team. If you are potentially considering using an API, our sales team can provide you with pricing options.

Other

If you didn’t find the answer you were looking for, please contact us.