REST, key authenticated
Every request carries an API key in a header. Keys are created and revoked from the Integrations screen, and each one is shown to you exactly once.
Integrations and API
It talks to the systems
It talks to the systems
you already run.
A cart fleet rarely lives on its own. Golf Cart Rental Pro connects to your website, to your reservation system and to anything else through a documented REST API.
Your website
A booking widget for the
A booking widget for the
site you already have.
The widget is a drop in for your existing website. It reads your live availability and your rates, takes card payment and writes the booking straight onto your calendar. Your API key stays on your server and never reaches the browser.
- Server side proxy, so the key is never exposed
- Whitelisted routes and per address rate limits
- Takes your site styling, stays on your domain
Reservation systems
Sold as an extra on
Sold as an extra on
the site booking.
If your park runs the RV Business Tech reservation system, a cart rental can be sold as an option on the site booking itself. Pricing syncs both ways, and the cart portion of the payment can be charged to the rental company’s own account rather than the park’s.
- Two way pricing sync between the two systems
- Separate merchant accounts, so each business keeps its own money
- Server to server only, never a shared database
03
The API
Visible traffic
Calls and errors over the last twenty four hours, plus a recent activity log, so a broken integration is obvious rather than silent.
Idempotent charges
Payment calls carry an idempotency key, so a retried request cannot charge a guest twice.
Available endpoints cover availability, cart types, pricing, bookings, cards and charges. Ask us for the API reference when you book a demo and we will send it over.
Book a demo
Connect it to what you run.
Tell us what you need it to talk to and we will tell you plainly whether it does, today.