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

NUS Federated Identity Service (VAFS)

The National University of Singapore's own identity provider, and the only substantial machine-readable API surface the institution operates itself. Publishes an OpenID Connect discovery document, a JSON Web Key Set, and signed SAML 2.0 / WS-Federation metadata, all anonymously readable. Fronts OAuth 2.0 authorization, token, userinfo, device-code and logout endpoints. Relying parties are registered by NUS Information Technology; there is no public client registration and no self-service path.

NUS Federated Identity Service (VAFS) is one of 8 APIs that National University of Singapore publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Identity Federation, Authentication, OpenID Connect, SAML, and Single Sign-On. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 1 JSON Schema.

This API exposes 8 operations across 8 paths, organized into 3 resource areas, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 2026-08-19.

Requests are made against a single base URL, https://vafs.nus.edu.sg.

8 operations 8 paths 6 schemas 6 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2026-08-19
Base URL
https://vafs.nus.edu.sg/adfs
Authentication
HTTP Bearer, HTTP Basic, API Key, OpenID Connect
Terms of Service
Resource Areas
3

Authentication & Security 4

NUS Federated Identity Service (VAFS) declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP basic authentication (clientSecretBasic). An API key is passed in the header as Authorization (clientSecretPost). It supports OpenID Connect (oidc) discovered at https://vafs.nus.edu.sg/adfs/.well-known/openid-configuration.

  • clientSecretBasic — clientsecretbasic client authentication.
  • clientSecretPost — Placeholder for clientsecretpost; the provider also advertises privatekeyjwt and windowsclientauthentication.

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 6 GET, 2 POST. They span 3 resource areas: Discovery, Authorization, Session. Each is listed below with its method, path, parameters, and response codes.

Discovery 3

Machine-readable metadata describing the identity service and its signing keys.

GET
/adfs/.well-known/openid-configuration
OpenID Connect discovery document
getOpenIdConfiguration → 200
GET
/adfs/discovery/keys
JSON Web Key Set
getJwks → 200
GET
/FederationMetadata/2007-06/FederationMetadata.xml
SAML 2.0 / WS-Federation metadata
getFederationMetadata → 200
Authorization 3

OAuth 2.0 / OpenID Connect authorization and token issuance.

GET
/adfs/oauth2/authorize/
OAuth 2.0 / OIDC authorization endpoint
authorize 8 params → 302400
POST
/adfs/oauth2/token/
OAuth 2.0 token endpoint
token body → 200400
POST
/adfs/oauth2/devicecode
Device authorization endpoint
deviceAuthorization body → 200400
Session 2

End-user claims and session termination.

GET
/adfs/userinfo
UserInfo endpoint
userinfo → 200401
GET
/adfs/oauth2/logout
End session / front-channel logout endpoint
endSession 2 params → 302

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are OpenIdConfiguration (17 properties), UserInfo (16 properties), TokenResponse (7 properties), DeviceCodeResponse (5 properties). Each schema is shown below with its type and property counts.

OpenIdConfiguration
object
OpenID Provider metadata as returned by the live NUS discovery endpoint.
17 properties 4 required
Jwks
object
1 property 1 required
TokenResponse
object
7 properties 2 required
DeviceCodeResponse
object
5 properties 3 required
UserInfo
object
Claims the provider advertises in claimssupported. NUS issues pairwise subject identifiers, so sub is per-client and not a stable cross-client campus identifie…
16 properties
OAuthError
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nus-identity-openapi.yml Raw ↑

Other APIs National University of Singapore publishes across the network.

NUS NextBus (Internal Shuttle Bus) API
ScholarBank@NUS DSpace REST API
ScholarBank@NUS OAI-PMH Interface
NUS Canvas LMS API
Blog.nus WordPress REST API
NUSMods API (student-operated, not endorsed)
NUS entry in the Singapore Access Federation
Where this information came from

This is an independent, third-party profile of NUS Federated Identity Service (VAFS), 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.