
Developer Programme
Release Notes
22 Jan 2025 Updates
- Aircraft Service has been bumped to version 2.x, and the last version 1.x will cease to be supported. Highlight of non-backwards compatible changes:
drone_providers
is now justproviders
in all schemas- removed denormalised query for providers (removed
provider
query parameter) - added / aligned other query parameters with other aircraft equipment.
- Drone Simulators will now automatically stop after 24 hours of use. We recommend you stop the simulator once you are done.
Airspace Service Migration Guide
If you have UAS Fleet Management API category enabled and use Aircraft Service, please see the full migration guide from 1.x.x to 2.x.x below:
Schema changes
- Drone Model and Dock Model:
- Replace all existing
drone_provider_ids
anddock_provider_ids
withprovider_ids
.
- Replace all existing
- Drone and Dock
- Replace all existing
drone_provider_id
anddock_provider_id
withprovider_id
.
- Replace all existing
- Payload Model:
weight
:string
→number
(align with other equipment weights)dimension.*
:string
→number
(align with other equipment dimension), and dimension no s.
- Dock Model and Payload Model:
- Added standardized fields:
control_interface
,control_metadata
,compatible_drone_models
for integration needs. Can be ignored for the most part of the integration happens at the Drone level, useful when the payload and the drone speak in a different protocol.
- Added standardized fields:
Endpoint Changes (General)
- Replace all calls to
/drone-providers
and/dock-providers
with/providers
- Replace all existing query parameters with
drone_provider_id
withprovider_id
- Remove the existing
provider
orproviders
query parameter. A separate query to/providers
will be necessary to get provider information if needed. - (optional) Add
limit
query parameter to any end point to limit the number of results. - (super admin only) Add
company_ids
query parameter to enlarge the search for Equipments or Flights to cover the specified companies. - (super admin only) Add
all_companies
query parameter to query against all companies in the given server instance to search for Equipments and Flights.
Reminder: what used to be a separate table between cameras
and payloads
has been combined as just payloads
with the additional properties in cameras
captured under camera_properties
in payloads. You will find all previous cameras migrated soon.
Endpoint changes to /drone-models
Deleting a drone model used to be a soft delete. This has been changed to a hard delete to align with all other equipment model’s behaviour. If you need to retain the soft delete, use PATCH endpoint with status: 'deleted'
instead. This also implies deletion of a drone model is not allowed unless there are no drones pointing at it (including soft deleted ones)
Endpoint changes to /dock-models
Deleting a dock model used to be a soft delete. This has been changed to a hard delete to align with all other equipment model’s behaviour. If you need to retain the soft delete, use PATCH endpoint with status: 'deleted'
instead. This also implies deletion of a dock model is not allowed unless there are no docks pointing at it (including soft deleted ones)
Endpoint changes to /flights
- All insurance policies related data has been deleted from the system as it’s been 4 years since the shut down of CoverFlight. The field
policies
no longer exist. - Previously, due to a higher audit requirement that was only applicable to the Flights table, the name of Batteries, Cameras, and Payloads were copied to Flight table’s
batteries
,cameras
, andpayloads
field respectively. This results in an incomplete record.- Moving forward, these 3 fields will be retired, and their ids retained in the Flight table’s
drone.battery_ids
anddrone.payload_ids
respectively. - A separate query to either of this table gives not just the name but the full record of the equipment.
- Care should be taken to avoid changing the equipment’s attributes / reusing equipment IDs.
- Equipment attached to the drone will be found in the
drone
nested object, such asdrone.tracker_ids
. Equipment used that are part of the flight but not mounted on the drone will have its own entries e.g.dock
orcontroller
. - Replace query parameters
trackers
,batteries
,cameras
, andpayloads
with tracker_id,battery_id
, andpayload_id
. They are now for exact matches only.
- Moving forward, these 3 fields will be retired, and their ids retained in the Flight table’s
- Remove query parameter
deployment_id
as it no longer works (a subsequent deprecation will occur where deployments will be migrated to security incidents.