passthrough

Provider passthrough

Runtime-configurable passthrough endpoint under /p//; enabled by default via server.enable_passthrough_routes. The endpoint path is opaque and may proxy JSON, binary, or SSE responses with upstream status codes preserved. For multi-segment provider endpoints, clients that rely on OpenAPI-generated path handling should URL-encode embedded slashes in the endpoint parameter. A leading v1/ segment is normalized away by default so /p//v1/… and /p//… map to the same upstream path relative to the provider base URL.

PATCH

{provider}

{endpoint}

curl --request PATCH \
  --url https://gomodel.example.com/p/{provider}/{endpoint} \
  --header 'Authorization: <api-key>'

"<string>"

Authorizations

Authorization

string

header

required

Path Parameters

provider

string

required

Provider type

endpoint

string

required

Provider-native endpoint path relative to the provider base URL. URL-encode embedded / characters when using generated clients.

Response

Opaque upstream response body

The response is of type file.

List batches

⌘I

Provider passthrough

curl --request PATCH \
  --url https://gomodel.example.com/p/{provider}/{endpoint} \
  --header 'Authorization: <api-key>'

"<string>"

admin

system

passthrough

batch

chat

embeddings

files

models

responses

Provider passthrough

Authorizations

Path Parameters

Response