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

III. Considerations

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

Important: ER2ER shares subjects and their positions, not sources or source assignments. The first time the destination receives a device, it creates the source and one assignment to that subject with no end date, and never changes it afterwards. If a device is moved to another subject on the source site, the move is not copied, and its positions appear under the first subject. After configuring the integration, especially with a long look back window, compare the source assignments on the destination with the source site. Correct them in the destination's admin where a device was used by more than one subject, and repeat this check whenever a device is moved to a different subject on the source site.

IV. Configuring Gundi v1

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

{
   "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"
}

V. Next Steps

VI. Troubleshooting

Notes:

• Sources will not retain their original names between the source and destination sites. In the destination site, each Source will be named using the Source ID from the source site. The External ID of each destination source is the source site's internal source ID, not the original device ID.
• Positions appear under the wrong subject on the destination: source assignments are not copied between sites. Compare the destination's assignments with the source site. In the destination's admin, edit the existing assignment's start and end dates and add an assignment for the other subject.
• To confirm which Subjects are being shared, use:
  GET /api/v1.0/subjectgroups?include_hidden=true

Example:

curl https://[site].pamdas.org/api/v1.0/subjectgroups --url-query include_hidden=true --oauth2-bearer [token] | jq

• To verify whether the sharing process will proceed or stop, check:
  GET /api/v1.0/subjectsources - the sharing function will abort if this endpoint cannot be read.

Continue Learning

Event Sharing

ER2ER, EarthRanger to EarthRanger, Gundi v1, Subject Sharing
Oct 10, 2025

Other ER2ER