Website: https://www.wpswatch.org 

The Gundi Integration allows wpsWatch to post images to one or more EarthRanger sites, or other outbound destinations. To configure an integration, you will need:

• Access to a Workspace in Gundi. This can be requested by contacting our Support Team.
• When EarthRanger is the destination:
  • An existing Destination in Gundi, or
  • Admin access to the EarthRanger instance.
• System Admin access to wpsWatch (WPS staff only)

Integration Process Summary

EarthRanger

• Update the Camera Trap Event Type schema in EarthRanger
• Create a user in EarthRanger with permissions to post Events and a long-lived token for that user. Read more .

Gundi

• Create a Connection in Gundi.

wpsWatch

• Edit the integration in the wpsWatch site to enable the Gundi integration.
• Update the alert configuration(s) in wpsWatch to send the alerts to Gundi.
• Validations.

Configuration

GUIDES

Gundi v2 Push Integration Configuration Steps

1. Gundi Connection Settings

1.1 Visit our portal. 

1.2 Click on Create Connection.

1.3 Select your technology.

1.4 Select your Workspace.

1.5 Enter a name for this Connection (e.g., “TechnologyName - AreaName”)

1.6 Click Next.

1.7 Select a Destination. Please consult our guides.

1.8 Visit the Connection you created during this process, and copy the API key. To do this, go to the Connection's Provider tab, find the API key field, and click the copy icon. 

1.9 Send the API key and your account identifier to your contact at the data source provider, asking them to set up an integration with Gundi (URL: https://sensors.api.gundiservice.org/v2/observations/). Alternatively, configure the API key directly in their system if you have access to those settings.

Suggested Contacts:

• Tom Coetzee (tom.coetzee@wildlifeprotectionsolutions.org)

WPS Staff will help you with the following actions:

• Edit the Integrations in the wpsWatch site to enable the Gundi integration with the URL and API Key.
• Update the alert configuration(s) in wpsWatch to send the alerts to Gundi.
• Validations.

2. Configurations in wpsWatch

2.1 Edit your integrations in wpsWatch.

1. Log into wpsWatch as a System Admin and navigate to Site Details.
2. Go to Actions > Edit Integrations
3. Check Gundi In the Outbound Integrations section
4. The Base URL should automatically be populated with the appropriate Gundi URL:
   https://sensors.api.gundiservice.org/v2/events/ (for Production)
5. In the API Key field, enter the API Key you copied from Gundi.
6. Click Save to enable the integration

2.2 Update the alert configuration(s) in wpsWatch to send the alerts to Gundi

1. From Site Details, go to Actions > Configure Alerts
2. Depending on the conditions where you want to send alerts to EarthRanger, you can either create a new alert configuration or edit an existing one.
3. Specify whatever criteria you want to trigger the alerts, and check the Send Notification to Gundi box in the routing options
4. Click Save.

2.3 Validation

When a photo is tagged in wpsWatch (by the AI or manually) that meets the criteria of the alert configuration you created above, wpsWatch sends the event to Gundi. Confirm delivery in both Gundi and EarthRanger:

In Gundi (optional):

• The first time a photo comes in, a new source appears on the Sources tab, along with a Source Created line in the logs.
• A new Observation Delivered event appears in the logs for each photo sent, followed by a second log line for attaching the image to the ER event.

In the destination EarthRanger site:

• You should see a new camera trap event. With the V2 integration, the event now includes the following additions:
  • The event name includes the deployment name and a list of the unique tags from the photo.
  • An array of tag information, including a count of each tag.
  • The battery level, if it is available in wpsWatch.
  • A unique list of tags stored on the event. This list is not displayed in the ER UI but is included in exported events for reporting purposes.

Considerations

• This integration does not currently include event updates.  If a ‘rhino’ tag is added to the photo in wpsWatch, that tag won’t be added to the event in ER. 
• An integration with Cmore is in the roadmap, but not yet available.
• The array of tags isn’t reportable in ER, so there’s a separate Tags field that contains a comma-delimited list of tags that can be used for reporting. It isn’t displayed in the UI for the event, but it is included in exports.

Characteristics

• This integration is classified as a “Push” type, meaning wpsWatch services send data to Gundi as soon as they process the images. Gundi then immediately attempts to forward the image and metadata to the destination specified in the Connection.

Camera Trap, Push Integration, Data Provider
Mar 10, 2026