For the complete documentation index, see llms.txt. This page is also available as Markdown.

Developers Guide

Access vertiport sensor data programmatically via the NOVA REST API

This guide is for developers who want to integrate NOVA vertiport data into external systems — for example, flight management software, analytics pipelines, or custom dashboards.

Authentication

All requests require a JWT bearer token issued. Contact your Unisphere representative to obtain credentials.

Pass the token in the Authorization header:

Authorization: Bearer <your_token>

Required Permissions

Goal
Permission

List and read vertiports

vertiport.vertiport.read

Read sensor data and observations

vertiport.readings.read

Contact your administrator if you receive 403 Forbidden responses.

Getting Sensor Data

The typical workflow for reading sensor data from an external system:

1

Find your vertiport ID

List all vertiports in your organization to obtain the UUID of the target vertiport.

GET https://prod.unisphere.rocks/api/v1/vertiport/
Authorization: Bearer <token>
{
  "items": [
    {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "name": "Vertiport Berlin Mitte",
      "vertiport_code": "VPBIC1",
      "latitude": 52.520,
      "longitude": 13.405
    }
  ],
  "total": 1
}
2

Discover available parameters

Retrieve the metric keys available for your vertiport. The available parameters depend on which sensors are installed.

GET https://prod.unisphere.rocks/api/v1/vertiport/{vertiport_id}/parameters
Authorization: Bearer <token>
[
  {
    "sensor_id": "a1b2c3d4-...",
    "parameters": [
      { "key": "air_temperature",    "name": "Air Temperature",       "unit": "°C"   },
      { "key": "wind_speed_average", "name": "Wind Speed (Average)",  "unit": "m/s"  },
      { "key": "wind_direction_average", "name": "Wind Direction",    "unit": "°"    },
      { "key": "air_pressure",       "name": "Air Pressure",          "unit": "Pa"   },
      { "key": "relative_humidity",  "name": "Relative Humidity",     "unit": "%"    },
      { "key": "rain_intensity",     "name": "Rain Intensity",        "unit": "mm/h" }
    ]
  }
]

Use the key values to filter responses in subsequent requests.

3

Fetch data

Choose the endpoint that fits your use case — see the sections below.

Data Endpoints

Latest Observations

Returns the most recent value for each metric across all sensors in the vertiport. Use this for live dashboards and status displays.

Filter to specific metrics using the filter query parameter:

Historical Observations

Returns raw time-series data. Defaults to the last 24 hours; maximum range is 30 days.

There is currently no bulk data export endpoint. If you need a historical data export covering a larger time range, contact support@unisphere.de.

Aggregated Observations

Returns time-bucketed statistics. Use this for trend charts, reports, or reduced-resolution data.

Parameter
Required
Description
Examples

bucket

Yes

Time bucket size

15m, 1h, 1d

aggregation

Yes

Comma-separated functions

avg, min, max, count, sum

start / end

No

ISO 8601 timestamps; default: last 24 h

filter

No

Comma-separated metric keys

air_temperature,wind_speed_average

Vertiport Meteorological Report (VMR)

The VMR endpoint returns a structured aviation-compatible weather string (similar to METAR) for the vertiport.

The tier field indicates which sensor tier produced the report (see Sensor Tiers).

The VMR is computed once per 10-minute window. Subsequent calls within the same window return the cached result instantly.

See the VMR reference for a full description of the string format and group definitions.

Per-Sensor Access

All data endpoints are also available scoped to a single sensor, useful when multiple sensors are installed at one vertiport and you need to distinguish between them.

These accept the same query parameters (start, end, filter, bucket, aggregation) as the vertiport-level endpoints.

Last updated

Was this helpful?