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

UGM ID — OAuth 2.0 / OpenID Connect Authorization Server

Universitas Gadjah Mada's own identity API, operated by the Directorate of Information Technology (DTI) at oauth.simaster.ugm.ac.id, in front of SIMASTER, the university's integrated academic information system. UGM publishes an OpenAPI 3.1.0 document for it at /openapi.json (retrieved 2026-09-01, 200, 19677 bytes) and serves Swagger UI from /docs. Twenty operations across five tags: the OAuth2 core (authorize, token, introspect, revoke, logout, userinfo), Discovery (OIDC configuration, RFC 8414 metadata, JWKS), three read-only resource endpoints (/api/me, /user/me, /user/username/{username}), social login initiation for Google, Microsoft 365, Facebook, LinkedIn and Apple, and a public /health check that reports the status of its database, Redis and SIMASTER dependencies. Six grant types including PKCE-protected authorization_code and RFC 8693 token exchange. Five scopes, all read-only. The specification is written by UGM in Indonesian. Two real defects are recorded rather than smoothed over: both discovery documents emit scheme-less URLs, breaking OIDC Discovery and RFC 8414 conformance, and the JWKS endpoint returns an empty key set while advertising RS256 id_tokens.

UGM ID — OAuth 2.0 / OpenID Connect Authorization Server is one of 8 APIs that Gadjah Mada University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Identity, Authentication, OAuth, OpenID Connect, and SSO. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, a status page, and 1 JSON Schema.

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

Requests are made against 2 base URLs: https://oauth.simaster.ugm.ac.id, https://oauth.dev.ugm.ac.id.

19 operations 19 paths 8 schemas 15 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0
Base URL
https://oauth.simaster.ugm.ac.id
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
5

Authentication & Security 2

UGM ID — OAuth 2.0 / OpenID Connect Authorization Server declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuth). It accepts HTTP bearer tokens (JWT) (BearerAuth).

  • BasicAuth — clientid:clientsecret via Basic Auth header
  • BearerAuth — Access token JWT dari /oauth/token

Paths & Operations 19

Across 19 paths, the API surfaces 19 operations — 15 GET, 4 POST. They span 5 resource areas: Discovery, API, Social Login, Infra, OAuth2. Each is listed below with its method, path, parameters, and response codes.

Discovery 3

RFC 8414 & OIDC Discovery

GET
/.well-known/jwks.json
JSON Web Key Set (JWKS)
getJwks → 200
GET
/.well-known/oauth-authorization-server
OAuth 2.0 Authorization Server Metadata (RFC 8414)
getOAuthMetadata → 200
GET
/.well-known/openid-configuration
OpenID Connect Discovery
getOidcConfiguration → 200
API 3

Resource API (butuh Bearer token)

GET
/api/me
Data User — Profil Dasar
getMe → 200401403
GET
/user/me
Data User — Profil Lengkap (Simaster)
getUserMe → 200401403
GET
/user/username/{username}
Data User by Username
getUserByUsername 1 param → 200401403404
Social Login 6

Social provider login (Google, Microsoft, Facebook, LinkedIn)

GET
/authorize/apple
Login dengan Apple
authorizeApple 4 params → 302
GET
/authorize/facebook
Login dengan Facebook
authorizeFacebook 4 params → 302
GET
/authorize/google
Login dengan Google
authorizeGoogle 4 params → 302
GET
/authorize/linkedin
Login dengan LinkedIn
authorizeLinkedin 4 params → 302
GET
/authorize/microsoft
Login dengan Microsoft 365 UGM
authorizeMicrosoft 4 params → 302
POST
/callback/apple
Callback Apple Sign In
callbackApple body → 302403
Infra 1

Health check & infrastruktur

GET
/health
Health Check
healthCheck → 200503
OAuth2 6

Endpoint inti OAuth2/OIDC

GET
/oauth/authorize
Otorisasi Pengguna (Authorization Code + PKCE)
authorizeUser 7 params → 200302400
POST
/oauth/introspect
Introspeksi Token (RFC 7662)
introspectToken body → 200401
GET
/oauth/logout
RP-Initiated Logout (OIDC)
logoutUser 3 params → 200302
POST
/oauth/revoke
Cabut Token OAuth2 (RFC 7009)
revokeToken body → 200401
POST
/oauth/token
Terbitkan Token OAuth2
getToken body → 200400401
GET
/userinfo
OIDC UserInfo Endpoint
getUserInfo → 200401

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ServerMetadata (13 properties), UserDetailData (12 properties), IntrospectResponse (10 properties), UserInfoResponse (8 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
3 properties
HealthResponse
object
4 properties
IntrospectResponse
object
10 properties
ServerMetadata
object
RFC 8414 / OIDC Discovery metadata
13 properties
TokenResponse
object
Respons token OAuth2
6 properties
UserData
object
Profil dasar user dari /api/me
7 properties
UserDetailData
object
Profil lengkap user dari Simaster (/user/me, /user/username/:username)
12 properties
UserInfoResponse
object
OIDC UserInfo claims
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gadjah-mada-university-ugm-id-openapi.yml Raw ↑

Other APIs Gadjah Mada University publishes across the network.

UGM Shibboleth SAML 2.0 Identity Provider
UGM Institutional Repository OAI-PMH
UGM Journals OAI-PMH
UGM Single Sign-On (CAS)
eLOK Moodle Web Services (institution deployment)
Crossref membership (member 9411, prefix 10.22146)
ROR organization record (ror.org/03ke6d638)
Where this information came from

This is an independent, third-party profile of UGM ID — OAuth 2.0 / OpenID Connect Authorization Server, 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.