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 {base_url}/p/{provider}/{endpoint}

Error

A valid request URL is required to generate request examples

200

"<string>"

"<string>"

"<string>"

"<string>"

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "param": "<string>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "param": "<string>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "param": "<string>"
  }
}

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

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

200

application/json

Opaque upstream response body

The response is of type file.