xPress API
Why choose an xPress API?
Simple
Using modern technologies, connect multiple apps whether they are mobile, local or hosted in the cloud
Secure
Using REST, oAuth and internet grade security, xPress APIs are an open standard and help avoid vendor lock-in!
Scalable & Standard
Using open standards, helps you avoid vendor lock-in. It can also scale with you as you grow your IT functionality.
What are the benefits of using xPress?
OPEN STANDARDS
- xPress usage supports educators in implementing technology-rich learning experiences while ensuring student’s privacy is not compromised
- xPress enables Districts to maintain control of their data – no ‘handing over’ control to others
TECHNICAL
- xPress is encrypted to prevent eavesdroppers
- xPress can control who may get what ‘chunks’ of data and how they get it
- xPress allows Data Providers to restrict data access at the field level
- xPress provides encryption on both ends of, as well as along, the ‘wire’
Districts & States… stay in control of your data.
Benefits:
- makes it easier for you to connect disparate systems and share common data
- increases the opportunities for educators, learners and parents to access and utilize data
- reduces the administration burden by sharing data, rather than having to key in multiple times
- improves data quality
xPress APIs are developed using open standards and contemporary technologies, therefore opening the marketplace to innovation and allowing users to select ‘best of breed’ applications to meet their requirements. By using modern technologies (like REST and OAuth), xPress APIs embody simplicity by enabling direct communication among systems.
xPress APIs can be developed by vendors (or your own IT department) but are administered by you. With ‘permission only’ access, only authorized personnel have access to the shared data, which is encrypted and sent securely. xPress APIs rely heavily on existing Internet grade security, this includes the use of TLS (HTTPS) to prevent the reading of intercepted messages.
There are currently seventy objects from which solutions (xPress APIs) can be designed and built. Anyone can start to build a product or service based on these objects to provide the marketplace with options that go beyond any single xPress API. The two solutions currently available are Student Record Exchange and Roster, although the Access 4 Learning (A4L) Community are developing more use cases for release in the near future.
Need a quick 101?
Check out these resources below:
- If you are not familiar with APIs, check out this video ‘What is an API?‘
- If you are not familiar with REST, check out this tutorial ‘What is REST?’.
Please note, we are not endorsing any company or product by linking to these videos.
In Use LEA xPress Roster RFP Example
The goal of the [insert project name here] project is the creation of a new [insert description] that supports the latest certified version of the SIF Specification and which will allow for the integration of current data from multiple source systems into a single structure. The [insert name of project] project will perform all inter-system data transfers (with internal and external agencies) and application integration functions for [insert function].
The [insert application/solution/etc.] must be certified to the most recent version of the xPress Roster [confirm whether Consumer or Provider] Certification Program, which enable school districts software management systems to communicate roster information with each other.
In Use SEA SIF RFP Example
To assist in the implementation of the state reporting systems required pursuant to [project/legislative/ etc. charge], the Department shall contract for the creation of, and implement, a state-wide data-sharing system that is based on the xPress Roster API. After the state-wide data-sharing system is implemented, each school district may, but is not required to, participate in the state-wide data-sharing system by using a data system that is certified with the Access 4 Learning (A4L) Community.
All technology systems used by the Department of Education and by local K-12 schools and districts shall be xPress Roster Certified. Alternative systems may be used if the alternative system is compliant and all data sets required by the Department of Education are provided to the department in acceptable, real-time format. Schools and districts may use alternative compliant systems if an alternative system is needed because of cost, efficiency, or a need for additional software features.
In Use Policy SIF Legislative Language
Any state and/or federal funds utilized in the development and implementation of student record systems, local, regional and state educational entities shall construct systems to contain the following elements and comply with the following standards and compliance capabilities:
- UtilizeExtensibleMark-upLanguage(XML),whichdefinescommondataformatsusedduring communication between disparate systems;
- Certify to the most recent version of xPress Roster Certification, which enable school district software management systems to communicate with each other; and
- Utilize defined state data codes to ensure consistent reporting from school districts (i.e. course identifiers, teacher certification, etc.).
By the [insert 20XX-20XX] school year, any state or federally funded student information systems and any instructional management system used by school districts and the state shall comply with the Extensible Mark-up Language (XML), standards and xPress Roster Certification, or any updated versions of the specifications.
API Developers… Develop once, use many times.
Benefits:
- Enables vendor application to seamlessly integrate with other applications
- Development and maintenance of one interface, rather than a bespoke solution for each customer
- Data exchange is secure and processed in a timely manner
The xPress API suite embodies simplicity in its design by using contemporary technologies like REST, JSON and OAuth, enabling direct communication among systems (middleware is optional) and representing commonly used data in a straightforward manner. (If you are not familiar with REST, check out this tutorial ‘What is REST?’.)
Most developers will immediately grasp the concepts and implementation because xPress APIs look and act just like other modern APIs.
In order to ensure interoperability and fit with marketplace needs, xPress API solutions must support the creation of tokens through Password Grant.
- Tokens allow applications to submit credentials for synchronizing data.
- Tokens require a responsible user’s permission, which gives them the ability to give the indicated user one or more shortcuts to the requested data.
- Tokens are similar to barcodes. When you look at a barcode, it’s not understandable, but when you have the right access and format, you can read it.
- A token requires two things: a key and a format. The key is what is passed first when you authenticate; this authentication is passed in HTTP calls, and a call to the REST interface.
(For more information on tokens, please refer to the Developer’s Guide)
Just like OAuth 2.0, xPress APIs rely heavily on existing Internet grade security. This includes the use of TLS (HTTPS) to prevent the reading of intercepted messages.
There are currently seventy objects from which solutions can be designed and built. Anyone can start to build a product or service modeled on these to provide the marketplace with options that go beyond any single xPress API. In addition to this there are many infrastructure advantages that can be realized above and beyond the APIs currently available.
xPress APIs are developed using open standards and contemporary technologies opening the marketplace to innovation and allowing users to select ‘best of breed’ applications to meet their requirements.
Find out more…