Build an incremental synchronization pipeline from PowerSchool to an Ed-Fi ODS using the PowerSchool Changed Records API

Steps

1. Enable the PowerSchool Changed Records feature in the plugin configuration; it tracks inserts, updates, and deletes per table using an internal change sequence number.
2. On first run, call GET /ws/v1/plugin/changedrecords/table/<tablename>?sinceVersion=0 to retrieve all existing records and note the returned maxVersion in the response envelope.
3. On subsequent runs, use sinceVersion=<maxVersion> from the prior response to receive only changed records; PowerSchool returns the changed rows with a changeType field ('INSERT', 'UPDATE', 'DELETE').
4. Map changed PowerSchool rows to Ed-Fi resource payloads using your field mapping configuration; for DELETE records, issue DELETE requests to the corresponding Ed-Fi endpoint using the stored natural key.
5. Persist the maxVersion cursor durably after each successful batch to survive restarts; if the pipeline crashes mid-batch, replay from the last committed cursor.
6. Implement a reconciliation check weekly: compare PowerSchool record counts against Ed-Fi counts per school to catch any records missed due to replication gaps or API errors.