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

TritonAI Developer API — SCIM 2.0 provisioning

SCIM 2.0 (RFC 7643 / RFC 7644) user and group provisioning surface exposed by the TritonAI gateway on UC San Diego infrastructure — 18 operations across /scim/v2/Users, /scim/v2/Groups, /scim/v2/Schemas, /scim/v2/ResourceTypes and /scim/v2/ServiceProviderConfig. The deployment is the institution's; the endpoint shapes are supplied by the LiteLLM proxy software it runs. Credential-gated and not documented on the campus-facing TritonAI developer pages. This is the education regime's `scim` domain standard, present in the contract rather than in a prose claim.

TritonAI Developer API — SCIM 2.0 provisioning is one of 12 APIs that University of California, San Diego publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include SCIM, Identity, Provisioning, and Standards. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 18 operations across 10 paths, and defines 13 schemas. It is described by OpenAPI 3.0.3, at version 1.97.0.

Requests are made against a single base URL, https://tritonai-api.ucsd.edu.

18 operations 10 paths 13 schemas 2 DELETE10 GET2 PATCH2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.97.0
Base URL
https://tritonai-api.ucsd.edu
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

TritonAI Developer API — SCIM 2.0 provisioning declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Issued TritonAI API key passed as a Bearer token.

Paths & Operations 18

Across 10 paths, the API surfaces 18 operations — 2 DELETE, 10 GET, 2 PATCH, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

scim 18

SCIM 2.0 user, group, schema and service-provider-config endpoints.

GET
/scim/v2
Get Scim Base
get_scim_base_scim_v2_get 1 param → 200422
GET
/scim/v2/Groups
Get Groups
get_groups_scim_v2_Groups_get 4 params → 200422
POST
/scim/v2/Groups
Create Group
create_group_scim_v2_Groups_post 1 param body → 201422
DELETE
/scim/v2/Groups/{group_id}
Delete Group
delete_group_scim_v2_Groups__group_id__delete 2 params → 204422
GET
/scim/v2/Groups/{group_id}
Get Group
get_group_scim_v2_Groups__group_id__get 2 params → 200422
PATCH
/scim/v2/Groups/{group_id}
Patch Group
patch_group_scim_v2_Groups__group_id__patch 2 params body → 200422
PUT
/scim/v2/Groups/{group_id}
Update Group
update_group_scim_v2_Groups__group_id__put 2 params body → 200422
GET
/scim/v2/ResourceTypes
Get Resource Types
get_resource_types_scim_v2_ResourceTypes_get 1 param → 200422
GET
/scim/v2/ResourceTypes/{resource_type_id}
Get Resource Type
get_resource_type_scim_v2_ResourceTypes__resource_type_id__get 2 params → 200422
GET
/scim/v2/Schemas
Get Schemas
get_schemas_scim_v2_Schemas_get 1 param → 200422
GET
/scim/v2/Schemas/{schema_id}
Get Schema
get_schema_scim_v2_Schemas__schema_id__get 2 params → 200422
GET
/scim/v2/ServiceProviderConfig
Get Service Provider Config
get_service_provider_config_scim_v2_ServiceProviderConfig_get 1 param → 200422
GET
/scim/v2/Users
Get Users
get_users_scim_v2_Users_get 4 params → 200422
POST
/scim/v2/Users
Create User
create_user_scim_v2_Users_post 1 param body → 201422
DELETE
/scim/v2/Users/{user_id}
Delete User
delete_user_scim_v2_Users__user_id__delete 2 params → 204422
GET
/scim/v2/Users/{user_id}
Get User
get_user_scim_v2_Users__user_id__get 2 params → 200422
PATCH
/scim/v2/Users/{user_id}
Patch User
patch_user_scim_v2_Users__user_id__patch 2 params body → 200422
PUT
/scim/v2/Users/{user_id}
Update User
update_user_scim_v2_Users__user_id__put 2 params body → 200422

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are SCIMUser (10 properties), SCIMServiceProviderConfig (9 properties), SCIMGroup (6 properties), SCIMUserName (6 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
SCIMFeature
object
4 properties 1 required
SCIMGroup
object
6 properties 2 required
SCIMListResponse
object
5 properties 2 required
SCIMMember
object
2 properties 1 required
SCIMPatchOp
object
2 properties 1 required
SCIMPatchOperation
object
3 properties 1 required
SCIMServiceProviderConfig
object
9 properties
SCIMUser
object
10 properties 1 required
SCIMUserEmail
object
3 properties 1 required
SCIMUserGroup
object
3 properties 1 required
SCIMUserName
object
6 properties
ValidationError
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ucsd-scim-api-openapi.yml Raw ↑

Other APIs University of California, San Diego publishes across the network.

TritonAI Developer API — chat
TritonAI Developer API — completions
TritonAI Developer API — embeddings
TritonAI Developer API — models
TritonAI Developer API — images
TritonAI Developer API — audio
UC San Diego Library Digital Collections JSON API
UC San Diego API Gateway (WSO2 API Manager)
UC San Diego Shibboleth Identity Provider (InCommon / eduGAIN)
UC San Diego Web API Portal (Atlassian Confluence Cloud tenant)
UC San Diego DOI registration (DataCite / California Digital Library)
Where this information came from

This is an independent, third-party profile of TritonAI Developer API — SCIM 2.0 provisioning, 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.