Direct answer: Sole plate recognition and parking software does not offer a ready-made public API. When passage records, authorisation lists or payment data need to be transferred to ERP, accounting, property management, visitor or central security software, the integration is developed per project: which data, how often and by which method is decided during the site survey. Device-level connections to barriers, sliding gates and turnstiles are set up as standard via relay and TCP/IP.
How is a project-specific integration planned?
- The target software and the data to transfer are defined (e.g. passage records, subscriber list, daily collections).
- Direction and frequency are agreed: real time, periodic or end of day.
- The methods supported by the other software are reviewed (web service, file transfer, database view, etc.).
- Authentication, access rights and logging rules are defined.
- The integration is verified in a test environment, then taken live.
What is available as standard?
- Report export: 51 ready-made reports in PDF, Excel and Word; scheduled reports can be emailed.
- Device integration: boom barriers, sliding gates, bollards and turnstiles via relay and TCP/IP.
- Payment device: card and QR payments are taken through an integrated fiscal POS device, which issues the fiscal receipt.
- Loop and photocell: via camera alarm inputs.
Which integrations are requested?
The most common requests are transferring daily collections to accounting or ERP software, pulling subscriber/flat lists from property management software, matching guest plates with visitor management apps and forwarding passage events to central security platforms. Each is assessed against the structure of the other software; scope and timing are stated in the quote.
Booth cabinet and local network architecture
The physical system behind the integration sits in the cabinet at the entry/exit booth: PoE powering the cameras, a network switch, electrical protection and barrier relay connections. Cameras, relays and the site PC communicate over TCP/IP on the same network; the site PC works in sync with the cloud software and keeps making passage decisions locally if the internet drops.
Quick technical facts
| Ready-made public API | No — integration is developed per project |
|---|---|
| Standard export | PDF, Excel, Word; scheduled email reports |
| Device connection | Relay, TCP/IP |
| Booth cabinet | PoE, switch, relay connections, electrical protection |
| Payment device | Integrated fiscal POS (issues the fiscal receipt) |
| Operating model | Cloud software + local decision on site |
Frequently asked questions
Is there a ready-made API?
No ready-made public API is offered. When passage, subscriber or payment data must be transferred to other software, the integration is developed per project; its scope is set during the survey.
Which systems can plate data be transferred to?
Transfer to ERP, accounting, property management, visitor management and central security software can be planned per project. The method is chosen according to what the other software supports.
How can I get the data without an integration?
The 51 ready-made reports can be exported to PDF, Excel and Word and scheduled by email. For many accounting processes these files are enough.
Does it work with my existing barrier?
Boom barriers, sliding gates, bollards and turnstiles that can be controlled by a relay are connected as standard; no separate software integration is needed.
How are the time and cost of an integration set?
They depend on the data to transfer, the structure of the other software and testing needs; they are set after the survey and shown as a separate item in the quote.
To see all license plate recognition system types, camera specifications, accuracy conditions and cost logic on one page, read our license plate recognition system guide.
Last updated: September 24, 2026 · Technical content: Gray Teknoloji project team
Get a free survey and quote →