What is Gundi?
Gundi is a free, open-source platform built by EarthRanger together with WPS and WCS to make data sharing easier for conservation teams. It helps connect sensor data with conservation software so teams can access the information they need to make better, faster decisions.
Our goal is simple: connect technologies and people so conservation areas have reliable access to the data and insights they need to take effective action.
How can I integrate our technology with Gundi?
If you are a conservation practitioner who has acquired, or is considering acquiring, a specific technology for your work, we recommend reviewing our list of supported devices. If your technology is not listed, several integration options are available, depending on the capabilities of the relevant devices or services.
Quick Overview of Integration Options
Quick Overview of Integration Options
- Integrate via supported technologies.
- Integrate via Webhook (real-time data push).
- Integrate via Gundi's API.
- Integrate via a Custom Integration (scheduled data pulls using the manufacturer’s API).
This article focuses on Webhooks, Gundi’s API, and custom Gundi integrations. Technologies already supported are documented separately in their respective guides.
1. Options to send data to Gundi for transformation, processing, and delivery
Objective: Establish a Gundi inbound connection.
1.1 Gundi Webhook 
- For sources with support for webhooks, this is often the simplest integration method.
- Depending on the complexity and structure of the data, some integrations can be handled through configuration alone, while others may require coordination with our development team.
1.2 Gundi API 
- Gundi's API gives developers full control over their integration, and typically requires minimal coordination with our team.
- Online documentation here.
1.3 Custom Gundi Integrations 
- When a system cannot push data, our team can build a Connector to pull data from that system's API.
- These integrations are often developed with a scheduled polling mechanism (e.g., every 5–30 minutes).
- This option requires coordination with our development team. Timelines will depend on implementation complexity and team availability.
2. Options to receive data from Gundi
Objective: Establish a Gundi outbound connection.
2.1 Custom Gundi Integrations
- Our team can build a custom Connector to push data to your system.
- The process involves understanding your system, user requirements, and API.
3. Collaboration
Once you have selected your preferred approach, please contact our team and share relevant details, including:
- Technology name and description
- Desired outcomes
- Technical point of contact
- Relevant device and/or integration specifications
How long does it take to integrate a device?
If the device is already included in our list of supported devices, integration is typically completed within one day or less.
For devices not yet supported, the timeline varies depending on complexity, data format, documentation quality, and vendor collaboration. In these cases, implementation can range from a few days to several months.
How does Gundi handle data privacy?
Gundi follows the EarthRanger sharing policy, which you can review here:
Additionally, users must review and accept Gundi's End User License Agreement (EULA):