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 Containers API

The containers API from University of Amsterdam — 10 operation(s) for containers.

University of Amsterdam Containers 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 Containers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 18 operations across 10 paths, and defines 2 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.

18 operations 10 paths 2 schemas 4 DELETE10 GET4 POST

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 Containers 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 18

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

containers 18
GET
/containers
List Containers
list_containers_containers_get → 200
POST
/containers
Create Container
create_container_containers_post → 200
GET
/v1/containers
List Containers
list_containers_v1_containers_get → 200
POST
/v1/containers
Create Container
create_container_v1_containers_post → 200
GET
/containers/{container_id}
Retrieve Container
retrieve_container_containers__container_id__get 1 param → 200422
DELETE
/containers/{container_id}
Delete Container
delete_container_containers__container_id__delete 1 param → 200422
GET
/v1/containers/{container_id}
Retrieve Container
retrieve_container_v1_containers__container_id__get 1 param → 200422
DELETE
/v1/containers/{container_id}
Delete Container
delete_container_v1_containers__container_id__delete 1 param → 200422
GET
/v1/containers/{container_id}/files
Handler Container Id
handler_container_id_v1_containers__container_id__files_get 1 param → 200422
POST
/v1/containers/{container_id}/files
Handler Multipart Upload
handler_multipart_upload_v1_containers__container_id__files_post 1 param → 200422
GET
/containers/{container_id}/files
Handler Container Id
handler_container_id_containers__container_id__files_get 1 param → 200422
POST
/containers/{container_id}/files
Handler Multipart Upload
handler_multipart_upload_containers__container_id__files_post 1 param → 200422
GET
/v1/containers/{container_id}/files/{file_id}
Handler Container File
handler_container_file_v1_containers__container_id__files__file_id__get 2 params → 200422
DELETE
/v1/containers/{container_id}/files/{file_id}
Handler Container File
handler_container_file_v1_containers__container_id__files__file_id__delete 2 params → 200422
GET
/containers/{container_id}/files/{file_id}
Handler Container File
handler_container_file_containers__container_id__files__file_id__get 2 params → 200422
DELETE
/containers/{container_id}/files/{file_id}
Handler Container File
handler_container_file_containers__container_id__files__file_id__delete 2 params → 200422
GET
/v1/containers/{container_id}/files/{file_id}/content
Handler Binary Content
handler_binary_content_v1_containers__container_id__files__file_id__content_get 2 params → 200422
GET
/containers/{container_id}/files/{file_id}/content
Handler Binary Content
handler_binary_content_containers__container_id__files__file_id__content_get 2 params → 200422

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ValidationError (5 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
ValidationError
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-amsterdam-containers-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 Containers 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.