Connect the systems you already run
ParkAgenda connects to the ANPR, barrier and on-site systems you already run, through our API and a connector our team builds with your supplier. The work on site can be handled by a local partner close to your parking.
- 93REST endpoints
- 2bespoke connectors already live
- 4ways a booking gets in
Four ways a booking gets into ParkAgenda
All four produce the same booking record, attributed to the source it came from. Two of them are connectors our team wrote for a named supplier, which is the part worth reading twice.
- API pull, live
Parkos
Bookings arrive on their own, per merchant, with the arrival window already reconciled.
What that means in practiceA direct pull from Parkos, per merchant. Credentials sit in Azure Key Vault, sync cursors run on the updated and cancelled timestamps with an overlap so nothing falls between two runs, and arrival windows are reconciled on the way in. A booking that cannot be linked to a merchant is quarantined rather than dropped, and an operator can force a pull at any moment.
- Polling bridge, live
Solution Park
The second one, added the same way, without touching the platform.
What that means in practiceA second bespoke connector, polling on a sliding window. It was added the same way the first one was, and that is the argument: a new source is one adapter behind a shared interface, not a change to the platform.
- Email adapter
The reseller’s own format
The reseller keeps sending the email they already send.
What that means in practiceEach parking gets a monitored address. A booking source declares the format its emails arrive in and an adapter translates it, so the reseller changes nothing on their side. Senders are whitelisted by exact address, and a duplicate delivery is caught on the message id or a hash of the body.
- Import
CSV migration
Your booking history comes in as a file, and can be re-run safely.
What that means in practiceHistoric bookings come in as a file. The import is idempotent on the parking, the source and the reference, so running it twice changes nothing, and every row comes back as created, updated, unchanged or failed with the reason it failed.
Anything that cannot be applied safely lands in a review queue with the raw evidence attached. A person promotes it, reprocesses it, whitelists the sender or dismisses it. Nothing is silently dropped.
A real REST API, described in OpenAPI 3
It is the same API the ParkAgenda console runs on. Nothing is held back for a higher plan and nothing on this list is a stub.
What the API is not
- There is no self-service programme. No API keys, no client credentials, no sign-up form. A caller needs an identity in our own tenant, which means we set the access up with you rather than handing you a token page.
- ParkAgenda receives webhooks and does not send any. There is no event subscription and no callback URL. Data leaves by reading the API or by taking an export.
We would rather write that here than say it at the demo.
93 endpoints
Bookings, parkings, organizations, users, shifts, shuttle legs, analytics, cash, vehicle check-ins and intake records, on clean resource routes.
An OpenAPI 3 document
Titled ParkAgenda API, version 1.0.0. Nearly every operation carries its parameters, its request body and its responses, so a client can be generated instead of guessed at.
Bearer token authentication
Microsoft Entra External ID issues the JWT. Roles are read from the token and never from the caller, so an integration cannot ask for more than the identity it was handed.
Three inbound webhooks
Stripe billing events with the signature verified, SendGrid delivery outcomes, and SendGrid Inbound Parse for booking intake behind a function key.
Exports out
Bookings, raw analytics rows and the cash recap all export per parking, over the same authenticated API.
ParkAgenda has no ANPR of its own. It connects to yours.
No cameras, no barrier control, no reader, no kiosk. What ParkAgenda does have is the plate on every stay and an API to match it against. Your plate recognition keeps doing exactly what it does today, and we build the connector between the two with the supplier who installed it.
Said plainly
If you are looking for a supplier who sells you the cameras and the barriers, that is not us. If you already have them, or you are buying them from someone local, ParkAgenda is the software behind them and the integration work is ours.
How it works in practice
- Your camera reads the plateThe read happens in your own system, on your own hardware, exactly as it does today.
- The plate matches a stayEvery booking in ParkAgenda carries the vehicle plate, normalized for search, so a read resolves to a customer, an arrival window and a spot.
- Your system decides what happensOpening a barrier, lighting a sign or logging an entry stays with the equipment that already does it. ParkAgenda supplies the booking, not the command.
The work on site is done by a partner near you
Cabling, mounting, supplying the cameras and the barrier, commissioning: that is a job for someone who can be at your site within the hour. We work with local installers and integrators close to the parking, and we take the software side and the connector.
What ParkAgenda does
- Writes and maintains the connector between your equipment and ParkAgenda.
- Runs the API, the field mapping and the reconciliation once bookings start moving.
- Stays on the call with your supplier until the two systems agree.
What the local partner does
- Supplies, mounts and cables the cameras, the barriers and the screens.
- Configures the equipment on site and commissions it with you.
- Answers when something physical needs a person at the gate.
You run a parking
Tell us what hardware is on site today, who supplied it and what you want it to do. We will say honestly whether we can connect it and what that takes.
Describe your setupYou install parking equipment
If you fit plate recognition, barriers or access control near an airport, we want to know you. We bring the software and the connector, you bring the site.
Become a partnerFive steps, and roughly how long each one takes
These durations come from the two connectors already running, not from a sales deck. The variable is almost never our side of the work.
We list what you run
One callYour plate recognition, your barrier, your booking sources, the export your accountant wants. We ask who supplied each one and whether there is documentation.
We agree the data contract
A few daysWhich fields move, in which direction, how often, and what happens when the two systems disagree. It is written down before anybody writes code.
We build it against your test data
Two to four weeksA source connector is one adapter behind a shared interface. That is how Parkos and Solution Park were added, and it is why the second one took less time than the first.
We run it in parallel
Two weeksYour current process keeps going while the connector writes into ParkAgenda. Every booking is reconciled before anything is switched off.
We keep it running
OngoingSuppliers change their format without warning. When that happens the adapter is ours to fix, and the review queue means the affected bookings wait for a person instead of vanishing.
The honest caveat: a source that arrives by email is usually the fastest thing we do. A connector against a supplier’s own API depends on their documentation and on how quickly they answer an email. We have had both.
The six we are asked before every contract, answered the way we answer them on the phone.
Does ParkAgenda include ANPR?
No. ParkAgenda has no plate recognition of its own, no cameras and no barrier control. It connects to the ANPR system you already run through our REST API, and our team builds that connector with the supplier who installed it.
Can ParkAgenda work with my existing ANPR car park management system?
Yes, through the API and a connector we write for it. Every booking in ParkAgenda carries the vehicle plate and it is indexed for search, so a plate read by your own system resolves to a stay, a customer and an arrival window.
Do you have a public API I can sign up for?
No, and we would rather say so here. There is a documented REST API with an OpenAPI 3 description, but access needs an identity in our own tenant, so we set it up with you. There are no self-service API keys.
Does ParkAgenda send webhooks to my system?
Not today. ParkAgenda receives webhooks from Stripe and SendGrid, and it does not send any. Data leaves by reading the authenticated API or by taking an export, and both work per parking.
Who installs the cameras and the barriers on site?
A local installer near your parking. ParkAgenda works with integrators close to the site for supply, cabling, mounting and commissioning, while we handle the software, the API and the connector between the two.
How long does a custom integration take?
A new booking source that arrives by email is usually live in about two weeks. A connector against a supplier’s own API typically runs four to eight weeks from the first call, and the pace depends on how quickly that supplier answers.
Tell us what is already on your site
The camera, the barrier, the platforms you sell through, the export your accountant asks for. We will tell you what connects today, what needs a connector, and what we cannot do at all.
Set-up in 24 hours
Lots, sources and operators configured with you.Your data stays yours
Export any view to CSV or PDF, whenever.FR & EN support
By people who have worked a parking desk.