Question 1

Which standards and protocols does Fuxam support for integrations?

Accepted Answer

Fuxam consistently relies on open standards. For identity and SSO, SAML 2.0, OAuth 2.0 and OIDC are supported, and for directory services LDAP and Active Directory. Learning content can be connected via LTI 1.3 and imported as SCORM packages. Calendar synchronization runs via iCal stream, and all other interfaces use the documented REST API for event-based workflows. For official notifications, Dakota is integrated for GKV data exchange.

Question 2

Can we connect our own third-party systems via the REST API?

Accepted Answer

Yes. Fuxam’s REST API is fully documented and covers all platform objects, students, modules, curricula, rooms, appointments, applications, grades, and more. Authentication is handled via OAuth 2.0 or API keys. University IT teams or external service providers can build integrations without waiting for vendor releases.

Question 3

How does the migration of data from existing school management systems work?

Accepted Answer

Yes. Fuxam’s REST API is fully documented and covers all platform objects, learners, subjects, curricula, classrooms, appointments, registrations, grades, and more. Authentication is handled via OAuth 2.0 or API keys, and webhooks notify external systems about changes in real time. School IT teams or external service providers can build integrations without waiting for vendor releases.

Question 4

Will existing investments in Moodle content and SCORM packages be preserved?

Accepted Answer

Yes. External learning tools can be integrated directly into Fuxam via LTI 1.3, SCORM packages are natively supported and can be imported individually or in batches. Existing Moodle courses, external authoring tools such as Articulate Storyline or iSpring, and SCORM-compliant learning materials can continue to be used without needing to recreate anything.

Question 5

What does the situation look like regarding interfaces and data exchange between Fuxam and third-party systems?

Accepted Answer

All interfaces are encrypted via HTTPS and TLS. API access requires OAuth 2.0 authentication or API keys with configurable permissions. The granular authorization system allows you to control, for each integration, which data is exchanged. Audit logs record every API access in a tamper-proof manner.

Question 6

Which integrations are native and which run via the REST API?

Accepted Answer

Natively integrated are video conferencing systems (Zoom, Microsoft Teams, Google Meet, BigBlueButton), calendar tools (Outlook, Google Calendar, Apple Calendar), identity providers (Active Directory, LDAP, SAML/OAuth/OIDC), payment processing (Stripe), wallet systems (Apple Wallet, Google Wallet), and statutory health insurance data exchange (Dakota). Via the REST API, library software, CRM systems, ERP and accounting solutions, as well as school-specific tools can be connected. No plug-ins, no adapters required.

Question 7

Who builds the custom integrations – Fuxam, our IT department, or external service providers?

Accepted Answer

Standard integrations are available natively and are configured as part of the implementation. For custom connections via the REST API, there are three options: the institution’s IT department builds them independently using the documented API, external service providers implement them, or Fuxam handles the integration as part of an extended implementation package. The choice lies with the institution, depending on available resources and the complexity of the integration.

Seamless Integration Through Open Interfaces

Live Sessions, Just One Click Away

Appointments Right Where They’re Already Managed

One Login for the Entire University Environment

From the First Lead to Alumni Engagement

School Fees, Contracts and Payment Statuses on a Single Data Basis

Full Integrability Into Existing Systems

Book Your Personal Demo

Frequently Asked Questions About Interfaces