The OpenAI Pass-through API from University of Amsterdam — 2 operation(s) for openai pass-through.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/university-of-amsterdam:university-of-amsterdam-openai-pass-through-api"curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a 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.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: LiteLLM OpenAI Pass-through API
description: 'Enterprise Edition
Proxy Server to call 100+ LLMs in the OpenAI format. **Customize Swagger Docs**
👉 ```LiteLLM Admin Panel on /ui```. Create, Edit Keys with SSO. Having issues? Try ```Fallback Login```
💸 ```LiteLLM Model Cost Map```.
🔎 ```LiteLLM Model Hub```. See available models on the proxy. **Docs**'
version: 1.95.0
tags:
- name: OpenAI Pass-through
paths:
/openai/{endpoint}:
put:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai__endpoint__put
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
post:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai__endpoint__post
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
patch:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai__endpoint__patch
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
delete:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai__endpoint__delete
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
get:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai__endpoint__get
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/openai_passthrough/{endpoint}:
put:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai_passthrough__endpoint__put
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
post:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai_passthrough__endpoint__post
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
patch:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai_passthrough__endpoint__patch
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
delete:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai_passthrough__endpoint__delete
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
get:
tags:
- OpenAI Pass-through
summary: Openai Proxy Route
description: 'Pass-through endpoint for OpenAI API calls.
Available on both routes:
- /openai/{endpoint:path} - Standard OpenAI passthrough route
- /openai_passthrough/{endpoint:path} - Dedicated passthrough route (recommended for Responses API)
Use /openai_passthrough/* when you need guaranteed passthrough to OpenAI without conflicts
with LiteLLM''s native implementations (e.g., for the Responses API at /v1/responses).
Examples:
Standard route:
- /openai/v1/chat/completions
- /openai/v1/assistants
- /openai/v1/threads
Dedicated passthrough (for Responses API):
- /openai_passthrough/v1/responses
- /openai_passthrough/v1/responses/{response_id}
- /openai_passthrough/v1/responses/{response_id}/input_items
Docs'
operationId: openai_proxy_route_openai_passthrough__endpoint__get
security:
- APIKeyHeader: []
parameters:
- name: endpoint
in: path
required: true
schema:
type: string
title: Endpoint
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
components:
schemas:
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
securitySchemes:
APIKeyHeader:
type: apiKey
description: Bearer token
in: header
name: x-litellm-api-key