Connectivity methods supported by Proqio

1. FTP/SFTP

Proqio hosts an FTP/SFTP server to which third parties can send device data files. The server supports both FTP and SFTP (upon request) protocols on different ports.

Users can create their own FTP server instance directly from the Proqio interface. Which will provide the connection details (including address, protocol, ports, directory path (folders), and authentication credentials (username and password)) to connect to the FTP server.

Note: Certain restrictions apply to the FTP server to ensure efficient data processing.

2. MQTT

Proqio also supports MQTT for data transmission. An MQTT server instance can be created from the Proqio interface, which will provide the connection details (including address, port, topic, and authentication credentials).

3. PUSH HTTP API

Proqio offers an HTTP endpoint for sending device data. As with other methods, users can create the connection through the interface and get its details.

Authentication options for PUSH HTTP API: Two methods are allowed to authenticate HTTP requests. Connection details for both are provided from the Proqio interface.

Basic Authentication: Using username and password
API Key Authentication: Using an API key in the HTTP request. Either in the headers or in the request query.

4. PULL HTTP API

Unlike the previous methods where data is pushed to Proqio by a third party (devices, gateways, servers…), the PULL HTTP API allows Proqio to periodically retrieve data from a third-party HTTP API.

Therefore, for it to work, several requirements must be applied to the third-party API:

The connection address must be publicly accessible over the internet.
The third-party API must provide an HTTP server that allows for data retrieval.

Supported authentication methods:

Basic Authentication (username and password)
Bearer Token Authentication
API Key Authentication (via headers or query parameters)
OIDC (with prior login for token retrieval step)

API response and structure requirements:

HTTP method must be GET or POST. If POST is used and the request body is required, the API must accept application/json or plain text.
The endpoint should allow the selection of the device(s) from which to obtain data.
The endpoint must allow selecting a data range to get data from in a suitable format (preferably ISO 8601 compliant).
Response data must be structured in JSON, CSV, or plain text formats.
Devices records returned must be ordered by date/timestamp.

Data Format and Parsing

With any of these connection methods in place, Proqio will be able to receive the data.

Proqio is capable of ingesting heterogeneous data formats. Our platform supports the creation of custom parsers to convert incoming data into Proqio’s internal format.

Commonly supported formats include CSV, JSON, and plain text. In cases where the format is uncommon or complex, a case-by-case assessment may be required.

Compatibility with Existing Solutions

Proqio is a technology-agnostic platform that connects with leading instrumentation providers and monitoring systems worldwide through standard protocols such as FTP, SFTP, MQTT, and HTTP APIs (pull and push), ensuring reliable interoperability with your existing infrastructure.

These providers include the following, amongst others:

Worldsensing
Leica GeoMos
Topcon
Senceive
Ackio
BDI
Campbell Scientific
Comnav Technology
Delta IoT
Detektia
DeweSoft
Encardio Rite
Geobotika
Geofem
Gintec
Instantel
IqSoft TCB
Korr.AI
Move Solutions
Omnidot
Osprey
RIEGL
RST, Measurand (ShapeArray)
Satshot
Sigicom
Trimble
Wisen Innovation
Custom Basemaps
UAVs