[Testing and Accommodations in SIRAS] [TOMS API for SIRAS] [SIRAS TOMS Export FAQ] [Exporting SBAC/ELPAC from SIRAS for TOMS]
How does it work?
SIRAS has the capability of sending Test Settings data directly to TOMS for one student at a time.
This will not replace the need for batch file uploads though.
- Only one set of credentials are needed, these are the District credentials already entered into your District's SIS system.
- The District Attending sets those credentials into the /Tools/SIRAS Admin/TOMS API area.
Data for one student can be sent in two ways:
- When a Meeting is Finalized, there will be a confirmation checkbox indicating to send the test settings data.
- From the Student Profile / Assessments page, staff may connect, review data as it exists in TOMS, and trigger an update manually.
We have the API working now, should we stop doing bulk uploads?
NO, do not stop doing bulk uploads! The API method at this time will never fully populate TOMS when TOMS erases all accommodations each academic year.
What does it send to TOMS?
Accommodations and Designated Supports (Test Settings) are sent as a full replacement.
This is the same information the SIRAS TOMS Export.
The accommodations that are sent are the ones that the parent most recently agreed to.
If a meeting is finalized and there is no parental agreement or partial agreement, then the accommodations won't automatically transfer to the current data.
This prevents accommodations not agreed to from being sent to TOMS.
What kinds of errors might occur when sending data?
When sending accommodations data to TOMS via the API, there are several categories of errors that may occur.
If the accommodations data was sent to TOMS as part of finalizing a meeting, and there are errors, those errors will become visible at the top of the MIS Summary.
There are a few main types of errors:
- Data Validation errors: invalid combinations of test settings were selected.
- LEA ownership errors: the LEA does not have ownership of the student record in ETS, or the student ID does not exist.
- Invalid Credentials: the district's API credentials may have expired or have been input incorrectly
What happens when there are errors?
- Errors when connecting or sending will be displayed at the top of the page you are on.
- Error follow ups for admins to review with providers will be posted on the MIS page.
- Depending on the error type, the data remains in a queue for SIRAS to re-process nightly.
- The error may manually be deleted to remove it from the MIS Summary.
What are TOMS API Keys?
This is the username/password information already entered into your SIS that allows your SIS and now SIRAS to send data directly to TOMS for one student at a time.
If your district applies for new credentials, make sure the new credentials are entered into both your SIS and SIRAS.
Can we send all our district data in batch with the TOMS?
At this time no.
How get instructions for accessing API Keys:
How do I enter our TOMS API credentials into SIRAS?
- For full instructions, click here:
How can I tell if the TOMS API connection in SIRAS is configured correctly?
- Login to SIRAS at your District level.
- Go to: /Tools/SIRAS Admin
- Select the 'TOMS API Credentials' Tab
- Click 'Test Connection' to see if the connection is successful.
- Look for the 'Successfully authorized' message at the top of the page.
- Also look for the green check mark next to the 'Test Connection' button
- See screenshots below
