Interfaces
As we have mentioned earlier, our data model is what enabling the fast query execution speed. That means, not only we could offer a flexible analytical tool for the research team, analysts and their use-cases that doesn't require fast query execution, but we are also making it possible to perform the software integrations via an API.
![Screenshot 2022-10-27 at 08.35.37.png 2018](https://files.readme.io/2ab5caf-Screenshot_2022-10-27_at_08.35.37.png)
An exhaustive guide to our web application can be found at this link:
We offer two types of API - REST and SQL. We describe in detail the difference in the benefits of each in a separate section, available at the chapter:
Speaking of the latter, SQL API, we have laid down a unique UX that allows us to quickly get desired insights immediately on the web application before software integrations and, when satisfied with the query results, simply reuse it within the API. Making a simple visualization, the process will be as follows:
![Screenshot 2022-10-28 at 09.38.21.png 2698](https://files.readme.io/e99a0dc-Screenshot_2022-10-28_at_09.38.21.png)
Web application -> SQL API
Thus, the analysis of which area, you would not carry out; queries, as complexities, you would not have to describe within the drag-and-drop interface or directly in SQL, for example, using nesting, window functions, correlated subquery and other advanced concepts, you can be sure that insights will be possible to port from the interface with the purpose of obtaining them in the form of hierarchical structures from the API. Below you can see a variety of project examples built using our data:
![Screenshot 2022-10-28 at 09.52.20.png 2776](https://files.readme.io/6b46126-Screenshot_2022-10-28_at_09.52.20.png)
Updated almost 2 years ago