Ceres Wild

Website: https://cerestag.com/ 

Prerequisites

Ceres Wild

You will need:

  • Ceres account.
  • Ceres Wild tags.  Important: We have a different guide for Ceres Ranch and Ceres Rancher tags.

Gundi

User will need:

  • An account in the legacy Gundi portal (v1).  Link: https://cdip-prod01.pamdas.org/. Ask user to click “Register” and to notify you when it has been done. 
  • User has been added to a Gundi Organization.

Data Delivery

EarthRanger

Movement Data

To send movement data to EarthRanger, you will need:

Please refer to EarthRanger's documentation or contact Support.

Please refer to EarthRanger's documentation or contact Support.

To send event data to EarthRanger, you will need:

Event Data

Event Type “ceres_alert” has been created in EarthRanger. 

An auth token has been created in EarthRanger for this integration. The EarthRanger user owning the token has been granted permissions to the Event Category hosting the “ceres_alert” event type.

 
 

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.

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

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.

Next Steps

After logging in to the Ceres Portal, the user should select “EarthRanger” as their software. The portal will then prompt them to sign in to the Gundi Portal.

Once logged in, they will be redirected back to the Ceres Portal, where they will be asked to choose a connection. In most cases, only one integration will be available, which they should select.

Characteristics

  • This integration will trigger an event or alert whenever the collar detects either no activity or unusually high activity.
  • 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.

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.

Additional Resources

Internal Documentation

https://allenai.atlassian.net/wiki/spaces/CDIP/pages/27007680518/Ceres 

 
 

 

Animal Tracking, Movement Data, Push Integration, Data Provider, Gundi v1
Jan 20 14, 2026