Dronetag provides several integration options to allow access to data from our devices, focusing primarily on Remote ID data. This guide will help you choose the most suitable method for integrating Dronetag into your systems, whether you are working with UTM platforms or building custom solutions.
If you prefer to work with established platforms, Dronetag supports several ready-made integrations:
The integrations currently implemented by Dronetag include:
| Integration | What it is used for | Access method |
|---|---|---|
| Aloft | Sharing Dronetag telemetry with Aloft services. | Dronetag App integration |
| SafeSky | Making Dronetag flights visible in SafeSky. | Dronetag App integration or Data Push |
| InterUSS | Exchanging flight data with U-Space / UTM systems through InterUSS services. | Platform integration |
| TAK Server | Streaming Remote ID data to TAK-compatible systems. | Data Push using Cursor on Target (CoT) XML |
| SAPIENT | Sending Remote ID telemetry as SAPIENT detection reports. | Data Push |
Data Push can also deliver Dronetag's own formats, including DUMP JSON, DUMP JSON Typed, and Dronetag Legacy JSON. These are useful when you are building a custom integration instead of connecting to one of the platforms listed above. See Protocols and Formats for recommended combinations.
For custom solutions or new integrations, we provide multiple options for building the integrations:
If you're unsure which integration method is right for you, check out our guide on Choosing the Right Integration Method for more information and guidance.
Integrating via our API provides a straightforward way to exchange information programmatically with third-party systems or services. We offer two primary methods to facilitate this integration.
By pulling data from our API, you can easily retrieve up-to-date information as needed. We provide an HTTP REST API for standard requests, as well as Socket.io for real-time data access. This method is ideal for server-client integrations, personal scripts, and other applications.
For a more permanent approach, you can set up a data flow that allows our systems to push real-time traffic directly to your API as soon as it arrives on our servers. This method ensures continuous updates without the need for constant requests, making it an excellent choice for server-to-server integrations.
Our cloud platform supports InterUSS services, enabling the exchange of flight data with distributed UTM systems. If your system already implements the InterUSS protocol, it is likely capable of exchanging data with our platform, ensuring a smooth integration process.
Due to limited demand, Dronetag currently offers only a subset of InterUSS services, and development of full compatibility is on hold. We are seeking partners interested in utilizing the InterUSS network for flight data exchange and are open to resuming development for collaborative projects.
If you're interested in exploring this integration further, please contact us to discuss potential collaboration.
Operating within the same Distributed Situational Awareness (DSS) instance as our system facilitates seamless data exchange between both platforms, enhancing operational coordination.
To learn more, visit the InterUSS Platform Official Website.
Currently Supported Services:
If you need to integrate our hardware directly without relying on cloud services, there are several options available to achieve this.
This section is a work in progress.
Some of our products are specifically designed for integration with existing systems. For detailed instructions, please refer to the user manuals for each product:
All Dronetag devices utilize standard Remote ID data formats that comply with the FAA's Remote Identification of Unmanned Aircraft Systems (UAS) rule and the ASTM F3411-22 standard, ensuring seamless interoperability and regulatory compliance.
If you're interested in receiving Remote ID data directly via Bluetooth, you can create your own Remote ID application to decode the signals transmitted by our devices according to the standard.
Please note that we do not provide an SDK for Remote ID decoding or documentation for our proprietary Bluetooth characteristics. If you have a specific project you’d like to discuss with us, please don’t hesitate to contact us for further assistance.
Every chapter of this document is a page of the Dronetag help site. Use these addresses to reach the latest version.