ICUServer

Website: https://www.icuserver.com/ 

Prerequisites

ICU Server

You will need:

  • An account with them.

Gundi

You will need:

  • Access to Gundi's legacy portal (v1)
  • An API Key (steps below)
  • An Integration UUID

Destination

You will need:

  • Credentials or an authentication token to access the delivery system.
  • A Camera Trap event type (cameratrap_rep).

Configuration

 

Integration Requires Assistance

Self-Service integration not available yet, please contact our Support Team.

This integration requires assistance from our support team for setup and configuration. Please contact our support team at support@earthranger.com and we’ll guide you through the process to ensure everything is set up correctly.

We are actively working to make this integration self-service in the future. Stay tuned for updates!

GUIDES

Gundi Connection Settings

1. Go to Gundi v1.

2. Create an Outbound Integration

  • Use a token tied to the Gundi Service Account permission set.

3. Create an Inbound Integration

Go to the Inbound Integrations and select Add Integration.

Follow the steps below to configure the integration.

Name: Enter a suitable name (e.g., "Trackers - AreaName")

Owner:  Select the integration's owner

Type: Select your technology

Provider Key:  Leave empty. Gundi will automatically give it a name.

Default Device Group: Leave empty. Gundi will automatically create a default group.

Endpoint:  Leave empty

Token:  Leave empty

Login/Password:  Leave empty

Click Save

4. Configure the Default Device Group

 Configure the Device Group with the Outbound Configuration created for this connection.

5. Share the API Key or Configure it in your data source system

Visit the Inbound Configuration you created during this process, and copy the Gundi API key.

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://cdip-api-prod01.pamdas.org/positions/). Alternatively, configure the API key directly in their system if you have access to those settings.

Suggested Contacts:

2. EarthRanger Settings

The following configurations are optional:

2.1. Select the data you want to see in the map.

2.1.1 Log in to EarthRanger as an admin (site.pamdas.org/admin).
2.1.2 Go to Source Providers.
2.1.3 Select the Source Provider created for this integration (e.g., "icu")

The “Source Provider” is automatically created after Gundi successfully retrieves data from this integration and pushes it to EarthRanger. If you don't find it, please ensure your Connection includes a Destination, and review the Connection Activity Logs for additional details. You should see some records mentioning that Gundi successfully delivered data to EarthRanger.
Important Note:  The integration might take 5 minutes to run. Please verify your connection after this period.

2.1.4 Click on Subject Details Configuration.
2.1.5 Configure the additional information you would like to see on the map.

2.2 Assign your Subjects to a Subject Group.

2.3 Rename your Subjects

Please refer to EarthRanger's documentation or contact Support.

Note on Latency

The time it takes for data to appear in your destination system depends on several factors, such as latency introduced by the source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data at scheduled intervals (approximately every 5 minutes).

If data is not available in your system after this interval, please check the source of the data for its availability. If the issue persists, contact our Support team for assistance.

 

Characteristics

This is a "Push" type integration, meaning your data provider sends data to Gundi on their own schedule (for example, immediately or every 5 minutes), and Gundi then forwards it right away to the destination specified in your Connection.

Only fresh data will be processed by Gundi, but a request can be made to the data provider for historic data.

 

 

Data Provider,  Camera Trap, Gundi v1, Push Integration
March 4, 2026