# Introduction to Unisphere APIs

## Unisphere API Philosophy

Unisphere´s public APIs allow to use services/features / NOVA directly via API and provide direct access to technologies (Tech APIs).

* NOVA API allows direct access to the same functionalities users will find on the NOVA Web application. E.g. CRUD operations for assets, operational limits, routes, missions etc. (non-exhaustive list). Some functionalities are not planned via public APIs at the moment e.g. user management, subscription management or similar.
* Except for flight checks, anything created, updated or deleted in the NOVA frontend, or via a Unisphere API is synced. Factually there should be no difference whether an asset is created in the web app or via API.
* Tech API allows direct access to technologies provided by Unisphere – e.g. Geo Information Service, or access to a trajectory simulation, services for U-Space Applications. They can, but must not be part of NOVA.

<figure><img src="/files/fBj5aBKB69s0wBPERDfI" alt="A scheme of Unisphere Public API that shows several levels: users → Public API → Web App Products"><figcaption><p>Unisphere Public API Scheme</p></figcaption></figure>

## Product Hierarchy

As part of our development roadmap, we are enhancing our technology by opening up multiple functionalities through a public REST API, making it accessible and integrate with external systems.

The functionalities are categorized into three levels: missions, flights, and assets. Each functional level offers different granularity of requests. Initially, public API users will be able to interact with missions already available in NOVA. For example, users can request a check for a flight at a specific take-off time. In subsequent developments, the API will allow users of the API to include all necessary information to execute these checks directly without NOVA.

<figure><img src="/files/tEYMbimpI8rEFqgYnbFF" alt="An overview of six API functions Unisphere offers"><figcaption><p>API Functions overview</p></figcaption></figure>


---

# 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.unisphere.io/unisphere-apis/introduction-to-unisphere-apis.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.