Columbia University · Authentication Profile
Columbia Authentication
Authentication
How authentication works across the surfaces Columbia University operates. The shape of this file is the shape of the institution: one small API that needs no credential at all, and an otherwise complete estate that is reachable only with a Columbia UNI. There is no API key, no OAuth client registration, no developer account and no self-service path to any Columbia surface for a caller who is not affiliated with the university.
Columbia University declares 6 security scheme(s) across its OpenAPI definitions.
UniversityHigher EducationEducationIvy LeaguePrivate Research UniversityUnited StatesNew YorkIdentity FederationLibraryOpen DataResearch RepositoryResearch DataCourse CatalogCampus Life
Methods:
Schemes: 6
OAuth flows:
API key in:
Security Schemes
Anonymous
Columbia CAS (Central Authentication Service) browser_sso
Columbia Shibboleth Identity Provider (SAML 2.0) saml
Columbia UNI affiliation gate affiliation_gated
OpenID Connect
Instructure Canvas bearer token (CourseWorks) bearer
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.