Implementation Details

Data Source

InfiniteCampus data syncing can either use their OneRoster API or an SFTP connection. Ensure the proper configuration matching the method is setup in your source.

Note: When leveraging the Infinite Campus v1.2 OneRoster API, records (e.g. users, classes, enrollments) may not be visible unless they are associated with the current school year. For example, if new students are added to Infinite Campus for the 2026-2027 school year, but the school is currently in session for the 2025-2026 school year, then Edlink may not have access to those student records until the rollover to the next school year.

Data "Version"

Each InfiniteCampus instance has a "version" of data that we are trying to access (e.g. 2024-2025, 2025-2026, etc.). The user that is trying to sync the data should have permissions to access only a single version of the data. If we attempt to read data and find no districts in the matching "version", the sync will fail.

Custom Mappings

An InfiniteCampus source can be configured within Edlink to use custom mappings for:

• races
• gender_identities
• grade_levels
• disabilities
• food_service_program_eligibility
• agent_relationships

Custom Field Mapping