Receiving data from TrapTagger

Website: https://wildeyeconservation.org/traptagger/ 

Prerequisites

TrapTagger

You will need:

  • TrapTagger Account.

Gundi

You will need:

  • API Key (Steps in this guide).

EarthRanger

Click to Expand

1. Create an Integration User

In EarthRanger, create a dedicated user account (e.g., traptagger_integration) for this integration.

2. Create Authentication Token

Create a long-lived token for the user created in Step 1. This token will be used for authentication.

3. Configure Event Type and Schema

Ensure that the required event type and schema exist in EarthRanger:

4. Assign Permissions

Edit the user created in Step 1 and assign the necessary permissions to post event data. Be sure to include permission for the Event Category that contains the event type (from Step 3).

Please refer to EarthRanger's documentation or contact Support.

 
 

Configuration

GUIDES

 

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., “Trackers - 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.

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., "traptagger")

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.

Do you need to use different Event Types depending on the species detected?
If so, just reach out to the Gundi Team to set up the “Route Configuration.”

 

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.

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.

 

Camera Trap, Push Integration, Data Provider
Feb 26, 2026