Ideas

To have a report that shows exam entries from all schools on central. We manage the entries centrally and to be able to see on central as a overview would be amazing. Would save time on logging into each school to check.

Dear iSAM Support Team, We are writing to request an enhancement to the Retrieves all non-archived absence codes endpoint: /api/registration/absencecodes. Currently, this endpoint is missing several vital fields that are available within the iSAMS...

Currently, Wonde can switch off lesson by lesson to the DfE at their end, but we have no control what is going out. We would like it control it at our end as the inclusion of lesson by lesson has caused discrepancies in the live data the DFE/LA is...

Summary: While integrating with the iSAMS API, we identified inconsistencies and limitations in the Registration - Registration Status endpoints that hinder reliable data retrieval and system interoperability. This proposal outlines actionable enh...

Dear iSAMS Support Team, We urgently require assistance resolving persistent 500 errors when using the POST /api/medical/students/{schoolId}/documents endpoint, despite following the "Try It" example and validating all parameters against live syst...

We propose an enhancement to the iSAMS REST API to include endpoints for accessing Audit Logs associated with Student and HR records. Currently, while audit logs are visible within the iSAMS interface, the inability to retrieve this data programma...

Affected Resource: PATCH /api/medical/students/{schoolId}/conditions/{conditionId} Current Documentation Problem Statement: Developers cannot reliably update student medical conditions due to: Unclear required JSON format (RFC 6902 vs custom struc...

We are reporting a validation discrepancy identified in the "[POST] Create Medical Condition for Student" and "[PATCH] Update Medical Condition for Student" REST API endpoints. The current logic erroneously validates the dateReviewed field against...

The "GET" request for Pastoral (Wellbeing) Concerns requires the concern {id} as an input parameter, as well as the student's {schoolId}. There is currently no endpoint to list concerns by student, and so it is not possible to know the concern {id...

The NCYearCode from the pupil profile needs to pull through.