TokenReply

Loading…

Reload
74
Classic UIClassic
ClassicSign in

Duplicated /v1 path

The final URL contains /v1/v1 because both the configured base URL and client logic add the version prefix. TokenReply currently accepts the repeated prefix, but other gateways, proxies and future clients may return 404, so fix it anyway.

Last checked · Sources: TokenReply code and documentation review; upstream wording may vary

Area
Client configuration
Typical response
Usually tolerated by TokenReply
Retry?
No, remove one prefix

Symptoms

  • Logs show a path such as /v1/v1/chat/completions or /v1/v1/messages.
  • The same configuration fails when pointed at another gateway or through a proxy.

Likely causes

  • A full /v1 endpoint was entered where the SDK expects an origin.
  • A workflow concatenated /v1 onto a base URL that already includes it.

How to diagnose

  • Inspect the exact final path after client URL joining.
  • Check environment variables and code for separate /v1 additions.
  • Compare the SDK convention with the TokenReply base URL guide.

Fixes

  • Keep /v1 in exactly one layer.
  • Use the gateway origin for Anthropic clients that append /v1/messages.
  • Use the /v1 base for OpenAI clients that append /chat/completions.

How to verify

The repeated path disappears and the request reaches one valid operation route.

Resources