This integration imports student and parent demographics data from Skyward into SameGoal on a nightly basis. Demographics information appears on each student's "Details" tab in SameGoal, and auto-copies into documents as they are created for each student.
Steps
To setup demographics integration with Skyward Qmlativ:Create an Integration Access Record:
- Navigate to Administrative Access > API > Integration.
- Select the Integration with Product Name SameGoal Demographics.
- Select the Integration Accesses tab, and then click Add Integration Access.
- Set a Name, Key, and Authentication Type for the Integration Access.
- Name can be whatever you choose.
- Access defaults to expire a year after creation date; you may extend or even delete this expiration.
- For Custom API Entities, select your District Entity and any entity you wish to include in integration.
- Authentication type should be OAuth 2.0.
- After the Integration Access is created, SameGoal will be able to generate a secret to pair with this key.
- Email tier2help@samegoal.com from your district email with subject “Complete SameGoal Demographics Integration” (no additional information needed).
- Our technical team will verify that the Integration Access record has been created for your district.
- Our technical team will generate the required secret for this Integration Access record. Full API credential information for this integration will then appear in SameGoal. To view/verify this information:
- Login to SameGoal as an administrative user.
- Visit Settings (left menu) > District Information.
- Under STUDENT INFORMATION SYSTEM INTEGRATION, locate Skyward Qmlativ.
- The "add Nightly Demographics" section will be expanded and contain:
- API Base URL, Client Key and Client Secret
- You will receive a confirmation reply email once SameGoal setup is complete.
- This integration runs nightly. Students should appear from Skyward the following morning in this environment.
- SameGoal’s demographics integration import processing includes all student enrollments where the student withdrew within the past year, as well as all current or upcoming enrollments for the current school year. In Skyward Qmaltiv, this data is stored in the Student Profile tab under Enrollment → Entity Year.
- After retrieving these enrollments, we apply the following post-processing rules:
- Ignore all enrollments identified as cross-entity course enrollments (Where WithdrawalCode = 'CECS'). With CECS, a student can be enrolled in a course at another school within the district and still have all their grades, attendance, and information housed at their home campus. We wish to ignore these enrollments because we care about the enrollments with their home campus only and don't want data from other entities to interfere with our enrollment status determination.
- If a student has an enrollment effective as of today, we classify the student as ENROLLED.
- If a student has an enrollment effective at a future date:
- If there is no past enrollment for the student, we classify them as PRE-ENROLLED.
- If there is a past enrollment, we classify them as ENROLLED. This is primarily done to ensure that a student remains ‘ENROLLED’ during summer breaks.
- If the student has no current or future enrollment, they are either GRADUATED or INACTIVE:
- If the Withdrawal Code for their most recent past enrollment is '01' (following TEA standards), we classify them as GRADUATED.
- In all other cases, we classify them as INACTIVE.
- Currently, we do not support enrollment status codes such as 'TRANSFERRED', 'DROPPED_OUT', or 'HISTORICAL_IDLE'.