# Introduction!

## Welcome to KLINICLY API

KLINICLY is an Open Source API that's enables innovators and health-tech businesses to easily embed and distribute genuine drugs using our formulary within their products with the aim to fully digitize healthcare processes within Africa. Collaborators within the products includes (Health-tech companies , HMOs, Hospitals, Manufacturers )

Welcome to the Klinicly API! You can use our API to access Drug API endpoints, which can get information on drugs, drug products,brands and drug generics in our database.

The Drug API is organized around REST. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients. JSON is returned by all API responses, including errors, although our API libraries convert responses to appropriate language-specific objects.

You can view code examples in the dark area to the right, and you can switch the programming language of the examples with the tabs in the top right.

## Want to jump right in?

Feeling like an eager beaver? Jump in to the quick start docs and get making your first request:

{% content-ref url="/pages/gLgcsrNlvva64AlIdyed" %}
[Before you start.....](/before-you-start......md)
{% endcontent-ref %}

## Want to deep dive?

Dive a little deeper and start exploring our API reference to get an idea of everything that's possible with the API:

{% content-ref url="/pages/kHxIMv34aUo9OOzXqzV5" %}
[API Reference](/reference/api-reference.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.klinicly.net/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.