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 Hong Kong O Auth API

OAuth 2.0 / OpenID Connect protocol endpoints.

University of Hong Kong O Auth API is one of 8 APIs that University of Hong Kong publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and 1 JSON Schema.

This API exposes 5 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2026-08-19.

Requests are made against a single base URL, https://adfs.hku.hk.

5 operations 5 paths 2 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-08-19
Base URL
https://hkafidp.hku.hk/idp/shibboleth
Authentication
HTTP Bearer, OAuth 2.0
License
Not stated
Resource Areas
1

Authentication & Security 2

University of Hong Kong O Auth API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode, clientCredentials and deviceCode flows, exposing 9 scopes. By default, every request must be authenticated.

  • bearerAuth — Access token issued by https://adfs.hku.hk/adfs, signed RS256.
  • oauth2 — Flows transcribed from the HKU AD FS discovery document.

Paths & Operations 5

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

OAuth 5

OAuth 2.0 / OpenID Connect protocol endpoints.

GET
/adfs/oauth2/authorize/
Authorization endpoint
authorize 7 params → 302503
POST
/adfs/oauth2/token/
Token endpoint
token body → 200400411
POST
/adfs/oauth2/devicecode
Device authorization endpoint
deviceAuthorization → 200405
GET
/adfs/userinfo
UserInfo endpoint
userinfo → 200401
GET
/adfs/oauth2/logout
End-session endpoint
endSession → 302503

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TokenResponse (6 properties), OAuthError (3 properties). Each schema is shown below with its type and property counts.

OAuthError
object
RFC 6749 section 5.2 error response.
3 properties
TokenResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hku-oauth-api-openapi.yml Raw ↑

Other APIs University of Hong Kong publishes across the network.

HKU Shibboleth Identity Provider
HKU ITS API Developer Portal and Gateway
HKU Scholars Hub OAI-PMH
HKU DataHub (Figshare tenancy)
HKU Libraries Discovery (Ex Libris Primo tenancy)
HKU Microsoft Entra ID Tenant
University of Hong Kong Discovery API
Where this information came from

This is an independent, third-party profile of University of Hong Kong O Auth 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.