The API between
travellers and parking.
One integration. Every operator. Built by APCOA (Europe's largest parking-operator) so you can stop worrying about edge cases...
Travellers book parking last. Or not at all.
Every flight, hotel, train, or event booking has a parking question attached to it. Online Travel Agencies see it on customer feedback, support tickets, and missed checkout revenue — but the supply side is hundreds of independent operators, each with their own platform and contract terms. Bilateral integration with every operator doesn't scale. Selling no parking, or generic third-party parking, leaves money and customer experience on the table.
Parking operators see the mirror image. OTAs are where their customers actually decide to travel — yet onboarding into each OTA's tech stack is a years-long bilateral negotiation that few operators have the bandwidth to pursue. The result: parking gets sold at the barrier, late, often at a premium, and almost always after the booking decision has already been made elsewhere.
One API. Both sides. No payment processing.
ParkAttach is the integration layer. OTAs call a single quote / reserve / commit API to embed pre-booked parking into their existing checkout. Parking operators connect their parking platform once — via APCOA's Parkway and Nucleus today, plus partner connectors on a per-platform basis — and reach every OTA on the platform under terms they set per channel.
Payment processing stays where it already is: in the OTA's checkout. ParkAttach mediates inventory, not money. The bilateral commercial agreement between OTA and operator — commission split, pricing rules per channel, cancel windows — is configured in the platform and applied at quote time.
An APCOA initiative
APCOA is Europe's largest parking-operator group, with car parks at hotels, airports, train stations, stadiums, music venues, and conference centres. ParkAttach is built inside APCOA — the platform starts with APCOA's own inventory and grows the partner-operator roster on the same terms. That's the difference between a marketplace bolted onto a directory and a marketplace built by an operator who has been on the other side of this problem for decades.
How we build
A handful of decisions that shape the platform — engineering choices that translate directly into partner experience.
Hot-path discipline
Three layers of cache keep the typical quote under 2 ms wall clock. Nothing on the response path widens a database query for analytics convenience.
Permission is the agreement
An OTA's right to sell a car park is encoded as an active bilateral agreement. There is no separate visibility ACL — the contract is the access.
Fair commission, per channel and per venue
The same car park can carry different commission and pricing for Expedia, IHG, and Booking.com — and different terms when sold alongside a hotel versus a rail station. The data model is the deal.
Graceful degradation everywhere
Kafka outages don't fail quotes. Urgency-service timeouts return absent fields, not 5xx. Capacity miss falls back to live state, not stale data.
Partner-first roadmap
Connector tiers, agreement structure, and cancel semantics are shaped by what partner operators and OTAs need, not by a planning calendar.
Demand made visible
Every quote surfaces nearby car parks the calling OTA can't yet sell — so operators can see the bookings waiting at their sites before they ever commit.
Sound like a fit?
Whether you sell travel or supply parking — start a conversation and we'll work out what an integration looks like for you.
Book a demoSound like a fit?
Whether you sell travel or supply parking — start a conversation and we'll work out what an integration looks like for you.
Book a demo