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 Amsterdam SSO Settings API

The SSO Settings API from University of Amsterdam — 6 operation(s) for sso settings.

University of Amsterdam SSO Settings API is one of 122 APIs that University of Amsterdam publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include SSO Settings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 6 operations across 6 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.95.0.

Requests are made against a single base URL, https://llmproxy.uva.nl.

6 operations 6 paths 14 schemas 3 GET3 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.95.0
Base URL
https://llmproxy.uva.nl
Authentication
API Key
Resource Areas
1

Authentication & Security 1

University of Amsterdam SSO Settings API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-litellm-api-key (APIKeyHeader).

  • APIKeyHeader — Bearer token

Paths & Operations 6

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

SSO Settings 6
GET
/get/internal_user_settings
Get Internal User Settings
get_internal_user_settings_get_internal_user_settings_get → 200
GET
/get/default_team_settings
Get Default Team Settings
get_default_team_settings_get_default_team_settings_get → 200
PATCH
/update/internal_user_settings
Update Internal User Settings
update_internal_user_settings_update_internal_user_settings_patch body → 200422
PATCH
/update/default_team_settings
Update Default Team Settings
update_default_team_settings_update_default_team_settings_patch body → 200422
GET
/get/sso_settings
Get Sso Settings
get_sso_settings_get_sso_settings_get → 200
PATCH
/update/sso_settings
Update Sso Settings
update_sso_settings_update_sso_settings_patch body → 200422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are SSOConfig (20 properties), DefaultTeamSSOParams (6 properties), ValidationError (5 properties), DefaultInternalUserParams (5 properties). Each schema is shown below with its type and property counts.

SSOSettingsResponse
object
Response model for SSO settings
3 properties 2 required
LitellmUserRoles
string
Admin Roles: PROXYADMIN: admin over the platform PROXYADMINVIEWONLY: can login, view all own keys, view all spend ORGADMIN: admin over a specific organization,…
AccessControl_UI_AccessMode
object
Model for Controlling UI Access Mode via SSO Groups
3 properties 3 required
DefaultTeamSSOParams
object
Default parameters to apply when a new team is automatically created by LiteLLM via SSO Groups
6 properties
SSOConfig
object
Configuration for SSO environment variables and settings
20 properties
InternalUserSettingsResponse
object
Response model for internal user settings
2 properties 2 required
ValidationError
object
5 properties 3 required
KeyManagementRoutes
string
Enum for key management routes
DefaultTeamSettingsResponse
object
Response model for default team settings
2 properties 2 required
HTTPValidationError
object
1 property
RoleMappings
object
Configuration for mapping SSO groups to LiteLLM roles. The system will look at the groupclaim field in the SSO token to determine which role to assign the user…
4 properties 2 required
NewUserRequestTeam
object
3 properties 1 required
DefaultInternalUserParams
object
Default parameters to apply when a new user signs in via SSO or is created on the /user/new API endpoint
5 properties
TeamMappings
object
Configuration for mapping SSO JWT fields to team IDs. This allows configuring teamidsjwtfield via the database instead of requiring config file changes and res…
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-amsterdam-sso-settings-api-openapi.yml Raw ↑

Other APIs University of Amsterdam publishes across the network.

UvA Identity Provider (SAML 2.0 / SURFconext)
DataNose API
UvA Library Linked Open Data (TriplyDB tenancy)
UvA-DARE OAI-PMH and Pure Web Service (Elsevier Pure tenancy)
UvA Archives Collection Descriptions OAI-PMH (ArchivesSpace tenancy)
UvA Central Catalogue OAI-PMH (Ex Libris Alma tenancy)
UvA/HvA Research Data Repository (Figshare tenancy)
UvA Timetable API (MyTimetable tenancy)
University of Amsterdam A2a API
University of Amsterdam A2a Registration API
University of Amsterdam access group management API
University of Amsterdam Adaptive Router API
Where this information came from

This is an independent, third-party profile of University of Amsterdam SSO Settings 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.