Application Programming Interfaces (APIs) Extend Functionality for Your Platform

APIs are the smart way for applications to get the information they need, when they need it. They allow for easy, well-defined program interoperability.

EDmin is constantly working to extend interoperability in this rapidly evolving area.

EDmin partners can quickly grow marketshare by using features from our flexible platform, such as:

Content Management API

  • This web service API allows access to user data (i.e., content, collections, standards, etc.) via a defined profile.
  • Federated search technology provides precise access to data.

Correlation Web Services API

  • EdGate Correlation Services, a division of EDmin, provides publishers, school districts and content providers with a number of delivery methods for correlation data.
  • Via remote access, correlation data hosted by EdGate can be seamlessly integrated into an application or web site in real-time.

Roster Data API

  • The School Interoperability Framework (SIF) 2.2 Data Model is used.
  • Roster data is received and sent between applications based on the publish/subscribe model.
  • Data is shared through a series of standardized data objects defined by the SIF specification.
  • Retrieval and submission of roster data in XML format is facilitated by more than 30 API methods.

Assessment Data API

  • SIF 2.2 Assessment Working Group data objects are used to access (subscribe to) assessment related data.
  • Assessment definition information is retrieved, as well as student response and score data.
  • More than 20 methods facilitate the retrieval and submission of data in XML format.

On-line Test API

  • Applications can request a list of tests assigned for online testing.
  • Test-window parameters are provided, as well as assigned students.
  • Applications can launch the test for a student using Single Sign-on.


  • Three layers of content license management support interoperability across EDmin and third-party applications:
    • content license control that defines what content is associated with a user within a single instance implementation
    • authorization / single sign-on with different SIF “zones” and agent keys
    • account management for integrations

Single Sign-On API

  • A two-phased approach uses an authentication engine and authorization to ensure security.
  • The standard for user credentials is based on a globally unique identifier (GUID).
  • Access is role-based.
  • Applications can authenticate and provide access to specific areas and functions, reducing navigation steps.