For developers
Developer API
Universities run many systems. This page explains how Oxonia connects with them today and how to ask about API access.
Where we are today
Oxonia connects to the systems most universities use through standards: LTI 1.3 for learning platforms, and Microsoft, Google, or SAML and Shibboleth for sign-in. These cover rosters, links, study packs and identity.
The full scope, format and terms of a public developer API are [to be confirmed]. This page will be updated when they are confirmed.
What universities usually ask for
- Moving student and course lists into Oxonia from the student record system.
- Sending released results from Oxonia Mark to the student record system.
- Sending fee payments from Oxonia Wallet to the finance system.
- Taking staff records from HR into Oxonia Nexus.
- Pulling figures into the university's own reports, alongside Oxonia Compass.
How we handle it now
During onboarding, our team works with your IT team on data import and on the connections you need. Onboarding and data import are available from £5,000. Tell us about your systems when you book a demo.
Principles we will follow
- Access only through keys the university controls, set in the admin console.
- Each key limited to the data it needs.
- Every call recorded in the audit log.
- Official records, such as marks and minutes, still approved by a named person before they leave Oxonia.
Security
Any API will follow the same protections as the rest of the platform. See Security overview, Encryption and Access controls and 2FA. To report a security issue, see Vulnerability disclosure.
Stay informed
Changes to integrations will appear in the release notes.
Common questions
Can we export our data? Yes. Your data is yours. How and when you can export it is set out in the terms of service and the data processing agreement.
Is there a sandbox? Details of any test environment are [to be confirmed].
Who do we talk to? Our onboarding team. Start by booking a demo.
If your university has a specific connection in mind, write it down before the demo: which system, which data, how often and who owns it. That makes it much quicker for our team to tell you what is possible now and what is planned.
Related