Data Link Backend
Required roles:
ATC Data Link Access— Roles
Base endpoint:https://dlink-api.ibosoft.net.tr:2096
Reference documents: ARINC Specification 618-6 Air/Ground Character-Oriented Protocol Specification (16/06/06) · ARINC Specification 620-6 Datalink Ground System and Interface Specification (15/11/07) · ARINC Specification 622 · ICAO Annex 10 Volume III Communication Systems, Ed. 2 (Amend. 92) (28/11/24) · ICAO Doc 10037 Global Operational Data Link (GOLD) Manual, Ed. 1 (2017)
Attribution: showibonav.aerowherever this data is displayed
Data sources: none
Last updated: 18 OCT 2026About the reference documents: Related Documents and Resources
Aviation Data Link messages received by the Ibosoft ATC receivers, served live by the data link backend (ACARS Backend, open source). The ibonav.aero ATC Data Link frontend software uses the same service.
Documentation: the message format, the endpoints and how the backend works are described in its repository: github.com/ibosoftnet/acars-backend.
| Endpoint | Description |
|---|---|
GET https://dlink-api.ibosoft.net.tr:2096/stream |
Live Data Link messages as a Server-Sent Events (SSE) stream |
GET https://dlink-api.ibosoft.net.tr:2096/health |
Service status |
POST https://dlink-api.ibosoft.net.tr:2096/decode |
Decoding of ARINC 622 applications operating via the ACARS network (ADS-C, CPDLC, MIAM …) |
The backend handles all messages. To request stored D-ATIS and DCL messages, two of the ACARS network ATS application message types, for an aerodrome in a simpler way, without requiring a live stream or database connection, use the Data Link API.