Integrations & API

Sync from your source systems, sign-in providers, Google Classroom, RFID readers, notifications, Excel and Word, and the scoped third-party API.

Data sync from a source system

Many institutions keep a central academic or student system as the source of truth. Sivitas's data-sync framework pulls from it on a schedule.

• Entities. Students, faculty, research groups, programs and study programs, time periods, courses, course classes, faculty education and assignment. Each entity has its own field mapping in the sync profile.
• Schedule. A daily run by default, plus per-minute student updates where supported. Failures notify the integration team by email or Telegram.
• Manual runs. Under Curriculum & Courses › Data sync, run Sync course & course classes or Sync faculty & student for a term, watch progress, retry failed records and read per-record errors.
• Ownership. Synced fields are overwritten on the next run; fields Sivitas owns (discipline, HR tabs, roles, constraints) are kept.

Profiles exist for institutions' own academic web services and for national data platforms. A new source needs a mapping written once by Sivitas or your IT team.

Sign-in providers

Google Workspace (OAuth) and institutional single sign-on are supported alongside email and password. See Signing in.

Google Classroom

With a Google Workspace connection, every course class can open its linked Classroom and push the roster. Google Calendar sync is available for published schedules.

RFID and fingerprint readers

Readers report taps to Sivitas by reader ID; supported device families include network fingerprint and card terminals. See Attendance & RFID.

Notifications

Email for workflow events (password reset, review assignments, survey invitations) and Telegram for operational alerts (sync failures).

Excel and Word

Almost every list exports to Excel and most bulk entry goes through Excel templates. Syllabi, course portfolios, CVs, DUPAK documents and honorarium decrees generate as Word documents.

Third-party API

Other systems (a website, a mobile app, a room-display system) can read data from Sivitas.

1. Setup › API Keys › Create. Name the consumer, choose scopes (academic calendar, courses, schedules, rooms), set an expiry.
2. Copy the key when it is shown; it is stored hashed and cannot be shown again.
3. The consumer sends the key in a header on each request. Requests are limited to 120 per minute per key. Last-used time is shown in the list.
4. Setup › API Documentation lists the endpoints with live example responses from your data.
5. Revoke a key from the list; the change is immediate.

Available endpoints cover the academic calendar (semesters, exam windows, holidays), the course catalogue, published schedules per term, and rooms. Write access and further scopes are added per agreement.