Subject Sharing


Website: https://www.earthranger.com/ 

Also known as ER2ER, DAS2DAS, or EarthRanger to EarthRanger Subject Sharing, this integration enables subject (animal or asset) data sharing through Gundi for synchronized monitoring across multiple EarthRanger instances.

 

I. Audience

  • EarthRanger Support Team.
  • Deployment Partners.

 

II. Prerequisites

Source Site

Click to Expand

Subject Group. Create a group that includes all subjects you intend to share.

Permission Set. Define a permission set that allows Gundi to read observations, sources, subjects, and subject-source assignments.

User. Create a dedicated user account (e.g., “er2er rhino collars”) for this integration. Please refer to EarthRanger's documentation or contact Support.

  • Assign the previously created permission set (e.g., “ER2ER Subject Sharing Permission”) to this user.
  • Grant this user access to the subject group containing the subjects to be shared.

Warning

Ensuring the user has the correct permissions is essential to prevent both oversharing and insufficient access. Refer to the final section of this article to verify the configurations if there is any uncertainty.

 

Authentication Token. Generate a session token for this dedicated user. Please refer to EarthRanger's documentation or contact Support.

 
 

Destination Site

Click to Expand

User and Permissions. Create a special user (e.g., “er2er from PA”) with necessary permissions to create the subject group, subjects, and observations. 

Example:

Authentication Token. Create a session token for this special user. Please refer to EarthRanger's documentation or contact Support.

 
 

 

III. Considerations

Important: Data shared between EarthRanger systems is not available immediately. Expect a delay of about 45 minutes.

 

IV. Configuring Gundi v1

Integration Requires Assistance

Self-Service integration not available yet. Requires assistance from Support.

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!

Outbound Configuration

Audience: Support Team

Go to Gundi v1.

Set up an Outbound Configuration for the EarthRanger site that will receive the data.

Use a dedicated token generated specifically for this integration. Ensure the token belongs to a user account with permissions to create subject groups, subjects, sources, and observations.

Incorrect permission configuration may cause the integration to fail, such as subjects not being properly received in the destination.
 
 

Inbound Configuration

Audience: Support Team

Go to Gundi v1.

Go to the Inbound Integrations and select Add Integration.

Follow the steps below to configure the integration:

Name: Provide an appropriate name for this connection (e.g., ER Site 1 to ER Site 2)

Organization: Select the organization that owns the data.

Type: Choose “ER2ER Subject Sharing”.

Endpoint: Source endpoint (e.g., https://your_site.pamdas.org/api/v1.0)

Token:  Authentication token at the source site.

Important: Using an incorrect token can result in sharing more data than intended. Ensure the token is linked to a dedicated user with access restricted to the specific subject group being shared with the destination.

State:  

{
   "feature_groups":[
      {
         "id":"{{string}}"
      }
   ],
   "look_back_window_hours":{{number}},
   "provider_key":"{{string}}",
   "schedule_interval_minutes":{{number}},
   "subject_additional":{{boolean}},
   "subject_group":"{{string}}"
}

Additional Guidance

Provider Key (provider_key): This value will be used as "Provider Key" in the replicated subject(s).

Subject Group (subject_group): All the replicated subject(s) will be grouped in this value in the destination site.

Feature Group (feature_groups): (Optional) Provide the feature group(s) ID to enable geo-filtering. Each of the IDs will point a specific feature (geoJSON) for filtering the replicated observations to be contained within the feature. If more than one ID is provided, the geo-filtering logic will validate if the observations are within any of the provided features.

Subject Additional (subject_additional): Whether the replicated subject(s) will include "additional" data

Look Back Window Hours (look_back_window_hours): How many hours back we will look for subjects on the source site.

Example:

{
   "feature_groups":[
      {
         "id":"76f970b9-bf3e-4946-8b6d-0c94dd55544a"
      }
   ],
   "look_back_window_hours":12,
   "provider_key":"er2er_subjects_from_sitea",
   "schedule_interval_minutes":5,
   "subject_additional":true,
   "subject_group":"ER2ER - Lions from SiteA"
}
 
 

Click Save.

 
 

Device Group

Audience: Support Team

Modify the Device Group to assign the Outbound Configuration set up in a previous step.

 
 

 

VI. Troubleshooting

Request to confirm which Subjects will be shared:
/api/v1.0/subjectgroups?include_hidden=true


Request to check whether sharing function will process or abort
/api/v1.0/subjectsources

The sharing function will abort if it cannot read this endpoint.

 

 

Continue Learning

Event Sharing

 

 

ER2ER, EarthRanger to EarthRanger, Gundi v1, Subject Sharing
Last Update: Oct 10, 2025