Partner program

There is no sign-up form and no self-service listing. You write to us, and part of what follows is done by hand by Grondia staff. This page says which part.

There are two ways in, because products connect in two directions (see What you can build). Both end at the same place: a pilot with one campground, a listing in the Grondia App Store, and a support contact.

You build on our API

1. Apply
2. Sandbox
3. Build
4. Review

We build on your API

1. Send your API docs
2. Test account or hardware
3. Adapter, if Grondia builds it

Both lead to:

1. Pilot
2. App Store listing
3. Go live and support

You build on our API

This is the path for software that reads or writes campground data: channel managers, accounting, CRM and guest messaging, tills.

1. Apply.

   Write to Felix, felix@grondia.com, or to Siro, siro@grondia.com. Say what your product does, which data it needs (bookings, availability, invoices, events, and personal data if it cannot work without it) and, if you have one, which campground wants to use it. A few sentences are enough. Felix or Siro tell you what happens next. What you can build helps to say which of the two paths you are on.

2. Get a sandbox.

   Grondia staff set it up. The sandbox is one shared test campground with a read-only key; the Quickstart says what it contains. You cannot try writes, webhooks or the till endpoints in it, and there is no separate write sandbox today. If you need to try them, tell Felix or Siro what you need.

3. Build.

   Work from the Core concepts, the Credentials page, the recipe for your kind of product in What you can build and the API reference. The reference is generated from the OpenAPI document the production API serves. A coding agent can read /llms.txt on this site. Write to the same two addresses with questions while you build.

4. Check your product against the review list.

   Before you ask for a review, check that your product:

   • keeps each campground’s key apart, on your server, and out of any browser and repository;
   • asks for the scopes it uses and no more;
   • stops on 401 and 403 instead of retrying them (Credentials, Errors);
   • works when guest names and emails come back redacted (Credentials, Personal data);
   • follows next through a list instead of assuming one page (Syncing changes);
   • stays under the key’s rate limit, 1000 requests per rolling hour by default (Rate limits);
   • sends an Idempotency-Key header on a write it may repeat, so a retry replays the first answer instead of creating a second booking (Retrying safely);
   • checks the X-Grondia-Signature header of every webhook delivery (how), and fetches the booking for details, because webhook payloads carry no guest data;
   • copes with a pending booking that nobody pays: Grondia releases it after about 30 minutes (Core concepts).

   When you have checked these, write to Felix or Siro and ask for a review. Felix or Siro tell you what happens next.

5. Pilot with one campground.

   The first real use is with one campground that is already on Grondia and wants your product. It needs the API module. Its administrator creates the key in the admin. For scopes the admin does not offer, a key with those scopes on the campground’s live account is created on request (Credentials). The administrator can see the key’s recent requests, which makes the first days easy to follow. Write to Felix or Siro to set a pilot up. Before this first production key you sign short API terms of use, which also cover how you handle the guests’ personal data; the sandbox needs no signature.

6. App Store listing.

   Send the items in What to send. Grondia adds the card for your product; you cannot add it yourself. How a campground connects through the card depends on what Grondia builds for it (see What the card does). Before a card exists, a campground can already use your product with its API key.

7. Go live and support.

   Once the card is added, campgrounds can find it in the App Store in their admin. Keep the support contact you gave us reachable: operators need someone to write to about your product. Grondia’s policy is a minimum of 12 months’ notice before an API version’s sunset date (Versioning). The Changelog shows the current API version.

We build on your API

This is the path for devices and services that act on the campground: door locks, entry barriers, EV chargers. Grondia can write an adapter to your API, if it decides to build one. You do not apply for a key; you send us your API documentation and a way to test it. Device makers lists what an adapter needs from your API and what to do next.

From the pilot on, the path is the same as above: one campground, the App Store listing, then go live and support.

What to send for the App Store listing

A listing is a card in the App Store in each operator’s admin. Today it is a code change by Grondia, so it ships with a normal Grondia release, not the moment you send the items. Send:

• Name, as it should read on the card.
• Tagline, one line. It sits under the name on the card.
• Description, one paragraph, in German, French, Italian and English. The operator reads it when they open your card.
• What the operator needs to have ready, as a short list. The card shows it as a “What you need” checklist, for example an account with you and the scopes to tick when creating your key.
• Category, the part of the App Store where the card should sit.
• Logo, as SVG. Today’s cards show a simple icon from a fixed set, not a vendor logo, so your logo may not appear on the card.
• Support contact, a name and an email address for questions about your product.

What the card does

What an operator can do from a card depends on what Grondia builds for it. Today every card in the App Store opens a panel that Grondia built, for example a form for a lock’s token. A card with no panel behind it shows only an upsell message. For a product that works with an API key, the operator creates the key in the admin (Credentials) and gives it to you; the description and the “What you need” list can tell them how. Anything more than that, such as a form on the card, is Grondia work that you settle with Felix or Siro.

Ask us

Applications, sandboxes, reviews, pilots and listings all start with an email. Write to Felix, felix@grondia.com, or to Siro, siro@grondia.com.