Technology
Integration & interfaces in the PARQ system
With integrations & interfaces, PARQ works together with the systems you already use: hotel software, accounting, parking apps, payment services, data platforms and much more. Ready-made integrations and an open interface are available for this. Existing technology at the entrance is also connected, as far as its controls allow, rather than being replaced.
Integration & interfaces at a glance
PARQ fits into what you already have in place: existing barriers and roller doors are connected rather than replaced, as far as their controls allow. Data is sent via interface, as a live event, or directly into your BI tool, wherever you need it. Ready-made integrations connect payment service providers, parking apps and much more.
- Connecting existing barriers and roller doors instead of replacing them, as far as the controls allow
- Open REST-API, fully documented
- Webhooks & events live
- BI integration: Power BI, Tableau, Google Looker
- PARQ Connect: payment service providers, Microsoft 365, parking apps, hotel software, traffic guidance systems via the Mobilithek and much more
Integrations
Integration & interfaces in everyday use.
Connect rather than replace: what already runs on your site and in your building stays. Existing barriers and roller gates are connected to PARQ via their controller, as far as the controller allows, and then open via licence plate recognition. Only what is missing is added, usually the cameras at the entrances and exits. This keeps the conversion small, and the site remains usable during the changeover. The same goes for software: your hotel software, your accounting, your parking apps and payment providers keep running and work together with parking operations. Ready-made integrations exist for Microsoft services, the Mobilithek, parking apps such as Parkster and PayByPhone, and payment providers such as Stripe, Adyen, PAYONE, TeleCash, Mollie, Klarna, PayPal, Wero and many more. Where there is no ready-made integration, the route is the open interface: parking sessions, payments and reports can be retrieved and transferred into your systems. New integrations are added continuously.
Connect existing barriers and roller doors
A barrier or roller door that's already in place doesn't need to be replaced. Its controls are integrated, and after that the system opens via licence plate recognition: for authorised licence plates, for booked tickets or according to your rules. We clarify whether this works for your installation when we survey the site.
- Barriers and roller doors stay, the control system is connected
- Opens via licence plate recognition, without a ticket
- Small-scale conversion, site stays usable during the changeover
Your software keeps running
Hotel software, Microsoft services, accounting, parking apps such as Parkster and PayByPhone, payment providers such as Stripe, Adyen, PAYONE, TeleCash, Mollie, Klarna, PayPal and Wero, plus the Mobilithek for traffic data and many more. Whether an integration is possible also depends on the interfaces your software offers.
- Hotel and point-of-sale systems
- Parking apps and payment service providers
- Accounting and reports, for example in Power BI
- Traffic data to guidance systems and portals
- And much more
Your own integration via the open interface
Where no ready-made integration exists, the way forward is via the REST API and webhooks: parking sessions, payments and reports can be retrieved and forwarded, and events arrive live. Which fields the target system expects is clarified in advance.
Further functions
- Vehicles on the area, live
- Every parking session with entry and parking duration
- Revenue per area and payment source
- Outstanding receivables in view
- Violations recorded automatically
- Automatically transmitted to your service provider
- Whitelist individually, as a group or by list
- Authorisations for an occasion
- Tariffs per area and time window
- Free parking periods and special rules
- Night, weekend and monthly tickets with a fixed term
- Valid for the areas you define, with period and capacity if desired
- Your own rules for each area
- Utilisation per zone
- Peak times, parking duration and much more
- Raw data export as JSON, XML, CSV, Excel or PDF
- At the pay station: card, contactless or Apple/Google Pay, and with the PARQ Automat A2 cash too
- Via app or QR code
- Authorisation via QR code and charging receipt
- Your rule for people charging
- At a tablet on site, e.g. at reception
- With a disability card via QR code
- Full logo, small logo and favicon
- Your own colours and your own typeface
- GDPR-compliant
- Encrypted transmission
Your parking system. Your rules.
Ready at a click.
Integration & interfaces: common questions.
No. Existing barriers and gates are integrated and continue to be used, if their controls allow it. Only what's missing is added, for example cameras at the entrances or a pay station. That keeps the conversion small and the area usable during the changeover.
Ready-made integrations exist for Microsoft services, the Mobilithek, parking apps and many payment providers. Everything else runs via the open REST API and webhooks, such as your accounting or your own data platform. New integrations are added continuously, so ask us about your system.
PARQ has open interfaces, so connecting the hotel software is generally possible, for example so that guest authorisation doesn't also need to be maintained at reception. Whether it works in a specific case depends on whether your hotel software allows such a connection. We'll check this together.
Yes, via open interfaces. For example to the Mobilithek. Utilisation, occupancy and reports can be passed on, depending on what your system expects. That way the values from your areas feed into traffic management without anyone passing figures on by hand or maintaining lists.