Endpoint
input is one string or an array of strings. The gateway resolves model through the virtual key and translates the request into the provider’s own embeddings call.
Request
Response
Which providers serve it
Parameters the gateway changes or refuses
The
X-LangWatch-End-User-Id, X-LangWatch-Metadata and Traceparent request headers work as on Chat Completions.
Response headers
The same set as Chat Completions:X-LangWatch-Gateway-Version, X-LangWatch-Gateway-Request-Id, X-LangWatch-Fallback-Count, X-LangWatch-Budget-Warning, Traceparent, X-LangWatch-Heartbeat-Active, and X-LangWatch-Provider on a forwarded provider error. X-LangWatch-Handled-Error carries the error.code when the gateway wrote the error itself, and is removed from a forwarded provider response.
Streaming
This endpoint does not stream. Astream field in the body is not read.
Errors
Codes this endpoint raises before the provider is called:missing_model, model_not_allowed, model_provider_not_bound, model_not_recognized, bad_request, end_user_required. All answer 400. A provider’s own error is forwarded with its status and body. The full table is on Errors.
Also check: Fallback chains, Model aliases.