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
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.
The AzEDS database server experienced an issue yesterday evening around 4pm. This impacted the API, AzEDS Portal reports and the nightly Integrity and ACE processes. The server issue has been resolved. Our initial analysis of the database that receives data from LEAs does not show any data loss. We encourage you to continue your data submissions as usual.
Due to the outage the AzEDS Integrity and ACE nightly processes did not run last night. They will run today at 6pm as scheduled.
LEAs and Vendors,
There is a known issue involving Private Day School, Residential Treatment Center, and Head Start Program calendars being deleted. We are working with the related SIS vendors to correct this issue. We will post an update once this issue is resolved.
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