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

Tongji University Open Platform

The university's own institutional data and capability API platform, operated by the Tongji University Information Office. Roughly 234 documented interfaces across fifteen families: personnel, student, teacher, teaching management, research, school management, library, campus-card and access control, asset and procurement, education-data verification, AI services, notifications, calendar, cloud meeting and electronic signature. Routes carry a version segment (/v1/, /v2/) and a delivery-mode segment — `rt` for real-time queries against the system of record, `dc` for warehouse-served batch data, `infra` for shared campus capabilities, `metadata` for reference code tables. Interfaces are called with an OAuth 2.0 bearer token from the platform's Keycloak realm under either client-credentials or authorization-code mode; thirteen reference-metadata interfaces need no credential at all and were confirmed callable on 2026-09-01. Rate limiting is a documented token bucket at 50 requests per second per application per IP, with 429 on exhaustion. Notably, every interface page names the upstream system of record it draws from — a provenance practice most university platforms do not have.

Tongji University Open Platform is one of 3 APIs that Tongji University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Open Platform, Campus Data, Research Data, Library, and Reference Data. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, rate-limit docs, a JSON-LD context, and 3 JSON Schemas.

This API exposes 13 operations across 13 paths, and defines 14 schemas. It is described by OpenAPI 3.1.0, at version 2026-09-01.

Requests are made against a single base URL, https://api.tongji.edu.cn.

13 operations 13 paths 14 schemas 13 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2026-09-01
Base URL
https://api.tongji.edu.cn
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Tongji University Open Platform declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (openPlatformOAuth) using the clientCredentials and authorizationCode flows, exposing 4 scopes. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • openPlatformOAuth — OAuth 2.0 / OpenID Connect issued by the Open Platform Keycloak realm. Discovery document: https://api.tongji.edu.cn/keycloak/realms/OpenPlatform/.well-known/o…
  • bearerAuth — The accesstoken obtained from the Keycloak realm, presented as Authorization: Bearer .

Paths & Operations 13

Across 13 paths, the API surfaces 13 operations — 13 GET. Each is listed below with its method, path, parameters, and response codes.

Reference Metadata 13

Openly callable code tables (metadata dictionaries) that define the controlled vocabularies used across every other Open Platform interface.

GET
/v1/metadata/asset/campus_gate
Campus and campus-gate reference list
v1_metadata_asset_campus_gate 1 param → 200429
GET
/v1/metadata/meeting/meeting_room
Meeting room reference list
v1_metadata_meeting_meeting_room → 200429
GET
/v1/metadata/teacher/send_user_types
Dispatched-staff category code list
v1_metadata_teacher_send_user_types → 200429
GET
/v1/metadata/teacher/status
Faculty and staff employment status code list
v1_metadata_teacher_status → 200429
GET
/v1/metadata/teacher/tech_job_code
Professional-technical post category code list
v1_metadata_teacher_tech_job_code → 200429
GET
/v1/metadata/teacher/tech_job_level_code
Professional-technical post level code list
v1_metadata_teacher_tech_job_level_code → 200429
GET
/v1/metadata/teacher/tech_level_of_workers_code
Worker technical grade code list
v1_metadata_teacher_tech_level_of_workers_code → 200429
GET
/v1/metadata/teacher/title_code
Appointed professional-technical title code list
v1_metadata_teacher_title_code → 200429
GET
/v1/metadata/teacher/types
Faculty and staff personnel category code list
v1_metadata_teacher_types → 200429
GET
/v1/metadata/user/person_idcard_type
Identity-document type code list
v1_metadata_user_person_idcard_type → 200429
GET
/v1/metadata/user/sex_code
Gender code list
v1_metadata_user_sex_code → 200429
GET
/v2/metadata/student/accom_building_code
Dormitory building code list
v2_metadata_student_accom_building_code → 200429
GET
/v2/metadata/student/accom_region_code
Dormitory region code list
v2_metadata_student_accom_region_code → 200429

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are V2MetadataStudentAccomBuildingCodeItem (8 properties), V1MetadataAssetCampusGateItem (7 properties), V2MetadataStudentAccomRegionCodeItem (6 properties), V1MetadataTeacherTechJobCodeItem (5 properties). Each schema is shown below with its type and property counts.

Envelope
object
Standard Tongji Open Platform response envelope. Every interface returns code, data and msg.
3 properties 2 required
V1MetadataAssetCampusGateItem
object
Record fields for Campus and campus-gate reference list.
7 properties
V1MetadataMeetingMeetingRoomItem
object
Record fields for Meeting room reference list.
2 properties
V1MetadataTeacherSendUserTypesItem
object
Record fields for Dispatched-staff category code list.
2 properties
V1MetadataTeacherStatusItem
object
Record fields for Faculty and staff employment status code list.
2 properties
V1MetadataTeacherTechJobCodeItem
object
Record fields for Professional-technical post category code list.
5 properties
V1MetadataTeacherTechJobLevelCodeItem
object
Record fields for Professional-technical post level code list.
4 properties
V1MetadataTeacherTechLevelOfWorkersCodeItem
object
Record fields for Worker technical grade code list.
4 properties
V1MetadataTeacherTitleCodeItem
object
Record fields for Appointed professional-technical title code list.
4 properties
V1MetadataTeacherTypesItem
object
Record fields for Faculty and staff personnel category code list.
2 properties
V1MetadataUserPersonIdcardTypeItem
object
Record fields for Identity-document type code list.
2 properties
V1MetadataUserSexCodeItem
object
Record fields for Gender code list.
2 properties
V2MetadataStudentAccomBuildingCodeItem
object
Record fields for Dormitory building code list.
8 properties
V2MetadataStudentAccomRegionCodeItem
object
Record fields for Dormitory region code list.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tongji-reference-metadata-openapi.yml Raw ↑

Other APIs Tongji University publishes across the network.

Tongji University Shibboleth Identity Provider (CARSI / eduGAIN)
ROR Organization Registration
Where this information came from

This is an independent, third-party profile of Tongji University Open Platform, 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.