Hardware requirements
To test or integrate the Parklio API with physical hardware, you need at least one controllable device connected to your Parklio account.
There are two main ways to build this setup.
Option 1: Use a Parklio Product
You can use one of the supported Parklio products, such as a Barrier, Gate, Chain, or Bollard. You can view the available products on the Parklio website.
These products are added to your Parklio account using the Parklio Connect app. Once registered, they can be controlled locally over Bluetooth or remotely through the Parklio API when a Parklio Gateway is connected to the parking lot.
For API development and testing, one supported Parklio Product is enough to create a basic environment.
Option 2: Use an existing device with Parklio Brain
You do not need to replace an existing access-control device to integrate it with Parklio.
If you already have a compatible gate, garage door, barrier, bollard, or similar access-control system, you can connect it to Parklio Brain.
Parklio Brain acts as the interface between the existing device and the Parklio ecosystem. The connected device can be controlled locally through Parklio Connect and, when combined with a Parklio Gateway, remotely through the Parklio API.
Do I need a Parklio Gateway?
A Parklio Gateway is required when you want to control supported Parklio devices remotely through the Parklio API.
Parklio devices communicate locally over Bluetooth. The Gateway acts as the intermediary between the device and Parklio Cloud, allowing commands from your application to reach the physical device remotely and allowing product state to be returned to the API.
Without a Gateway, compatible devices can still be controlled locally over Bluetooth using Parklio Connect or, for supported mobile integrations, the Parklio SDK.
Minimum API test environment
A basic API test environment consists of:
- one Parklio Product, or one compatible existing device connected through Parklio Brain;
- one Parklio Gateway;
- a smartphone with Parklio Connect;
- a Parklio API Account.
The physical product is registered through Parklio Connect and assigned to a parking Zone, while the Gateway is assigned to the Parking Lot.
Once both are configured, you can begin testing API commands and receiving real-time device state updates.
Parking Detection hardware
If your integration uses real-time parking-space occupancy, additional Parking Detection hardware is required.
Parking Detection is configured for the specific parking lot. Depending on the installation, the system can use dedicated detection cameras or compatible existing IP cameras.
After the hardware is installed, parking places are mapped to the corresponding Lot in the Parklio Account. Your application can then retrieve occupancy information through the API and receive real-time parking-place changes through WebSockets.