Chulalongkorn University

Chulalongkorn University Authentication API

Session establishment and teardown

GitHub OpenAPI

Operations 3

GET /login Establish an SSO session and issue a service ticket #
POST /login Establish an SSO session (form POST) #
GET /logout Terminate the SSO session #

Documentation

📖
Documentation
https://account.it.chula.ac.th/wiki/doku.php
📖
APIReference
https://account.it.chula.ac.th/wiki/doku.php?id=how_does_it_work
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/chulalongkorn/refs/heads/main/authentication/chulalongkorn-authentication.yml

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/chulalongkorn/refs/heads/main/openapi/chulalongkorn-authentication-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/chulalongkorn/refs/heads/main/json-schema/chulalongkorn-sso-user-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/chulalongkorn/refs/heads/main/json-schema/chulalongkorn-course-study-schema.json

Other Resources

🔗
Examples
https://raw.githubusercontent.com/api-evangelist/chulalongkorn/refs/heads/main/examples/chulalongkorn-sso-servicevalidation-example.json
🔗
SourceCode
https://github.com/krerk/ChulaSSO.Android
🔗
CourseCatalog
https://cas.reg.chula.ac.th/class/course-schedule
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/chulalongkorn/refs/heads/main/examples/chulalongkorn-course-studies-example.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/chulalongkorn-authentication-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

chulalongkorn-authentication-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Chula SSO Authentication API
  version: '2017.01'
  description: Single sign-on authentication service operated by Chulalongkorn University at account.it.chula.ac.th, in production since January 2017.
  contact:
    name: Office of Information Technology, Chulalongkorn University
    url: https://www.it.chula.ac.th/
  termsOfService: https://account.it.chula.ac.th/wiki/doku.php
  x-provenance:
    generated: '2026-09-01'
    method: derived
    source: https://account.it.chula.ac.th/wiki/doku.php?id=how_does_it_work
    source_status: 200
    authored_by: API Evangelist
    note: Derived from the institution's published prose documentation. The institution does not publish a machine-readable contract for this service.
servers:
- url: https://account.it.chula.ac.th
  description: Production Chula SSO
tags:
- name: Authentication
  description: Session establishment and teardown
paths:
  /login:
    get:
      tags:
      - Authentication
      operationId: login
      summary: Establish an SSO session and issue a service ticket
      description: Validates credentials and generates a ticket-granting session. Without a valid session the service issues a 302 to /html/login.html carrying the service parameter; with a valid session it issues a 302 back to the service URL carrying a ticket parameter.
      parameters:
      - name: service
        in: query
        required: true
        schema:
          type: string
          format: uri
        description: URL to redirect to after successful authentication.
      - name: username
        in: query
        required: false
        schema:
          type: string
        description: Username, in email form.
      - name: password
        in: query
        required: false
        schema:
          type: string
          format: password
      - name: remember
        in: query
        required: false
        schema:
          type: integer
          enum:
          - 0
          - 1
        description: Any non-zero value makes the session non-expiring.
      responses:
        '302':
          description: Redirect. To /html/login.html with the service parameter when there is no valid session; to the service URL with a ticket parameter when there is.
          headers:
            Location:
              schema:
                type: string
                format: uri
    post:
      tags:
      - Authentication
      operationId: loginPost
      summary: Establish an SSO session (form POST)
      description: Same contract as GET /login; the documentation states GET/POST.
      responses:
        '302':
          description: Redirect, as for GET /login.
  /logout:
    get:
      tags:
      - Authentication
      operationId: logout
      summary: Terminate the SSO session
      parameters:
      - name: service
        in: query
        required: false
        schema:
          type: string
          format: uri
        description: URL to redirect to after logout. Defaults to /html/logout.html.
      responses:
        '302':
          description: Redirect to the service URL.
components:
  securitySchemes:
    DeeAppId:
      type: apiKey
      in: header
      name: DeeAppId
    DeeAppSecret:
      type: apiKey
      in: header
      name: DeeAppSecret