You build on our API
Software that reads or writes campground data: channel managers and booking portals, accounting and ERP, guest messaging and CRM, shop and restaurant tills and Zapier. The campground gives you an API key; you call Grondia and receive webhooks.
We build on your API
Devices and services that act on the campground: door locks, barriers, EV chargers. Grondia writes the adapter to your API, the way its existing lock, barrier and charger integrations work. Device makers
Not sure which one you are? What you can build sorts it out in two minutes.
Understand the model
Campground, pitch, booking, guest and invoice: the few nouns the API is made of, in one picture, and the life of a booking in another. Core concepts
First call
Get a sandbox key, list bookings with one request, read the answer. Examples in curl, Python and Node. Quickstart
React to events
Grondia tells your endpoint when a booking is created, changed or cancelled, when a guest checks in or out and when an invoice is issued. Each delivery is signed. Webhooks, then Syncing changes
Get listed
Pilot your integration with one campground. After a review, Grondia adds it to the App Store in the operator’s admin, where campgrounds find and switch on integrations. Partner program
The guides cover what every integration needs: errors, retrying safely, rate limits, dates, times and money, personal data and versioning. The German campground words you meet in the data, such as Stellplatz and Kurtaxe, are in the Glossary.
Sandboxes, keys with more scopes, access to personal data, reviews, pilots and App Store listings all start with an email. Write to Felix, felix@grondia.com, or to Siro, siro@grondia.com.
