How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

University of Groningen Ocasys Course Catalog API

The JSON backend behind Ocasys, the University's own course and degree-programme catalog. Verified live 2026-08-30 with no credentials: course search, full course records, the catalog page projection, programme search, faculties and organizational units, controlled option lists and the academic-year list all return 200 to an anonymous GET. Course records are bilingual and carry ECTS credits, study level, assessments, formats, prerequisites, offerings, ENLIGHT alliance status and per-course UN Sustainable Development Goal flags. Enrollment, permission and course-offering paths in the same namespace return 403 without an institutional SAML session and are documented as gated, not as callable. This is the one genuinely institution-engineered API surface in the University's footprint. The OpenAPI below is DERIVED by API Evangelist from live probes — the University publishes none, and does not advertise this interface at all.

University of Groningen Ocasys Course Catalog API is one of 6 APIs that University of Groningen publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Course Catalog, Education, Curriculum, Registrar, and Open Data. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 9 operations across 9 paths, organized into 5 resource areas, and defines 8 schemas. It is described by OpenAPI 3.1.0, at version 2026-2027.

Requests are made against a single base URL, https://ocasys.rug.nl/api.

9 operations 9 paths 8 schemas 9 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2026-2027
Base URL
https://ocasys.rug.nl/api
License
No licence published for the interface or its data
Terms of Service
Resource Areas
5

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 9 GET. They span 5 resource areas: Academic Years, Organization, Courses, Programmes, Option Lists. Each is listed below with its method, path, parameters, and response codes.

Academic Years 2

Which academic years the catalog holds and when the next one starts.

GET
/year-status
List every academic year the catalog holds
listAcademicYears → 200
GET
/year/next-academic-year-start-date
Start date of the next academic year
getNextAcademicYearStartDate → 200
Organization 1

Faculties and departments used to scope courses and programmes.

GET
/orgunit/faculties-and-universities
List faculties and the university root organizational unit
listFacultiesAndUniversities → 200
Courses 4

Course search and full course descriptions.

GET
/{academicYear}/course
Search courses within one academic year
searchCourses 2 params → 200400
GET
/{academicYear}/course/{courseCode}
Get one course by its catalog code
getCourse 2 params → 200404
GET
/{academicYear}/course/page/{courseCode}
Get the catalog page projection of one course
getCoursePage 2 params → 200404
GET
/{academicYear}/course-offering
List course offerings (institutional session required)
listCourseOfferings 2 params → 403
Programmes 1

Degree-programme search.

GET
/{academicYear}/program
Search degree programmes within one academic year
searchPrograms 2 params → 200400
Option Lists 1

Controlled vocabularies used by course and programme records.

GET
/{academicYear}/option-list
List the controlled option lists used by course and programme records
listOptions 1 param → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Course (25 properties), Program (14 properties), Option (7 properties), CourseSummary (7 properties). Each schema is shown below with its type and property counts.

LocalizedText
object
Bilingual string, Dutch and English. The catalog is authored in both languages.
2 properties
AcademicYear
object
3 properties
OrganizationalUnit
object
6 properties
CourseSummary
object
7 properties
Course
object
Full course record as served for a single course code.
25 properties
Program
object
14 properties
Option
object
7 properties
Problem
object
RFC 9457 problem detail, as emitted by the Spring backend.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-groningen-course-catalog-api-openapi.yml Raw ↑

Other APIs University of Groningen publishes across the network.

University of Groningen Research Database OAI-PMH
University of Groningen Identity Provider (SURFconext / eduGAIN)
University of Groningen Research Portal (Pure) REST API
University of Groningen research data collection on DataverseNL
University of Groningen Library discovery (OCLC WorldCat)
Where this information came from

This is an independent, third-party profile of University of Groningen Ocasys Course Catalog API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.