AzEDS REST API 6.0 for FY2021 is live now and LEAs can submit data using the URL provided below AND fiscal year as 2021:
Production REST API 6.0 URLs:
To ensure the LEA SIS is configured properly for FY21, the LEA should refer to their vendor communications, support documentation or contact vendor to setup properly.
There is no change to the key and secret assigned to each district for AzEDS REST API 6.0 for FY21.
For data elements required for the new fiscal year, please refer to the AzEDS Use Case 6.0 document on AzEDS Developers Site.
The AzEDS 6.0 User Acceptance Testing (UAT) is now available for LEAs. LEAs will use the same Key and Secret they used for AzEDS 5.0 UAT.
To request access to the AzEDS 6.0 UAT, please submit a ticket through our Self-Service Portal or email
School Finance has created a web page with guidance regarding school closures. This guidance is specific to School Finance and any questions or concerns related to this subject should be emailed to [email protected]. Questions/concerns submitted to School Finance that are not covered in our guidance, or posted elsewhere on the ADE website, may assist us in updating our guidance. The date and time of updates to this web page will be posted at the top of the page.
Effective March 19th 2020, two new integrity rules will be implemented for SPED data validations in AzEDS. This is in an ongoing effort to ensure clean data within the fiscal year, and avoid corrections of data after close of the fiscal year.
-40073 Only SPED Exit Codes may be used to exit a SPED Least Restrictive Environment (LRE).
This rule is to ensure any exit code associated with a SPED LRE must be a SPED Exit Code.
There have been previous cases where exit codes with similar exit descriptions have been reported for SPED data.
- ELL05 Transferred to a different program
- ELL06 End of school year
-40075 SPED Least Restrictive Environment (LRE) with Exit Code SPED07 must have enrollment end on same exit date.
This rule is to ensure student reported as dropped out from SPED are ending their enrollment on the same date. If enrollment continues after the SPED LRE then another exit code must be selected.
- A new enrollment may be reported at the site if the student returns.
All Integrity errors can be found on the AzEDS Portal – INTEG15 Student Data Integrity Report.)
Record Level Security is a security feature in AzEDS API that addresses the issue where one LEA can delete the records of another LEA. This issue typically occurs in a tuition out scenario where multiple LEAs are reporting data to AzEDS about students enrolled at some point in the fiscal year in the same private day school. This issue does not occur for student data reported at a school that is directly owned by the LEA.
Phase I of this feature is now complete and has been live since December 13, 2019. This phase enabled data submitted to AzEDS to be automatically tagged with the LEA owner ID as soon as the data is received by AzEDS. In order to ensure all records are tagged with ownership, it is recommended that LEAs resync or refresh (updating will not tag existing records) their data. The method to submit the data is dependent on your Student Information System (SIS). Each SIS vendor is aware that this process needs to take place, so if you have questions on what actions you need to take to get your data tagged, please contact your SIS vendor.
Phase II of this feature was tested and went live on February 21, 2020. Record-level security will now be enforced. Any attempts to update or delete records by a LEA that does not own that record will cause the SIS to receive an error from AzEDS.
If you have students from your LEA that are tuitioned-out to private day schools, it is highly recommended that you complete the resync or refresh of your data to get your records tagged as this will protect them from being deleted by another LEA when they try to resync their data.
The AzEDS REST API Release 6.0 with Ed-Fi ODS API 3.3 is now available in the sandbox environment.
The AzEDS team published the following for all AzEDS SIS Vendors.
Sandbox 6.0 Release Notes and
Use Case 6.0.
Version 6.0 of the REST API is available for SIS vendors in the sandbox environment using the following URLs:
Please let us know if you have any questions or encounter any issues.
Thank you for your continued efforts.
Dear LEAs and Vendors,
LEAs and SIS vendors must submit data using the appropriate URL AND fiscal year in the URL listed below:
Production REST API URLs for LEA’s:
To ensure the LEA SIS is configured properly for FY20, the LEA should refer to their vendor communications, support documentation or vendor contact to setup properly.
There is no change to the key and secret assigned to each district for AzEDS access.
For data elements required for the new fiscal year, please refer to the AzEDS Use Case 5.0 document on AzEDS Developers Site.
The API 5.0 External UAT is now available for LEA’s. LEA’s will use the same Key and Secret they used for API 4.0 External UAT.
To request access to the API 5.0 UAT, please submit a ticket through our Self-Service Portal or email